Re: telnet delays

Allen McIntosh wrote:

they seem to be having significant keystroke delays at different times of the day(press "K" wait a second, press "I", wait...etc). those on the internal network, where the server is located, do NOT have that problem.

My first reaction was that it was because of the dsl, but that can't be because two offices 75 miles from each other are having the same problem at the same time - has to be an internal problem. The main office(server site) is 192.168.1.x, and the offices are on 192.168.30.x and ~40.x


It doesn't have to be internal - for example, it could be a sluggish router on whatever path the two routes have in common.

Things you might try
- install some good network monitoring software
- look at all hardware under your control and make sure you're not having hardware problems somewhere (firewall, border router, ...). I'm thinking high error counts here. I don't think this matches the pattern you are seeing, but it never hurts to be thorough.
- run a low frequency ping (or udpping; need to turn the echo port on) from both remote systems and see if you get delays at the same time.
- run same to another system and see if you get delays at the same time (unless you are 100% sure it's not a server problem).
- capture traffic at the clients and determine if packets are being dropped.
- capture traffic at both ends and measure one-way delay. (hard problem)


After running netstat I see that the ~:ipp TIME_WAIT status below coincides with the slowdown? ipp would be a printjob, yes? Can I adjust the tcp_fin_timeout from 60 to, say, 15 or 30?

tcp 0 0 localhost.localdomain:48751 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48750 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48763 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48762 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48760 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48767 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48766 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48765 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48764 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48755 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48754 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48752 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48759 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48758 localhost.localdomain:ipp TIME
_WAIT
tcp 0 0 localhost.localdomain:48756 localhost.localdomain:ipp TIME
_WAIT
.

Relevant Pages

  • Re: telnet delays
    ... those on the internal network, where the server is located, do NOT have that problem. ... - run a low frequency ping from both remote systems and see if you get delays at the same time. ... - run same to another system and see if you get delays at the same time (unless you are 100% sure it's not a server problem). ...
    (comp.os.linux.networking)
  • Re: telnet delays
    ... >>> the internal network, where the server is located, do NOT have that ... >> from both remote systems and see if you get delays at the same time. ... >> (unless you are 100% sure it's not a server problem). ... My first thought about your problem was improper MTU settings, ...
    (comp.os.linux.networking)
  • Re: Still having firewall issues
    ... Microsoft CSS Online Newsgroup Support ... How many subnets are in your SBS internal network? ... |> 4) Click Add Adapter and then select Server Local Area Connection. ... |> to the same internal default gateway address as the ISA Server computer. ...
    (microsoft.public.windows.server.sbs)
  • Re: Sort files by filename
    ... is running on a server that simply relays the data to all our ... but this is a production server that feeds 13MB/hr for each ... Otherwise routing delays could cause you additional ... list of missing files, and it would take only milliseconds, primarily ...
    (Fedora)
  • Re: Still having firewall issues
    ... How many subnets are in your SBS internal network? ... > 4) Click Add Adapter and then select Server Local Area Connection. ... No default gateway difined. ... > to the same internal default gateway address as the ISA Server computer. ...
    (microsoft.public.windows.server.sbs)