>I am presently running the following:
>SCO:Unix::5.0.5Eb rs505a.Unix505.1.0a oss471c.Unix505.1.0a
>I am trying to telnet in from home to this office computer running SCO.
>at home I have Win98 connected through a cable modem and optonline ISP.
>at work the computer is connected to a Ugate 3200 router to a westell XDSL
>modem and ISP is bell atlantic. At work there are a few other Win98
>machines connected locally to the network through the Ugate3200
>When I use one of the Win98 computers at work and telnet into SCO everything
>From home when I telnet in to the SCO , I get the Login prompt and I do log
>in. It seems that whatever I run, after about 1 or
>maybe 2 minutes the computer hangs and I have to close down the telnet
>session to continue. It does not seem to make a diff if I run an application
>or if I just doing things like system commands ( i.e. ls, cd and so on). I
>am using PoweTerm Interconnect
>terminal emulation program from Ericom Software to telnet. It does not seem
>to be the telnet software at home since the same thing happens with
>Hyperterminal as well as the Windows telnet software.
Methinks the important thing to do first is to isolate whether the
problem is at the Windoze end, there router in between, or at the OSR5
end. Basically, I start at the furthest part of the puzzle (the
application) and work my way back to your Windoze machine. This is often
called "assigning the blame".
It's not clear from your description if the telnet session on the Windoze
box is what is hung, or if the application you're running on the OSR5 end
is hung. The easiest way to determine this is to run *TWO* telnet
sessions, using whatever Windoze telnet client is convenient, connected
to the OSR5 box. One runs the application, the other just sits on the
shell prompt. If the application is hung, but not the shell prompt, then
methinks there is something wrong with the application. Perhaps it
doesn't appreciate packet loss or something. If both sessions hang
simultaneously, then it's not the application.
Try checking for network errors on the OSR5 end:
llistat -l (long and messy).
Since you're on a switched port, you should have absolutely no
collisions. If there are a bunch, it's possible that your OSR5 NIC is
broken, or possibly the driver. However, as local traffic works, this is
probably not the case.
Are there any other machines, on your office lan, that are accessible
from your home computer? Try maintaining a connection to those those.
It doesn't have to be telnet, but can be some other service (email, web,
ftp, whatever). If it also hangs, then it's not the OSR5 server. If it
works well, then I don't have a clue.
The next step is to telnet to the Ugate 3200 router IP address or perhaps
fire up the web browser configuration interface. No need to change
anything, just see if there's a reliable connection. I'm not sure this
is possible as some cheap routers (i.e. Linksys) are not accessible from
the WAN side. I'm also curious as to how many services are running on
the router. Cacheing DNS? VPN Pass-thru? DHCP server? Etc? Just
curious. Are you connecting directly to the SCO OSR5 box via IP port
re-direction, or are you running a VPN to some kind of NT server, and
connecting from there? Just guessing.
Yech. Worthless data sheet from marketting.
Assuming the Umax Ugate 3200 can be eliminated as a potential problem,
that leaves Bell Atlantic. I'll assume that you're getting a reliable
connection with reasonable packet loss. Run:
netstat -e -s
on your Windoze box for clues. Look for errors. A small percentage are
Moving to the Windoze machine, do other services to high traffic web
sites and such work well? I'll assume they do. Have you done any of the
RWIN tweaks? See:
The RWIN tweak (maximum receive window) is necessary to get decent
performance over xDSL and cable modems. There is a similar tweak for
OSR5 that I described in the past. It's probably NOT necessary if you
have a 100baseT card in the OSR5 server. However, the 10baseT defaults
are much too small. See:
It's at the bottom. If running:
perf. params: recv size: 4096; send size: 8192;
It's time to tweak. Also, be careful about running inconfig. It breaks
a needed symlink.
150 Felker St #D Santa Cruz CA 95060
831-421-6491 pager 831-429-1240 fax
http://www.cruzio.com/~jeffl/sco/ SCO stuff