I have a Tru64 4.0f system running behind an NT box that is acting as a
ras server for a dialup. I want to be able to connect up to it with
eXcursion. There are three nics on the Alpha, each in a different
subent. When I tried to connect the first time I got a message saying
that there were three ip's on the system, so it will take some time.
This is my first question. Do I need to do any special configuring to
get DU to respond to eXcursion requests on all three nics? Or, can I
make sure that the nic I want will respond?(the nic that is on the same
network as the NT ras server)
My second question has to do with a message from the eXcursion console
itself. When trying to connect I get the following:
X Application Startup Information rexec: connection succeeded
X Application Startup Information _at_SYS$SYSTEM:PCX$SERVER
4,0,0,TCPIP,161.99.113.171 "XDMCP": Command not found.
DISPLAY=161.99.113.171:0.0: Command not found. export: Command not
found.
XDMCP: Command not found.
What does this mean? That XDMCP is not found on the DU box? I can run
excursion from the NT ras server onto the Alpha, but cannot connect from
a box logged in via ras. I have read some posts regarding windows in
the list and I thought the suggestion of running xdm in debug mode was a
good one. It said to go th the /var/lib/xdm/xdm-config file. There is
no /var/lib directory on the DU box. What does that mean? I have five
Alphas all with DU 4.0f and none of them have a /var/lib directory?
Still, if I can log in with my ras server, why can't I log in with a box
logged into the ras server?
Thanks!
Trevor Osatchuk
Received on Wed Mar 21 2001 - 19:57:39 NZST