| Title: | note 3 has pointer to current kit |
| Notice: | note 3 has pointer to current kit |
| Moderator: | PEACHS::GHEFF |
| Created: | Wed May 29 1991 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 3301 |
| Total number of notes: | 14905 |
Dear All,
I have a problem of connecting eXcursion to the server.
I'm not able to connect to the server. I have attached the
message.log from eXcursion.
The configuration of the UNIX Server is:
-AlphaServer 4100
-Digital UNIX 4.0B
-tu0 -- 202.44.210.84 egat1
-tu1 -- 10.110.2.250 egat2
The PC client configuration
-WIN95
-IP: 10.5.1.42
eXcursion 3.0
-enable XDMCP
XDMCP Startup Mode
- query host 10.110.2.250
XDMCP Configuration setting
- once
Access:
valid nodes: 10.5.1.42
controlling host: 10.5.1.42
Here's the error log file
1/4/40 11:53:15 X Server Information eXcursion V3.0.554
(Windows95) logging enabled.
1/4/40 11:53:20 X Application Startup Information rexec:
connection succeeded
1/4/40 11:53:20 X Application Startup Information ksh:
@SYS$SYSTEM:PCX$SERVER 4,0,0,TCPIP,10.5.1.42 "/usr/bin/X11/mwm": not
found ksh: setenv: not found
1/4/40 11:53:26 X Application Startup Information mwm: Could not
open display.
1/4/40 11:54:14 X Server Error Fatal server error:
1/4/40 11:54:14 X Server Error Xserver: unknown host:
10.110.2.250
1/4/40 11:54:14 X Server Fatal Error Fatal error: check error
log for details.
------------------------------------------------------------------------
And I also have another system with this following configuration.
The configuration of the UNIX Server is:
-AlphaServer 8200
-Digital UNIX 3.2g
-tu0 -- 10.1.1.103 tac
The PC client configuration
-WINNT 4.0
-IP: 10.1.1.104
When I install eXcursion and configure in eXcursion control panel as
the following
eXcursion 3.0
-enable XDMCP
XDMCP Startup Mode
- query host 10.1.1.103
XDMCP Configuration setting
- once
Access:
valid nodes: 10.1.1.104
controlling host: 10.1.1.104
It works fine but the client have to wait for a long time berfore it
can connect to the server.
And when I boot UNIX Server with Digital UNIX 4.0B. I got the same
problem that I'm not able to connect Unix Server.
Here's the error log file
4/1/97 2:30:44 PM X Server Information eXcursion V3.0.554
(Alpha) logging enabled.
4/1/97 2:30:44 PM Network Warning socket(12) failed,
error=EAFNOSUPPORT
4/1/97 2:30:45 PM Network Warning socket(12) failed,
error=EAFNOSUPPORT
4/1/97 2:30:45 PM Network Warning getnodeadd() failed,
error=EAFNOSUPPORT
4/1/97 2:30:45 PM Network Warning setsockopt(152)
failed, error=ENOPROTOOPT
4/1/97 2:32:51 PM X Server Error XDM: too many
retransmission
Thank you very much in advance.
Wanthipa Wongsamut
Technical Support
Digital Equipment Corporation Thailand
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 3256.1 | PEACHS::GHEFF | Got a head with wings | Tue Apr 01 1997 12:49 | 26 | |
>1/4/40 11:53:20 X Application Startup Information ksh:
>@SYS$SYSTEM:PCX$SERVER 4,0,0,TCPIP,10.5.1.42 "/usr/bin/X11/mwm": not
>found ksh: setenv: not found
This first set of error messages indicates a connection that it not
XDMCP. It shows an rexec connection that looks like it's failing
because the wrong Command Interpreter has been selected in the
eXcursion control panel. Make sure you select "ksh" instead of "Any."
You say that XDMCP is enabled. Does the XDMCP connection succeed?
After looking at:
>1/4/40 11:54:14 X Server Error Fatal server error:
>1/4/40 11:54:14 X Server Error Xserver: unknown host:
I'd guess that it doesn't. I'd query the remote host by its name
rather than its address. I recall a bug with query that causes it to
fail when using an address.
On the second set of error messages, check to make sure you're running
the released version of eXcursion. 3.0.554. 3.0.551 had a problem
that caused this message to appear.
#Gary
| |||||
| 3256.2 | Still Not Working | TLAV02::16.158.208.64::somnuk | Tue Apr 01 1997 23:11 | 35 | |
Hi Gary,
>>1/4/40 11:53:20 X Application Startup Information ksh:
>>@SYS$SYSTEM:PCX$SERVER 4,0,0,TCPIP,10.5.1.42 "/usr/bin/X11/mwm":
>>not found ksh: setenv: not found
> This first set of error messages indicates a connection that it not
> XDMCP. It shows an rexec connection that looks like it's failing
> because the wrong Command Interpreter has been selected in the
> eXcursion control panel. Make sure you select "ksh" instead
> of"Any."
We have changed to UNIX(ksh) too.
>I'd guess that it doesn't. I'd query the remote host by its name
>rather than its address. I recall a bug with query that causes it
>to fail when using an address.
We have tried both by address and by name. It does not work either.
>On the second set of error messages, check to make sure you're
>running the released version of eXcursion. 3.0.554. 3.0.551 had a
>problem that caused this message to appear.
We have the released version installed.
With all those changes, we still got the same error messages. Any
ideas. Could it be the DUNIX 4.0B or network configuration at the
customer site?
Thanks
Best Regards,
Somnuk
| |||||
| 3256.3 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Thu Apr 03 1997 17:40 | 6 | |
You seem to have a mismatch of operating systems here. The
"@SYS$SYSTEM:PCX$SERVER" would normally be for vms, but the
"/usr/bin/X11/mwm" would be for unix. I wouldn't expect to see both !
/Eric
| |||||
| 3256.4 | I chose Digital UNIX | TLAV02::16.158.208.71::somnuk | Fri Apr 04 1997 02:33 | 8 | |
Hi Eric, I chose Digital UNIX operating system at the Application tab. That's what wonder me too. Is there any bug in eXcursion on error reporting? Best Regards, Somnuk | |||||
| 3256.5 | JAMIN::OSMAN | Eric Osman, dtn 226-7122 | Tue Apr 08 1997 11:55 | 8 | |
I don't know of any particular error-reporting bug that would
cause what you are seeing.
Make sure you are careful about whether in the excursion control
panel you pick "rsh" or "rexec". It makes a difference.
/Eric
| |||||