CDE

[Martin Corner]

Using Reflection X to connect to one of several L class servers running hpux 11 and get the following error message on the client.

Your XDMCP connection timed out - make sure that the hosts on your network are running XDM programs.

In Xerrors I get the following error "Server open attempt #0 failed for PCNAME:0, giving up.

We have no problems connecting to the other L classes on the LAN.

Help much appriciated
Ian

[S.K. Chan]

Check the other L classes that were ok to see if they are running the dtlogin daemon.
# ps -ef|grep dtlogin
If they are, then check the server that you're having problem to see if it's running dtlogin. If it's not restart it ..
# /sbin/init.d/dtlogin.rc start
The dtlogin daemon manages all XDMCP connection request and my guess is it's probably not running on the server.

[Martin Corner]

Thanks for response

Tried ps -ef | grep dtlogin and got:
root 2171 2156 0 13:30:04 ? 0:00 /usr/dt/bin/dtlogin

Also tried stopping and starting dtlogin.

Even tried rebooting the machine. After reboot of machine I got the following messages in Xerrors:

Thu Jun 6 13:30:39 2002
error (pid 2387): Server -auth cannot be executed

Thu Jun 6 13:30:39 2002
error (pid 2171): Server unexpectedly died

Thu Jun 6 13:30:44 2002
error (pid 2171): Server for display Dtlogin*dtlite: can't be started.

Thu Jun 6 13:30:44 2002
error (pid 2417): Server -auth cannot be executed

Thu Jun 6 13:30:44 2002
error (pid 2171): Server unexpectedly died

Thu Jun 6 13:30:49 2002
error (pid 2171): Server for display Dtlogin*xdmMode: can't be started.

Thu Jun 6 13:40:04 2002
error (pid 3611): Server open attempt #0 failed for mbpc1331:0, giving up

[Michael Tully]

Hi,

Are there any differences in the patch levels of this L class server compared to other ones.

# swlist -l fileset | grep CDE

HTH
Michael

[Martin Corner]

Checked and the patches are identical on all machines

[Steven Sim Kok Leong]

Hi,

Are there any firewall restrictions pertaining to this specific L-class?

Have you checked the configuration files? Run the diagnostics to verify the configuration:

# /usr/contrib/bin/X11/dr_dt

Hope this helps. Regards.

Steven Sim Kok Leong

[S.K. Chan]

Try running CDE diagnostic tool on the server that worked and on the one that does not work and compare the two.
# /usr/contrib/bin/X11/dr_dt > cdelog
Can you spot any "significant difference in these 2 output ?

[Martin Corner]

Thanks again for input, I have run /usr/contrib/bin/X11/dr_dt on a machine that works and the one that doesn't and there is no difference, 6 warnings and no errors. The warnings are the same on both machines and are to do with file permissons.

[Steven Sim Kok Leong]

Hi,

To verify whether it is a firewall or filtering issue, can you swap the IP address of this faulty system with that of a working one?

If the faulty system now works, it is caused by firewall filtering. If it doesn't, the problem is narrowed to a cause within the system itself.

Hope this helps. Regards.

Steven Sim Kok Leong

[S.K. Chan]

This is from HP Technical Document, "Setting up CDE with Reflection X" it may give you additional clues on what to look for.
DocID=KBRC00000052

http://support1.itrc.hp.com/service/cki/search.do?searchString=KBRC00000052&mode=id&submit=Search&searchCrit=allwords&docType=Security&docType=Patch&docType=EngineerNotes&docType=BugReports&docType=Hardware&docType=ReferenceMaterials&docType=ThirdParty

Hope it helps ..

[Alex Glennie]

this is a new one on me .... I'd be tempted to compare the contents of /usr/dt/config/Xconfig and if it exists /etc/dt/config/Xconfig as that's where Dtlogin xdm mode and Xaccess could be set ... check the permissions on these too as well as ownerships ....

[Steve Steel]

Hi

maybe your system is slower

check patch levels

run /usr/contrib/bin/X11/dr_dt and check the output

vi /etc/dt/config/Xconfig

Uncomment
############################################################################
# To specify how long the Login Manager waits to connect to an X-server.
#
# Dtlogin*openTimeout:

Set it to 60 seconds

Steve steel

[Joe Colucci_1]

I would try to verify that the system is not having problems resolving its own hostname. This can cause seemingly random problems that don't immediately seem related.

I know there is an issue in 11.11 where the server will ALWAYS try to reach the dns server if dns is in /etc/nsswitch regardless of the order. If dns cannot be reached, the process has to wait for the timeout period before finding the hostname in /etc/hosts. This causes delays resolving the servers own hostname and can cause telnet and X access problems.

Try doing an nslookup on the servers hostname from the server itself. If it does not respond immediately, you have found the source of the problem.

[zhi wang_1]

not sure whether you are in "BROADCAST" method or "INDIRECT" method. But you should choose "DIRECT" method. In the box below "method" you will soon have all your servers on the network. Choose the one you want and then click "connect". The CDE should come up.

Good luck