xdmcp

[Eddy Sun]

pls find the attached log file. Thx.

[Steven E. Protter]

An explanation of what the trouble is would be useful. The logfile is not very easy to read.

The most common problem for xdmcp broadcasting not working is VLAN setup, which won't let the client see the server broadcast.

Help us out a little.

SEP

[Gopi Sekar]

is this log from client or server?

if from client, it means the client connection is rejected by the server. Server is not actually listening for XDMCP connection or it is denying the conntion from this client.

Gopi

[Eddy Sun]

The log is from the linux machine which acts as display server. All the applications are running in the other side, the HP-UX.

[Eddy Sun]

Very hard to get real info from the log. Agreed on that. What's VLAN. They can ping each other.

ES

[Gopi Sekar]

ooohhh, its still a confusing question :)

you said linux is display server, does it mean your X Server is on HP UX and linux is used to do X query to HP UX server.

If this is the scenario, then Linux is client and HP UX is server(where all applications are stored).

If this is the case, then it means your HP UX server is rejecting connections from Linux machine. go to HP UX machine and run xhost +

eg: xhost +linux

it will allow further connections from linux and you should be able to login.

Gopi

[Stuart Browne]

heh.. Terminology with X is fun.

Here's why:

XServer = the bit that does the GUI.
XClient = software which displays *ON* the XServer

So the Linux box *IS* the XServer.

It's querying an 'xdmcp' server which is remote, but that launches an XClient (window manager or something else).

The 'xdmcp' server isn't an XServer. It's an 'xdmcp' server.