xdmcp problem

[Michael Koops_1]

Hello

since 2 days we have problems to establish CDE sessions on a zx6000 (11.23) with ReflectionX. The same problems appear with a suse-9.1-box while there are no problems with 2 old hp-ux-boxes (10.20). the Xerrors file in /var/dt shows

error (pid 4000): Server open attempt #0 failed for xxx.intern:0, giving up

or

error (pid 4056): display xxx.intern:0 could not be initialized, server may be grabbed.

I checked all the previous issues here with similar problems but couldn't get a solution.

any good ideas?

[Govinda_1]

try restarsting the dtlogin.rc in HP-UX.

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

regards
Govinda.

[Michael Koops_1]

Hi Govinda

i did several times.

Michael

[B. Hulst]

Hi,

When you are sure no one is logged onto the server then kill -9 all the running processes called dtsession. Then stop & start as suggested above. :-)

If that does not work, then brute force:

#/sbin/init.d/dtlogin.rc stop

ps -ef | grep dt
kill all the process left running there
which have dt in the begin name (dtlogin, dtsession, etc... You can find more suggestion in /usr/dt/bin/dt*

#/sbin/init.d/dtlogin.rc start

Regards,
Bob

[RAC_1]

Can you resolve xxx.intern properly?? to and fro?? Also run dr_dt and check for errors.

What does ~/.dt/errorlog and startlog says??

Anil

[John Dvorchak]

This sounds like a name resolution problem. The HP boxes seem to be able to resolve, forward and reverse, the Reflection X box while the zx6000 and the suse box can't.

The hint is the error message "display xxx.intern:0 could not be initialized"

I am not sure if that is a DNS problem or not.

From the Reflection X box just try to telenet to the zx6000 box and if that works do a who -mT to see who the box really thinks you are. Name and address. Verify that name and address is correct for your Reflection X box.

[Michael Koops_1]

@Bob

i rebooted the machine several times to get clean processes but it didn't help

@Anil

the name resolution works in both directions without problem. dr_dt shows no warnings and no errors. the ~/.dt/-logs didn't show anything because i didn't get a login-screen.

thanx
Michael

[B. Hulst]

Try to connect with an X terminal or eXceed or ... just in case the reflection X is not messed up.

- Bob

[Michael Koops_1]

@John

telnet works and who -mT shows xxx.intern, so everything seems to be as it should

thanx
Michael

[Alex Glennie]

Not sure if this will work but ...

cp /usr/dt/config/Xconfig -> /etc/dt/config/Xconfig ...

vi -> set

Dtlogin*grabServer: False

Dtlogin*terminateServer: True

wq!

restart X .... any difference ?

[Michael Koops_1]

@Bob

we tried from every reflX-equipped pc and some linux-boxes and got always the same hangup

Michael

[RAC_1]

What is there in /var/adm/inetd.sec file??
Any restrictions there??

Anil

[Michael Koops_1]

Hi everybody

friday evening i tried to login from my home-pc (via isdn and router). absolutely no problems!!! this morning i got in on the second attempt. my collegues were successful too after some attempts. i didn't change anything in the configuration compared to friday afternoon. in my view it looks like a timing problem, but who is to slow or to fast? keep in mind that we have no problems with our old hpux-boxes.

greetings
michael

[Michael Koops_1]

@anil

just one line in inetd.sec:

dtspc allow

michael

[Michael Koops_1]

@alex

the changes in Xconfig didn't make any difference

michael

[B. Hulst]

Hi,

Try using a network sniffer to see what actually is going between the two hosts.

For example ethereal has good analyzing capabilities to see perhaps why the connection does not get establish.

It helped me a few times.

Just put a laptop with windows ethereal and listen the two hosts' traffic. And then start search in the output for port 6000 (the standard X11 port)

Regards,
Bob

[Michael Koops_1]

Hi everybody

yesterday we solved our problem:

we found out that one of our routers runs a dns-server with factory default configuration. this dns-server responds to reverse lookup requests and provides wrong hostnames so that reflectionX couldn't work properly.

thank you all for your assistance
Michael

[Michael Koops_1]

see above