Re: Telnet over WAN latency troubleshooting

John,
thanks for replying. For the time being we're holding; the ISP
has indicated that Bellsouth has acknowledged the problem and is
working on it. We don't have any further info at this point.

Right now we don't have any peecees or other systems capable og
being an SNMP browser at the remote sites, and nobody really capable of
installing or running one at the central location. I can probably open
up an SNMP rule on the firewall central site firewall and let the Alpha
do the very basic browsing that the tools VMS comes with is capable of,
but thats it.

The purpose of trying the ping tests to the intervening routers
was to see if we could localize the latency to one box, or one
connection; we were not able to do that. However thats a good point
about the traffic shaping capability, even though for traffic within
the tunnel they should not be aware of the traffic type... of course
they could be downgrading the tunnel traffic priority too.

We're running Sonicwall firewalls at each location. These
firewalls provide IPSec VPN site to site tunnels. We have tried
bypassing the tunnels completely by turning them off and setting up
telnet 'holes' in the central site firewall for the users to come in
directly; we also tried leaving the tunnels up and having some users go
through the tunnel and others go outside of it.

The applications in question are good old fashioned SMG based
screen apps on VT terminals. The lag is expecially noticeable when
typing in larger fields, when scrollable regions scroll, and on screen
refresh/updates. There is no question about system latency; local
users, and the one or two remote terminals left on the MUXservers due
to the problems are running fast and clean. Flow control is XON/XOFF,
just as it was on the DECmuxes.

We have telnetted to the DECservers and then telnetted back out,
either to the customer central site or our own location. When we go to
the customer site, the latency is very obvious; when we telnet back to
our own system (yet another telnet hole in the firewall) its present
but not as bad subjectively... but then I haven't had time to run a
side-by-side test either. Our own telnet access to the customer system
(through another tunnel) runs nicely. No comm analyzer available.


We have other customers running in this configuration, with the
same (or nearly) equipment; the main difference is these are brand new
sparkly DECserver 90M+ units with DNAS V3.2, and the other sites all
use DECserver 90M units with DNAS 2.2 or 2.3a. Of course the others
are not on Bellsouth ADSL with PPPoE underpinnings either, though
several sites are running similar applications over 'normal' ADSL with
faster uplink speeds without issue.

Rich

.

Relevant Pages

  • Re: telnet replacement - not ssh?
    ... telnet in combination with kerberos, s/key or srp ought to do as you ask. ... since part of the traffic is via the internet an unencrypted transport ... connect to it via ssh from outside via the firewall but nothing but telnet ... telnet from the tunnel terminus, so if work needs to be done on the ...
    (comp.security.misc)
  • Re: Cisco PIX or VPN 3000 Concentrator to effect IPSec tunnel
    ... Set the VPN 3000 outside. ... > are trying to set up a secure tunnel using IPSec to a customer. ... > customer is using Checkpoint firewall and Checkpoint VPN software. ...
    (comp.security.firewalls)
  • Re: Remote telnet through firewall failing
    ... >> I have not found internet telnet to be the worst of the various security ... I was amazed that after months on the internet (directly to ... no firewall) there was no discernible problems. ... have over 250,000 BSD machines for their hosting services. ...
    (comp.unix.sco.misc)
  • Re: smtp to my isp (demon)
    ... Colin typed: ... telnet will not connect with using port 25. ... I have the firewall on the internet and email ... Demon do not block port 25 (tested this on the old server). ...
    (microsoft.public.windows.server.sbs)
  • Re: 45 days STUCK LIKE CHUCK. DNS / Mx record cant recieve emails
    ... I don't think it's Exchange since it's responding to telnet from the LAN. ... think it's the firewall, in which case it should be fixed if you run the ... still could be the Comcast router that's blocking the incoming connection. ... like Exchange not listening on the Internet NIC. ...
    (microsoft.public.windows.server.sbs)