Re: Xstart session time out
From: Jeremy Dodds (
)
Date: Mon May 31 2004 - 12:49:34 EDT
Hello,
I'd check to make sure nothing is blocking port 6000 between the Sun servers
and your PC. You also might want to make sure Xstart is picking up the
right IP Address. Telnet into the host and run "who -u". It should show
what IP address the host sees you coming in on.
Jeremy
----- Original Message -----
From: "J. Potts" <
>
To: <
>
Sent: Saturday, May 29, 2004 3:17 PM
Subject: Re: Xstart session time out
> On Thu, 27 May 2004, J. Potts wrote:
> > I'm having a problem trying to use an Exceed xterm window when dialing
in
> > to work from home. I just have a 56k modem so there's no VPN, no high
speed
> > connection. When I run the Exceed xstart program to start up xterm
windows,
> > the program connects to the host but times out before spawning the xterm
> > window. There are multiple Sun servers I've tried to connect to in our
> > network and I get the same problem with all of them.
> >
> > The version of Exceed is 7.1. I've used xstart methods of telnet and
rlogin.
> > The command line used was:
> >
> > @(XTerm, method=stdappdb) -display @d&@
> >
> > (this from the default command line provided by Exceed for Sun servers).
> > Our company help desk had me try an rexec session with a command line of
> >
> > export DISPLAY=@d;/usr/openwin/bin/xterm -ls &
> >
> > I didn't even get a host reply out of that one.
> >
> > When I used the first method, I'd get a window that would pop up with
the
> > host reply (having checked that option in xstart). Here is an example:
> >
> > Status: Connection open
> > Start Method: RLOGIN (port 513)
> > Host: ctip5ei.ih.lucent.com
> > User ID: navoff
> > Command: /usr/openwin/bin/xterm -display 135.255.30.86:0.0&@
> >
> > Also, in the box at the bottome of the window was the host response:
> >
> > /usr/openwin/bin/xterm -display 135.255.30.86:0.0&@
> > [1]15661
> > ksh: @: not found
> > ...a man with three buttocks
> > >
> >
> > (Note: the "...a man with three buttocks" with the carriage return and
the
> > ">" is my prompt)
> >
> > After a the designated timeout (currently set for 30 seconds) the popup
> > window status changed from "Connection open" to:
> >
> > Status: Connection closed (close timeout)
> >
> > Just a couple of weekends ago, I was able to use my exceed xstart
profile
> > to login in just fine. I just haven't been able to get it to work
during
> > the week (I'll have to test again this weekend to see if I can get in).
> >
> > The same program and setup works fine when I dial into my private ISP.
> > It also works fine when I'm at the office where I'm connected to our
LAN.
> > If anyone has any suggestions/solutions, please pass them along.
>
>
> Just a followup - I changed the close timeout to -1 and eventually an
> additional error message popped up:
>
> /usr/openwin/bin/xterm Xt error: Can't open display: 135.255.30.20:0.0
>
> I've checked the security settings under the Xconfig window and the
> "Host Access Control List" is set to "Disabled (any host access)". And
> the "Allow Clients to Modify Host Access Control List" checkbox is
unchecked.
>
This archive was generated by hypermail 2b29
: Mon May 31 2004 - 23:54:01 EDT
|
|
