To eliminate VT & HP3000, what happens when the ping size is increased?
ping addr -l 64
ping addr -l 128
ping addr -l 256
ping addr -l 1024
I also would look at the network statistics for each router. Sounds like small packets are making it, but larger packets aren't.
Mike
----- Original Message -----
From: johnpitman
To: [log in to unmask]
Sent: Thursday, February 19, 2004 3:36 AM
Subject: [HP3000-L] Network problem
Situation - N4000, 1x 220mhz, 1GB Ram. Happily running ~200 users. Remote
sites served by Frame Relay with DTCs on ends for some serial devices, most
now VT-mgr connected. Moving to Private IP network. Tested 1 remote site -
fine, no problem. Next site, 1000 miles away- connects fine, pings both ways
etc, BUT - any conversation with more than trivial output from 3000 to
user - hangs, mpe logs it off ~ 2-3 mins later. Small output, like :SHOWME
works fine. Max segment size in NMMGR was 1514 (despite finding a web page
that says max is 4600, default 4200) reduced to 1280 , no change. Telnet
connections work ok, but dont support Block mode, which is mandatory.
increasing the ping packet size until time out, quits at 1471 bytes - 1470
is ok, 1471 times out, reliably. probably just a function of bytesx speed >
timeout interval. Behaves the same from 3000 or from other PC s on network.
The fact that one site is ok, and the bad one is fully visible indicates the
gateway set up is ok on 3000 - gateway1 points at Internet firewall for VPN
access, gateway2 points at the ADSL router going out to the private ip
channel, and has all the relevant subnets listed. Tested another site in
same city, connects ok, and doesn't hang, but dropped connection a few
times.....
Any and all suggestions gratefully received.
Anybody BTDT???
TIA,
jp
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *
|
