XDMCP Fatal error for XTRA!X opening display with HPUX11.0

[Belinda Dermody]

I have been running XTRA!X for NT Version2.0 on my PC and had no problems connecting to my two HP Servers when they were running 10.20. Since I installed 11.0 about 6 months ago, I can not connect to either server. I have no problems connecting to a number of our Sun Servers running 2.7 and 2.8

I get the same error on both HP system H50 and K200 box with 11.00
XDMCP fatal error Session failed 11 failed for display va6its202227.xxxxxxx.com:4
Cannot Open Display.

I have tried it with no other XTRA!X running and while others where active same results each time.

[Steve Steel]

Hi

Maybe name resolution.

nslookup name
nslookup ip

Of the PC and the servers

Does the pc have a similar name to the servers.


Steve Steel

[Belinda Dermody]

The PC has the same name and IP to all the servers. Also there is no firewall between the PC and the servers, all servers that I connect too are on the inside.

[Alex Glennie]

sorry to ask the obvious but you do hae a dtlogin process running on the hpux 11 system right ?

other than taht it would most likely be down to hostname resolution .... could you try using a short hostname as opposed to a fully qualified one or try adding the ip address of the pc into /etc/hosts too ?

one other thing I just spotted : va6its202227 is more than 8 characters long which CDE will not like without the following steps :

1. Do this by adding a line in /etc/rc.config.d/netconf such as:

NODENAME="short"

2. You will also need to edit /etc/hosts and add this as an alias
to your hostname. This is very important as CDE will not work
without it. An example entry might be:

123.4.5.6 verylongname short

If you are using DNS and do not wish to have DNS entries for
these "short" nodenames, you must also configure the system
to use /etc/hosts before using DNS to resolve names and IP addresses.
This can be accomplished by using an "/etc/nsswitch.conf" file with
"files" before "dns" and/or "nis" on the hosts
line. An example file that can be used may be found at:

/usr/examples/nsswitch/nssw.filesdns

It can be put into place with:

cp -p /usr/examples/nsswitch/nssw.filedns /etc/nsswitch.conf

3. Finally, change your hostname entries in /var/adm/inetd.sec to your
IP address, for example:

Change line:

dtspc allow 127.0.0.1 verylongname

To read:

dtspc allow 127.0.0.1 123.4.5.6

4. Reboot the machine (/sbin/reboot will do).

[Steve Steel]

Hi

Alex explains what I was after well

If the first part of the names is the same
in the PC and server you have had it.

Do what he asks


Steve Steel

[Belinda Dermody]

I do have dtlogin running.

You might have misunderstood me, plus I have trouble explaining things also.

The 2 HP Hosts are Aspen and Cancun, the va61ts202061 is the PC running NT and EXTRA!X; like I said earlier, I was running XTRA!X on the PC without problems with 10.20, only since I did the cold install of 11.00 is when the problem started, connecting the Sun Solaris box's is no problem. Is there a set up or a configuration that I need to do or load on the HP systems.