View Full Version : packetloss on my first hop.
Basically for the past two days my internet connection has been slower than dial-up.....It took me an actual hour to register here due to loading speeds this is how bad the problem is. I have over 75% packetloss and the first hop on my tracert produces packetloss.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user1>tracert www.virginmedia.com
Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:
1 * * 7 ms 10.63.56.1
2 10 ms 9 ms 10 ms osr01king-v11.network.virginmedia.net [62.30.193
.161]
3 19 ms 18 ms * osr01perr-tenge73.network.virginmedia.net [62.30
.247.69]
4 8 ms 6 ms 8 ms perr-t3core-1a-ge-010-0.network.virginmedia.net
[80.0.176.69]
5 * 11 ms 13 ms man-bb-a-as1-0.network.virginmedia.net [213.105.
175.181]
6 24 ms 16 ms 18 ms gfd-bb-b-ae1-0.network.virginmedia.net [213.105.
175.146]
7 25 ms * 14 ms win-bb-a-so-010-0.network.virginmedia.net [213.1
05.172.129]
8 14 ms 15 ms 16 ms win-dc-a-v900.network.virginmedia.net [62.253.18
8.162]
9 15 ms 15 ms 13 ms www.virginmedia.com [212.250.162.12]
Trace complete.
Now I do understand when my first hop has packetloss it means the problem is on my end? Well I don't see how it possibly can be. I've scanned all my computer for ad-aware/spyware/viruses basically anything you can think of and nothing came up, my P.C speed is fine. It's not a NIC problem as I switched from Ethernet to USB and I'm still getting this horrendous packetloss. All external hardware is plugged in properly and thoroughly. Also I don't see how it's external as the lag fluctuates...for 5 hours it's none stop packetloss then for a good 10-15 minutes everything seems fine again and it just fluctuates like this for the past two days...it's unbareable now and I'm pretty much on the point where I'm just going to switch providors as I've had 100s of problems with this connection over 2 years it's just not reliable what so ever.
Here's my signal specs.
Frequency 331000000 Hz Locked
Signal to Noise Ratio 38 dB
Power Level -2 dB
Upstream Value
Channel ID 1
Frequency 22200000 Hz Ranged
Power Level 43 dBmV
Help/opinions greatly appreciated....this is just really frustrating.
homealone
07-06-2009, 00:43
:welcome:
I'm by no means an expert on these things, but I can't see any evidence for packet loss on the trace you provided.
- the time-outs on the first hop are more likely to be the UBR dropping ICMP requests, rather than packet loss - especially when the final hop shows such a good result.
Your power levels also look fine.
Personally I would revert to the ethernet connection, rather than USB, as that is usually more reliable....
:welcome:
I'm by no means an expert on these things, but I can't see any evidence for packet loss on the trace you provided.
- the time-outs on the first hop are more likely to be the UBR dropping ICMP requests, rather than packet loss - especially when the final hop shows such a good result.
Your power levels also look fine.
Personally I would revert to the ethernet connection, rather than USB, as that is usually more reliable....
Yeah I'm using ethernet now but I am getting horrendous packetloss....on my gaming server I freeze for over 30 seconds yet everyone around me is still moving/speaking and I can't move. Webpages are loading like dial-up speed and sometimes they just don't even load. So there's definatly some packetloss on my connection it's been like this for 2 days now here's the trace route for my gaming server.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user1>tracert jaguar.defianceuo.com
Tracing route to jaguar.defianceuo.com [193.192.51.4]
over a maximum of 30 hops:
1 6 ms 7 ms 7 ms 10.63.56.1
2 7 ms * 9 ms osr01king-v11.network.virginmedia.net [62.30.193
.161]
3 8 ms 7 ms 7 ms osr02perr-tenge73.network.virginmedia.net [62.30
.247.93]
4 * 10 ms 9 ms perr-t3core-1b-ge-010-0.network.virginmedia.net
[80.0.176.129]
5 8 ms 12 ms 7 ms bir-bb-b-as0-0.network.virginmedia.net [213.105.
175.185]
6 8 ms * 19 ms nth-bb-a-so-100-0.network.virginmedia.net [62.25
3.185.105]
7 14 ms 11 ms 11 ms nth-bb-b-ae0-0.network.virginmedia.net [62.253.1
85.118]
8 19 ms 16 ms * tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
9 * 15 ms 14 ms ae0-1234.rt2.the.uk.goscomb.net [195.66.224.226]
10 16 ms 16 ms 16 ms ae0-1624.rt0.sov.uk.goscomb.net [77.75.109.162]
11 45 ms 14 ms 14 ms berkeley-it-117.gw.goscomb.net [77.75.104.117]
12 14 ms 17 ms 17 ms fa0-0-509.cr1.iph.as35485.net [193.192.50.181]
13 15 ms 15 ms 16 ms jaguar.defianceuo.com [193.192.51.4]
Trace complete.
Honestly loading webpages is near impossible it'll take me about 10 tries just to post this message and the packetloss I'm experiencing on gaming servers aswell leads me to believe there's definatly a problem here....and it's been like this for 48 hours as I've mentioned many times.
homealone
07-06-2009, 01:02
Yeah I'm using ethernet now but I am getting horrendous packetloss....on my gaming server I freeze for over 30 seconds yet everyone around me is still moving/speaking and I can't move. Webpages are loading like dial-up speed and sometimes they just don't even load. So there's definatly some packetloss on my connection it's been like this for 2 days now here's the trace route for my gaming server.
Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.
C:\Documents and Settings\user1>tracert jaguar.defianceuo.com
Tracing route to jaguar.defianceuo.com [193.192.51.4]
over a maximum of 30 hops:
1 6 ms 7 ms 7 ms 10.63.56.1
2 7 ms * 9 ms osr01king-v11.network.virginmedia.net [62.30.193
.161]
3 8 ms 7 ms 7 ms osr02perr-tenge73.network.virginmedia.net [62.30
.247.93]
4 * 10 ms 9 ms perr-t3core-1b-ge-010-0.network.virginmedia.net
[80.0.176.129]
5 8 ms 12 ms 7 ms bir-bb-b-as0-0.network.virginmedia.net [213.105.
175.185]
6 8 ms * 19 ms nth-bb-a-so-100-0.network.virginmedia.net [62.25
3.185.105]
7 14 ms 11 ms 11 ms nth-bb-b-ae0-0.network.virginmedia.net [62.253.1
85.118]
8 19 ms 16 ms * tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
9 * 15 ms 14 ms ae0-1234.rt2.the.uk.goscomb.net [195.66.224.226]
10 16 ms 16 ms 16 ms ae0-1624.rt0.sov.uk.goscomb.net [77.75.109.162]
11 45 ms 14 ms 14 ms berkeley-it-117.gw.goscomb.net [77.75.104.117]
12 14 ms 17 ms 17 ms fa0-0-509.cr1.iph.as35485.net [193.192.50.181]
13 15 ms 15 ms 16 ms jaguar.defianceuo.com [193.192.51.4]
Trace complete.
Honestly loading webpages is near impossible it'll take me about 10 tries just to post this message and the packetloss I'm experiencing on gaming servers aswell leads me to believe there's definatly a problem here....and it's been like this for 48 hours as I've mentioned many times.
in my opinion there is no evidence of packet loss in that trace ???
Well if there isn't I'm still experiencing it...I'm still freezing on that gaming server right now and webpages are taking ages to load. Not sure why it isn't showing on the tests I post. It has improved some what in the last hour or so but it's still way below average.
---------- Post added at 01:10 ---------- Previous post was at 01:07 ----------
Request timed out.
Reply from 193.192.51.4: bytes=32 time=22ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=16ms TTL=118
Ping statistics for 193.192.51.4:
Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),
Approximate round trip times in milli-seconds:
Minimum = 16ms, Maximum = 22ms, Average = 19ms
C:\Documents and Settings\user1>
Quit ping test I did.
homealone
07-06-2009, 01:13
Well if there isn't I'm still experiencing it...I'm still freezing on that gaming server right now and webpages are taking ages to load. Not sure why it isn't showing on the tests I post. It has improved some what in the last hour or so but it's still way below average.
the only important hop on a traceroute is the last one, the traces you have posted show no problems at all with that - in fact at 15ms or so the returns are really fast.
I wish I could be more helpful, but just laying all the blame at 'packet loss' doesn't seem to scope your problem ???
<edit> the ping test would seem to support your theory more - I'm stumped, sorry ..
the only important hop on a traceroute is the last one, the traces you have posted show no problems at all with that - in fact at 15ms or so the returns are really fast.
I wish I could be more helpful, but just laying all the blame at 'packet loss' doesn't seem to scope your problem ???
I have 0 idea on what it is then? Slow connection speed, slow loading times and inexplicable freezing on different gaming servers. Any ideas what it actually is then?
homealone
07-06-2009, 01:20
I have 0 idea on what it is then? Slow connection speed, slow loading times and inexplicable freezing on different gaming servers. Any ideas what it actually is then?
I wish I did, sorry :(
NorthPlum
07-06-2009, 01:20
Are you connected via router?
Are you connected via router?
Yeah, Motorola Surfboard.
NorthPlum
07-06-2009, 01:27
Yeah, Motorola Surfboard.
Disconnect it for ten - twenty seconds then re-connect it. (Unplug the power)
I had a similar problem and it fixed it.
Not a definite fix, but all I can suggest.
Disconnect it for ten - twenty seconds then re-connect it. (Unplug the power)
I had a similar problem and it fixed it.
Not a definite fix, but all I can suggest.
Yeah tried it to no avail, thanks anyways.
Depending on how your ISP has configured their routers you may find they give responding to ICMP traffic a very low prority as they are configured to instead work on routing traffic to the next hop.
There is a way to tracert using TCP SYN packets but unfortunately i've not yet found a good tool to do it on a windows based system. :confused: for line the command is tcptraceroute but you usually have to download it first again it will depend on how the router is configured.
The only hop that actually matters in the final, although your ping shows a possible PL issue, it might be worth doing some more pings try ping -n 50 193.192.51.4 (if this is the ip you want to ping)
This will ping it 50x instead of 4 and might be more usefull.
Request timed out.
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=16ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=18ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=17ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=16ms TTL=118
Reply from 193.192.51.4: bytes=32 time=16ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Request timed out.
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=15ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Reply from 193.192.51.4: bytes=32 time=14ms TTL=118
Ping statistics for 193.192.51.4:
Packets: Sent = 50, Received = 38, Lost = 12 (24% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 18ms, Average = 15ms
C:\Documents and Settings\user1>
Nasty :(
Do you get PL to other destinations as well?
Are you connected directly to the modem or via a router?, also do you have some kind of secuirty software like a firewall/virus scanner on the machine, maybe it's filtering driver got corrupted and needs reinstalling.
Nasty :(
Do you get PL to other destinations as well?
Are you connected directly to the modem or via a router?, also do you have some kind of secuirty software like a firewall/virus scanner on the machine, maybe it's filtering driver got corrupted and needs reinstalling.
No active firewall or scanner. Yeah I get PL to everything. My computers actually fine right now, 0 packetloss but I can guarentee you in about 2-3 hours it comes back for the rest of the day. I'm connected via router.
No active firewall or scanner. Yeah I get PL to everything. My computers actually fine right now, 0 packetloss but I can guarentee you in about 2-3 hours it comes back for the rest of the day. I'm connected via router.
Try connecting directly just in case its the router, but I suspect not.
Is it during peak hours?
Try connecting directly just in case its the router, but I suspect not.
Is it during peak hours?
Yeah I tried connecting directly, same problem.
Yeah it usually starts around 1-3pm and doesn't stop till about 9-11.30pm.
TeDect, if you read around this forum and the newsgroup you'll see that the Virgin network is in a mess at the moment for a lot of users and will probably remain so until the 50Mb switchover is complete. I'm surprised there's not been a sticky thread added to this forum yet. VM sealed their own fate from the point at which they decided to plough through the 50Mb upgrade like a bull at a gate and leave existing customers high and dry.
10% packet loss if the norm for me now and speeds vary between 200Kb and 2Mb (and I'm on 20Mb package) and Virgin have point blank refused to do anything about it even though they admit there is a network problem that needs fixing.
TeDect, if you read around this forum and the newsgroup you'll see that the Virgin network is in a mess at the moment for a lot of users and will probably remain so until the 50Mb switchover is complete. I'm surprised there's not been a sticky thread added to this forum yet. VM sealed their own fate from the point at which they decided to plough through the 50Mb upgrade like a bull at a gate and leave existing customers high and dry.
10% packet loss if the norm for me now and speeds vary between 200Kb and 2Mb (and I'm on 20Mb package) and Virgin have point blank refused to do anything about it even though they admit there is a network problem that needs fixing.
Yeah, time to switch ISPs then. Not worth the hassel if this is the case.
vBulletin® v3.8.11, Copyright ©2000-2024, vBulletin Solutions Inc.