xdmcp and dtlogin... not responding.

[Karvendhan M]

Hi,

We are running one workstation with 10.20 + Sep 2000 General Release Pathces. PC users will log into these boxes using exceed.

Exceed's chooser list didn't display this workstation. I checked the unix box. For some reasons the monitor, kbd & nouse have been removed from that. So I commented the Xserver file entry for localhost and restarted /sbin/init.d/dtlogin.rc . /var/dt/Xerrors says,

Fri Sep 14 15:36:42 2001
error (pid 21053): error binding socket address 177, errno = 2

and no dtlogin process is alive. I restarted dtlogin.rc once again after putting thr original Xservers file in /etc/dt/config.

Now two dtlogin processes are running but I am not able to connect to that workstation using xdmcp . ( But the same error message has been repeated in /var/dt/Xerrors ). Sometime back this workstation was running fine.

Any solutions?

Thanks in Advance.

Karvendhan M.

[Santosh Nair_1 · Accepted solution]

Hmm, this sounds like dtlogin is trying to bind to port 177 but can't because someone else is already binding to that port. I'd kill off the dtlogin daemons since no one can use them anyway, then see if the port is being used by someone using the command netstat -na|grep 177|grep LISTEN. Then if that port is being used, find out by whom...you would have to use something like lsof for this.

-Santosh

[Karvendhan M]

Hi Santosh,

It is saying and not port. Also A typo in my question. It is 77 not 177. Sorry, and many thanks for such a fast reply.


Karvendhan M.

[Santosh Nair_1]

I'm sorry but I didn't understand your statements. Are you sure its complaining about port 77 and not 177...I thought dtlogin was supposed to bind to UDP port 177.

Also, what seems strange is that its reporting errno 2 which is "No such file or directory" rather than errno 226 which is "Address already in use" or something along those lines.

Could you also check if you have a /var/spool/socket/pwgr directory and /var/spool/pwgr/status file.

-Santosh

[Wodisch]

Hello,

if you remove mouse and keyboard from HP workstations
or servers, then the X-server will NOT be able to start!
Edit your "/etc/dt/config/Xservers" and comment out
the line starting with "*" (and ending in something like "/usr/bin/X11/X :0").

Then re-start the XDMCP daemon with:

/sbin/init.d/dtlogin.rc stop; /sbin/init.d/dtlogin.rc start

HTH,
Wodisch

[Scott Hebl]

I've encountered the same problem using exceed to connect to some of my machines... What I've discovered though, is that the one machine that consistently doesn't show up on the XDMCP Display Chooser list WILL eventually show up if I give it time (Sometimes as long as 10 minutes.) In my situation this machine is under a very heavy load, but as usual I suspect if I poked around enough I could find a better reason for why it takes so long to respond to the xdmcp request...

Anyway, try it again and let it sit there for ahwile to see if it'll show up in the list.

Scott