Timeout during connection [4]

When opening an XManager session to various internal UNIX boxes, I find that sometimes the connection works and I get a login dialog box and sometimes the connections doesn't work and I get no login box. I believe the issue here is a timeout problem. Is there any way I can control the timeout for XManager when I open a connection?

Thanks.
Sam

Xmanager waits about 15 seconds for the server to respond. After that, when there is no answer, it displays the "XDMCP connection failed, try again?" message box. If you click Yes, it waits another 30 seconds for a response from the server. There is no other timeout features in Xmanager. The response packet is small and even in slow network environments it should work well.

The problem might occur when too many users are using XDMCP sessions or the dtlogin process is unstable due to an unknown error. It may be helpful to read the following files:

- /var/dt/Xerrors in Unix machine.
- C:\Program Files\Xmanager1.3.9\Xmanager.log file in Windows.

Hope to solve the problem.

----
Technical Support

Thanks for responding. I never receive a timeout message from XManager. When a connection cannot be made when the XManager window opens, I just get a grayish, hatchmark background on the screen.

From looking at the logs, I still get a feeling that I am having a timeout problem. Below is the contents of the Xerrors file and my local XManager log file. Does this provide you any clue regarding the problem? Remember, sometimes the connection works, but it is unpredictable.

Thanks.
Sam

Xerror log:

Thu Oct 9 09:42:02 2003
error (pid 17565): Server open attempt #0 failed for wmwmnt26244.us.randomhouse.com:2, giving up


XManager log:

Xmanager Version 1.3.9.5 Build 16
Copyright (c) 1997-2002 NetSarang Computer, Inc.
All rights reserved.

UTC Date: Thu Oct 09 13:41:39 2003
Local Date: Thu Oct 09 09:41:39 2003

X Server Directory: "C:\Program Files\Xmanager1.3.9\"
Log File Path: "C:\Program Files\Xmanager1.3.9\Xmanager.log"
Server Generation 1
XDMCP UDP Port: 177
Product Serial #: 020926-110004-005040
WinSock Version 1.1
Highest Version 2.2
Description: WinSock 2.0
System Status: Running
Max Sockets: 32767
Max UDP Datagram: 65467
Local Hostname: 'WMWIT026244'
Local Host IP Address: 10.104.26.97
Xdmcp Init State: 0
Xdmcp Query Address: 10.104.9.65
Screen Resolution: 1152 x 864
Size of Palette: 0
Number of Reserved Colors: 20
Resolution of Color: 24
Depth of Screen: 32
Maximum Cursor Width: 32
Maximum Cursor Height: 32
Frame Width: 4
Frame Height: 4
Border Width: 1
Border Height: 1
Maximum Client Area Width: 1152
Maximum Client Area Height:817
Width of Display(mm): 320
Height of Display(mm): 240
Dots Per Inch X: 96
Dots Per Inch Y: 96
Icon Width: 32
Icon Height: 32
Caption Height: 19
DBCS Enabled: 0
GDI batch limit: 20
Mouse buttons: 3
Waveform Output Devices: 1
Mouse wheel present: 1
Monitors: 1
Same display format: 1
Virtual screen (x, y): (0, 0)
Virtual screen w x h: 1152 x 864
Screen 0: 1152 x 845
Keyboard file: US 101 keyboard
Keyboard type: 0
nKeys, minKC, maxKC, mapWidth, nCompose: 101, 8, 109, 4, 0
Number of keycodes: 102
Number of KeySyms: 408
Bytes of KeySyms: 1632
=== OS Version Information ===
Platform id : 2
Major Version : 5
Minor Version : 0
Build Number : 2195
Description : "Service Pack 2"
Country Code : 1
Country String: United States
==============================
Xdmcp Request Address: 10.104.9.65
Xdmcp Connection Address 0: 10.104.26.97
Xdmcp: sent a REQUEST message
Xdmcp: received an ACCEPT message
Xdmcp: sent a MANAGE message.
Xdmcp: Timed out, state 8. Retransmissions: 0
Xdmcp: sent a MANAGE message.
Xdmcp: Timed out, state 8. Retransmissions: 1
Xdmcp: sent a MANAGE message.
Xdmcp: Timed out, state 8. Retransmissions: 2
Xdmcp: sent a MANAGE message.
Xdmcp: received a FAILED message.
Xdmcp fatal error: Session failed Session 60 failed for display wmwmnt26244.us.randomhouse.com:2: Cannot open display

First, we recommend that you upgrade Xmanager to the newest version:

/download/download.html

Second, check the "wmwmnt26244.us.randomhouse.com" is correctly mapped to "10.104.26.97" in the name server. Sometimes an incorrect DNS configuration may prevent the server connecting to Xmanager.

The server tries to connect to Xmanager. If there is no response from Xmanager for about 15 seconds, it aborts the connection. Usually the problem occurs when the server tries to connect to an incorrect IP address (due to the name server problem).

Also, the dtlogin process may not work well. Please try to reboot the server machine, if possible.

I hope this can help you.

----
Technical Support

Here is a little more information. About 20 minutes after my previous attempt to connect to the server failed, I tried again. This time I successfully connected. However, when I looked in the Xerrors log file, I found the following entry:

Thu Oct 9 10:05:33 2003
error (pid 17684): OCFInit: OCF_WaitForCardInserted failed with return code 33

So, even though I was able to connect, an error was still logged.

Thanks.
Sam