Hmm.. Slow on LAN fast on DSL

[Vortex-5]

This is a strange problem (but then again I won't be posting if it was a easy one).

I've recently used some tweaking programs to play around with the registry settings to optimize my broadband unfortunately these killed my lan connection, so I went and hunted down the entries it edited. I made sure I got all entries from the suspected program. But it still doesn't help I've used several program so I don't really know which one might've caused it.

I've went into the registry and deleted: (Win98SE)

MaxMTU
DefaultRcvWindow
DefaultTTL
Size/Small/Medium/Large
BcastNameQueryCount
BcastQueryTimeout
... (you get the idea) All of these are under the MSTCP Key (HKLM\SYSTEM\CurrentControlSet\Services\VxD\MSTCP) (from memory might miss a subkey)

Basically I reset the MSTCP and NetTrans back to it's defaults unfortunately it looks like something else was affected, the strange thing is that I send files on my lan very slow but can recieve files from other computers at normal speed maybe something with the DefaultTCPSendWindow that you can't change?

[POBrien]

Check this thread. If not installed already, Try nebeui on all stations first.

http://forums.winguides.com/showthreaded.php?Cat=&Board=brdQuestions&Number=12155&page=2&view=collapsed&sb=5&part=

[Vortex-5]

I've fixed it not with netbeui some other problem but I have a new problem now and this is party why I was going so slow........ I have a 10% packet loss that's bad how do I check for suspected packet loss?

[POBrien]

Here's the results of pinging and tracing your ip address 206.47.244.55.

Pinging 206.47.244.55 with 32 bytes of data:



Reply from 206.108.98.226: Destination net unreachable.

Reply from 206.108.98.226: Destination net unreachable.

Reply from 206.108.98.226: Destination net unreachable.

Reply from 206.108.98.226: Destination net unreachable.



Ping statistics for 206.47.244.55:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 0ms, Maximum = 0ms, Average = 0ms



Tracing route to ch5smc.bellglobal.com [206.47.244.55]

over a maximum of 30 hops:



1 21 ms 28 ms 30 ms adsl-63-205-228-254.dsl.snfc21.pacbell.net [63.205.228.254]

2 15 ms 16 ms 16 ms core3-g2-0.snfc21.pbi.net [206.171.134.130]

3 16 ms 16 ms 16 ms edge1-ge1-0.snfc21.pbi.net [209.232.130.20]

4 20 ms 19 ms 19 ms sl-gw25-stk-8-3.sprintlink.net [160.81.16.21]

5 18 ms 19 ms 20 ms sl-bb21-stk-5-3.sprintlink.net [144.232.4.229]

6 53 ms 53 ms 53 ms sl-bb20-kc-11-0.sprintlink.net [144.232.9.205]

7 52 ms 52 ms 53 ms sl-bb20-kc-8-0.sprintlink.net [144.232.2.118]

8 63 ms 65 ms 62 ms sl-bb23-chi-6-0.sprintlink.net [144.232.8.202]

9 64 ms 62 ms 63 ms 144.232.26.53

10 64 ms 65 ms 63 ms sl-gw22-chi-8-0.sprintlink.net [144.232.10.10]

11 65 ms 66 ms 66 ms sl-ba-4-0-0.sprintlink.net [144.232.189.22]

12 65 ms 65 ms 65 ms core1-chicago23-pos10-0.in.bellnexxia.net [206.108.103.141]

13 107 ms 106 ms 107 ms core2-toronto63-pos3-0.in.bellnexxia.net [206.108.103.129]

14 107 ms 109 ms 109 ms dis22-toronto63-pos11-0-0.in.bellnexxia.net [206.108.98.226]

15 dis22-toronto63-pos11-0-0.in.bellnexxia.net [206.108.98.226] reports: Destination net unreachable.



Trace complete.

The Destination net unreachable statement implies that your isp's router isn't acknowledging your ip address. Contact them to check for any known issues. Also, ask them if the Destination net unreachable statement is normal.

(http://www.freesoft.org/CIE/RFC/792/3.htm)








Let's view your results.

1. Open a dos window and type...

ping regedit.com > c:\ping.txt

this command will re-direct the ping results to the ping.txt file in the c:\ drive.

then type..

tracert regedit.com > c:\trace.txt

post both results.

The Packet loss could also be local to your setup.

Do you run a firewall?

Post your Lan config as well.

[Vortex-5]

-->Ping Results:

Pinging regedit.com [209.197.107.91] with 32 bytes of data:



Reply from 209.197.107.91: bytes=32 time=171ms TTL=243

Reply from 209.197.107.91: bytes=32 time=180ms TTL=243

Reply from 209.197.107.91: bytes=32 time=165ms TTL=243

Reply from 209.197.107.91: bytes=32 time=176ms TTL=243



Ping statistics for 209.197.107.91:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 165ms, Maximum = 180ms, Average = 173ms

-->Trace Route Results:



Tracing route to regedit.com [209.197.107.91]

over a maximum of 30 hops:



1 61 ms 62 ms 112 ms HSE-Toronto-ppp289002.sympatico.ca [64.231.19.1]

2 55 ms 54 ms 54 ms dis21-toronto63-fe0-1-0.in.bellnexxia.net [206.108.106.33]

3 60 ms 57 ms 56 ms core2-toronto63-pos11-12.in.bellnexxia.net [206.108.98.213]

4 97 ms 96 ms 95 ms core1-chicago23-pos3-0.in.bellnexxia.net [206.108.103.130]

5 101 ms 102 ms 99 ms bx1-chicago23-pos10-0.in.bellnexxia.net [206.108.103.142]

6 234 ms 222 ms 212 ms 500.POS5-0-0.GW5.CHI6.ALTER.NET [157.130.107.113]

7 216 ms 219 ms 222 ms 116.ATM2-0.XR1.CHI6.ALTER.NET [146.188.209.154]

8 211 ms 215 ms 214 ms 191.at-1-1-0.TR1.CHI4.ALTER.NET [146.188.208.242]

9 427 ms 440 ms 411 ms 106.at-7-0-0.TR2.DCA8.ALTER.NET [146.188.138.178]

10 432 ms 432 ms 432 ms 197.at-5-0-0.XR1.TCO1.ALTER.NET [152.63.32.189]

11 432 ms * * 193.ATM6-0.GW3.PIT1.ALTER.NET [152.63.37.1]

12 249 ms 268 ms 271 ms pair-gw.customer.alter.net [157.130.48.162]

13 265 ms 233 ms 240 ms 192.168.1.5

14 239 ms 264 ms 251 ms regedit.com [209.197.107.91]



Trace complete.

As a side note the reason why you couldn't ping me is that I don't leave my computer on 24/7 I'm one of those users who believes in turning his computer off when I don't use it.

[POBrien]

The ping results show us that you are not dropping packets (at a router).

Pinging regedit.com [209.197.107.91] with 32 bytes of data:



Reply from 209.197.107.91: bytes=32 time=171ms TTL=243

Reply from 209.197.107.91: bytes=32 time=180ms TTL=243

Reply from 209.197.107.91: bytes=32 time=165ms TTL=243

Reply from 209.197.107.91: bytes=32 time=176ms TTL=243



Ping statistics for 209.197.107.91:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 165ms, Maximum = 180ms, Average = 173ms


The problem is latency. you can see
that getting to hop #6 is taking a long time


-->Trace Route Results:



Tracing route to regedit.com [209.197.107.91]

over a maximum of 30 hops:



1 61 ms 62 ms 112 ms HSE-Toronto-ppp289002.sympatico.ca [64.231.19.1]

2 55 ms 54 ms 54 ms dis21-toronto63-fe0-1-0.in.bellnexxia.net [206.108.106.33]

3 60 ms 57 ms 56 ms core2-toronto63-pos11-12.in.bellnexxia.net [206.108.98.213]

4 97 ms 96 ms 95 ms core1-chicago23-pos3-0.in.bellnexxia.net [206.108.103.130]

5 101 ms 102 ms 99 ms bx1-chicago23-pos10-0.in.bellnexxia.net [206.108.103.142]

6 234 ms 222 ms 212 ms 500.POS5-0-0.GW5.CHI6.ALTER.NET [157.130.107.113]

7 216 ms 219 ms 222 ms 116.ATM2-0.XR1.CHI6.ALTER.NET [146.188.209.154]

8 211 ms 215 ms 214 ms 191.at-1-1-0.TR1.CHI4.ALTER.NET [146.188.208.242]

9 427 ms 440 ms 411 ms 106.at-7-0-0.TR2.DCA8.ALTER.NET [146.188.138.178]

10 432 ms 432 ms 432 ms 197.at-5-0-0.XR1.TCO1.ALTER.NET [152.63.32.189]

11 432 ms * * 193.ATM6-0.GW3.PIT1.ALTER.NET [152.63.37.1]

12 249 ms 268 ms 271 ms pair-gw.customer.alter.net [157.130.48.162]

13 265 ms 233 ms 240 ms 192.168.1.5

14 239 ms 264 ms 251 ms regedit.com [209.197.107.91]



Trace complete.


Your Millisecond (ms) results should be anywhere from starting at 10 and ending at 100 (destination) for a decent route.

here's my results...

Tracing route to regedit.com [209.197.107.91]

over a maximum of 30 hops:



1 20 ms 20 ms 30 ms adsl-63-205-228-254.dsl.snfc21.pacbell.net [63.205.228.254]

2 10 ms 20 ms 10 ms core3-g2-0.snfc21.pbi.net [206.171.134.130]

3 10 ms 20 ms 10 ms edge1-ge1-0.snfc21.pbi.net [209.232.130.20]

4 10 ms 20 ms 20 ms sl-gw25-stk-8-3.sprintlink.net [160.81.16.21]

5 10 ms 20 ms 20 ms sl-bb20-stk-5-2.sprintlink.net [144.232.4.217]

6 20 ms 20 ms 20 ms sl-bb21-sj-9-0.sprintlink.net [144.232.9.165]

7 10 ms 20 ms 20 ms sl-bb20-sj-14-0.sprintlink.net [144.232.3.157]

8 70 ms 80 ms 70 ms sl-bb22-rly-12-0.sprintlink.net [144.232.9.217]

9 70 ms 80 ms 70 ms sl-gw8-rly-4-0-0.sprintlink.net [144.232.7.246]

10 80 ms 81 ms 80 ms sl-pairnet-1-0-0.sprintlink.net [144.232.190.142]

11 80 ms 80 ms 90 ms 192.168.1.5

12 80 ms 80 ms 91 ms registry.winguides.com [209.197.107.91]



Trace complete.




you can see that hop #8 is the culprit for me.


8 70 ms 80 ms 70 ms sl-bb22-rly-12-0.sprintlink.net [144.232.9.217]



You can see yours gets even worse at hop#9.

9 427 ms 440 ms 411 ms 106.at-7-0-0.TR2.DCA8.ALTER.NET [146.188.138.178]

Your ISP uses ALTER.NET as it's main backbone to route it's customers to the internet.

Ping to other sites to re-verify the latency.

Contact your ISP (talk to someone in Tier 2 or 3). Send them your results. Believe me their Wan admins already know that this latency is occuring.

As a matter of fact your trace times through your own ISP core routers isn't great either.

You can see mine are all in the 10's 20's then I hit Sprintlink (my ISP's backbone) and all is well until hop #8.

80's not too bad. however, if I had your number's i'd be calling them.

Also, gamers would have a fit. Their a demanding lot. It's no fun watching your screen slow down while your opponent is attacking only to then speed up and see that you've been obliterated.