• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

XDMCP problem.

C

charleskoh04

Member

Is the below result normal for a XDMCP transaction ?

eth-s1p2c0:i[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p2c0:I[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p1c0😱[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p1c0😱[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177

How come the input is also the output ???Pls advise.
 
Sorry ppl, i forgot that there are smileys enabled in this forum

eth-s1p2c0:i[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p2c0:I[55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p1c0 [55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
eth-s1p1c0 [55]: a-> b(UDP) len=55 id=47416
UDP: 3971 -> 177
 
Looks normal enough.
You've got some UDP packets, 55 bytes in length. The TCP session ID is 47416.

Sending from port 3971 to port 177.

Port 177 is a well-known port:

xdmcp 177/tcp X Display Manager Control Protocol
xdmcp 177/udp X Display Manager Control Protocol

I don't understand your reference to the input also being the output ...

There is no transaction exhibited by the output you've posted .... other than it appears to be TCP ... all of the traffic is going from machine 'a' to machine 'b'

What kind of problem are you having?


Scott


(Edited to correct pre-coffee typos)
 
Hi, the problem is the remote host is unable to login to the x-manager.Error msg is something like connection timeout...

User able to telnet to the host, ping and traceroute but just cant login.

Any advise ?
 
Are *any* hosts able to connect via X?

If not, chanced are you need to enable it on the *nix box. Check out the config files in /etc/ X (or X11, or X11R6 ...depends on the flavor of *nix)/ xdm and gdm.

If others can get in, then it's some peripheral parameter, like available fonts, or a firewall.

Most flavors of *nix are delivered with Telnet disabled, and SSH enabled instead. SSH is the same terminal functionality as Telnet, but it's encrypted (SSH also enables some other functions that may be desirable ... like secure FTP and tunnelling).

Find & download an SSH client and try that, or enable telnet on the *nix box (find & run telnetd (that's telnet-DEE).

Since your captured traffic shows no response from the *nix side, I'm going with "You need to enable X on the *nix ox" or you have a firewall in the way.

(Which X server/package are you trying to use?)

Good Luck

Scott
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top