Solaris 9 x86 CDE not starting via XDMCP [5]

Hi,

I'm trying to get remote CDE login access from a WinXP box (A) to a Solaris 9 x86 server (B) with XManager 2.0 0502. I can see the X server start, but nothing happens (as far as I can see), no errors but no login screen either!

1. dtlogin is running on (B) (UDP port 32771);
2. CDE login works OK locally on the Sun box;
3. Xstart xterm works OK from (A) to (B) over SSH;
4. /etc/dt/config/Xaccess is set to *
5. /usr/openwin/lib/xdm/xdm-errors reports nothing.
6. I tried XDM broadcast, no joy;
(returns XDMCP connection failed)
XDM Query (port 32771), no joy;
XDM Indirect (port 32771), no joy.

What am I missing here?

Thanks in advance for your help.

lollobis

Hello

First of all, is there a specific reason why you are using the port no. 32771 instead of 177? If not, then I think you should stick with the default UDP 177 port.

Also, make sure that your remote host can make a connection back to you PC. If there is any firewall between your PC and the remote host, you should open up the TCP 6000~6010 ports toward your PC direction. This includes the firewall installed on your PC as well.

Hope this helps.

Hi Andrew,

Thanks for your reply.

On Solaris, XDMCP is dtlogin which listens on UDP PORT 32771.
I've tried with the default 177 as well, but still the same behaviour.

bash-2.05# netstat -an

UDP: IPv4
Local Address Remote Address State
-------------------- -------------------- -------
*.111 Idle
*.* Unbound
*.32771 Idle
*.514 Idle
*.* Unbound
*.* Unbound

TCP: IPv4
Local Address Remote Address Swind Send-Q Rwind Recv-Q State
-------------------- -------------------- ----- ------ ----- ------ -------
*.* *.* 0 0 49152 0 IDLE
*.111 *.* 0 0 49152 0 LISTEN
*.* *.* 0 0 49152 0 IDLE
*.22 *.* 0 0 49152 0 LISTEN
192.168.1.11.22 192.168.1.12.1059 65483 51 49524 0 ESTABLISHED
*.6010 *.* 0 0 49152 0 LISTEN
*.6010 *.* 0 0 49152 0 LISTEN
*.* *.* 0 0 49152 0 IDLE

TCP: IPv6
Local Address Remote Address Swind Send-Q Rwind Recv-Q State If
--------------------------------- --------------------------------- ----- ------ ----- ------ ----------- -----
*.* *.* 0 0 49152 0 IDLE
*.22 *.* 0 0 49152 0 LISTEN
*.6010 *.* 0 0 49152 0 LISTEN

Active UNIX domain sockets
Address Type Vnode Conn Local Addr Remote Addr
d472ccc0 stream-ord d4045358 0000000 /tmp/.X11-unix/X0
d472cde8 stream-ord 0000000 0000000
bash-2.05#


Both boxes are on the same LAN.
The Sun server has no host-based firewall, the PC is running the firewall of WinXP SP2 (though allowing Xmanager services).
Just to rule this out, I've disabled the WinXP firewall alltogether, but the problem is still there.

Also, /var/dt/Xerrors on the Sun box is empty.

Any other idea?

Cheers

lollobis

Please check if you can see the remote host icon in Xbrowser. If the remote host is listed in Xbrowser, the problem is most likely caused by the remote host not being able to find your PC. Try adding your PC's IP address in /etc/hosts file like the following example:

192.168.1.198 $PC_NAME

Also, if you have not edited the dtlogin settings, you should use the default UDP 177 port. Netstat result for the TCP 32771 port is assigned for other daemons such as Xsun, some RPC services as well and it does not accept XDM connection.

If you problem persists, please provide us with the following information:

1. Xmanager log file. It is located in the following directory:

C:\Documents and Settings\%USER%\Application Data\NetSarang\Xmanager\2\Log\*.log

2. Can you see the remote host in Xbrowser?

Please let us know if we can be of further assistance.

Hi Support,

Well, I can see the remote host in Xbrowser because I've created an entry for it with "New Session Wizard" myself!

The IP address of my PC is already present on the /etc/hosts file of the Sun box.

I haven't changed any dt settings on the Sun box: I've also tried sticking to the default UDP port 177 when connecting with XManager, but no joy.

Attached is the latest XManager logfile.

Thanks again


lollobis

I had a same problem before and the problem was the blocked UDP 177 port on the Solaris machine. Check your firewall settings on the remote server.

To test this proble, try disabling the firewall for a moment and see if you can connect.

Also, I've notices, sometimes dtlogin process malfunctions for some reason. Try restarting the dtlogin process.

Does this problem only occur in your computer only or in all computers as well?