next »

[Please Support Us!]

Please Support Us!

Please help keep (=WDG=) alive

• Server rules
• Forum rules
• Join us
  
• Clan members
• About the clan
• Server stats
• WDG YouTube Channel
• WDG Downloads
• IRC Webchat

Steam groups:

• WDG community
• WDG clan group
• WDG Battlelog Platoon

Our allies:

• [NuB] TF2 clan
• Velocity Gamers Hub
• Destination Gamer

GoG Links:

• Wix Discord
• Wix IRC channel

TF2 Links:

• Official TF2 Blog
• TF2 Steam Forum
• The Fort 2

October 2025

Mo	Tu	We	Th	Fr	Sa	Su
		1	2	3	4	5
6	7	8	9	10	11	12
13	14	15	16	17	18	19
20	21	22	23	24	25	26
27	28	29	30	31
	Birthdays
Chaos (40)
	Upcoming Events
Upcoming Birthdays: Chaos (40)

[Power]

Right, if you use a normal networking cable directly with the modem, the internet doesn't work, that's why you need a crossover cable (usually yellow, are you sure you didn't get one delivered with the modem?).

All signs point to the modem so far, but you'll probably be better off ringing up Virgin and asking them to check the line from their end as well.

[claws]

I'm wondering if it's an SNR issue and the modem is internally freaking out, or whether it's gone faulty. If it were me I'd be tempted to try the virgin media forums (i'd probably also check the logs on the v router). Don't really have any other sensible suggestions, sorry

[Chaos]

I might have a Virgin Modem and a Cable Router I could send to you for testing mate.. you'd have to send it back though

Router cost like £180

[Cheez]

Just ran a trace route to the same ip:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Sam>tracert 81.19.221.201

Tracing route to ne1.nervousenergy.co.uk [81.19.221.201]
over a maximum of 30 hops:

  1     1 ms    <1 ms    <1 ms  192.168.1.1
  2    15 ms    35 ms    20 ms  10.11.68.1
  3    59 ms    44 ms    76 ms  aztw-geam-1b-ge142.network.virginmedia.net [80.1
.243.153]
  4    81 ms    33 ms    15 ms  aztw-core-1b-ae0-0.network.virginmedia.net [80.1
.241.13]
  5    70 ms    29 ms    39 ms  brhm-bb-1b-as1-0.network.virginmedia.net [213.10
5.175.161]
  6    22 ms    91 ms    70 ms  winn-bb-1a-so-220-0.network.virginmedia.net [62.
253.188.145]
  7    19 ms    37 ms    26 ms  popl-bb-1b-as5-0.network.virginmedia.net [212.43
.162.194]
  8    31 ms    12 ms    30 ms  popl-tmr-2-ae5-0.network.virginmedia.net [213.10
5.159.6]
  9    18 ms    43 ms    19 ms  tele-ic-2-as0-0.network.virginmedia.net [62.253.
184.6]
 10    15 ms    26 ms    17 ms  ntl.killercreation.co.uk [212.250.14.18]
 11    19 ms    17 ms    37 ms  rt-2-cent.killercreation.co.uk [217.146.94.2]
 12    14 ms    16 ms    18 ms  ne1.nervousenergy.co.uk [81.19.221.201]

Trace complete.

Does this conclude that it must be virgin fucking me over by throttling me?

[Junta]

Need that router back Sam? Happy to oblige for testing....

[Power]

I'm not sure if throttling would actually have any effect on your ping, it's more about the bandwidth than the response times. But apparently it is a problem with the line indeed...

[Zarf]

Hop 2 looks terrible : that's an internal address. How are you connected to your router, what kind of router is it, etc.

VM use the 10.x.x.x private address range for their internal routers. It's not his modem (should be able to access modem stats on 192.168.100.1 iirc, I had to use IE to view the page properly when I had one)

Final destination pings are what to look at, The pings being higher / dropped in the intermediate nodes isn't as significant as it seems, ISPs set ping responses on their routers to be a very low CPU priority so tracerts aren't as easy to interpret as they once were. What it does indicate is that the routers are running at close to capacity. I'd say it's a simple case of over subscription in your area due to the holidays. Not much you can do really.

[Cheez]

Need that router back Sam? Happy to oblige for testing....

Cheers for the offer mate but I have a similar netgear I can use to test now.

Zarf, that sounds about right mate You think upgrading to the 50mb package would help (been considering doing it for a while as it won't be much more with 5 of us paying).

[Nineblade]

I presume you've checked for kinks in the ethernet cable?

[Zarf]

Need that router back Sam? Happy to oblige for testing....

Cheers for the offer mate but I have a similar netgear I can use to test now.

Zarf, that sounds about right mate You think upgrading to the 50mb package would help (been considering doing it for a while as it won't be much more with 5 of us paying).

Yeah, it's definitely worth it amongst that many people, Think there is even a 100Mb package out now for not much more than the 50Mb. You get much better daytime caps and upload increase too which comes in handy when there are 5 people sharing the connection. Only takes someone uploading a photo album or youtube video to slow things down for everyone.

From what I understand the 20Mb and 10Mb products use a different network - DOCSIS 1.1 vs the DOCSIS 3.0 network for 50Mb+, I don't know enough about how VM have their infrastructure set up to confirm if it makes a difference, but forums consensus seems to be that one network can be congested for an area whilst the other isn't.

[Mr Chug]

Hijacking this.

I was having some ping troubles on the server last night, which puzzled me on the grounds that in the server browser I was getting normal 20-50 pings. Once connected to any server, however, my ping ranged from 80-200, and was generally warpy as hell. Again, if I disconnected I was fine, and if I looked at the server details (through someone else's game info in the steam overlay) it claimed I was getting normal ping. A look on the O2 forums revealed no complaints, and a google search about it didn't throw up nearly enough results for it to be widespread. Initially I thought it might be a busy exchange but that's excluded by normal pings in the server browser (when I had ping issues last year the server browser reflected that). It doesn't seem to be throttling, as while O2 do traffic shaping at peak times this a) normally doesn't affect my ping and b) trying it this morning well out of peak time gave the same result.

A clue might be in my stats; here's a ping followed by a tracert:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\Matt>ping wdgclan.co.uk

Pinging wdgclan.co.uk [82.165.207.9] with 32 bytes of data:
Reply from 82.165.207.9: bytes=32 time=34ms TTL=57
Reply from 82.165.207.9: bytes=32 time=33ms TTL=57
Reply from 82.165.207.9: bytes=32 time=36ms TTL=57
Reply from 82.165.207.9: bytes=32 time=37ms TTL=57

Ping statistics for 82.165.207.9:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 33ms, Maximum = 37ms, Average = 35ms

C:\Users\Matt>tracert wdgclan.co.uk

Tracing route to wdgclan.co.uk [82.165.207.9]
over a maximum of 30 hops:

  1    54 ms    87 ms    99 ms  O2WirelessBox.lan [192.168.1.254]
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4    94 ms    70 ms    76 ms  linx.bb-c.the.lon.gb.oneandone.net [195.66.224.98]
  5    80 ms    74 ms    60 ms  te-1-3.bb-c.bap.rhr.de.oneandone.net [212.227.120.49]
  6   118 ms    77 ms    81 ms  ae-5.gw-dista-a.bap.rhr.de.oneandone.net [212.227.122.1]
  7     *      143 ms    80 ms  vl-1991.gw-ps11.bap.rhr.de.oneandone.net [217.160.127.79]
  8     *      155 ms    71 ms  kundenserver.de [82.165.207.9]

Trace complete.

I get the same sort of thing regardless of where I ping to (including bbc, google, ne, etc).

It's the same on all my housemates', and none of us are downloading anything at the time. Connection speed is usual. Any ideas?

[DeadlyAvenger]

1    54 ms    87 ms    99 ms  O2WirelessBox.lan [192.168.1.254]

Is that a fairly consistent time? That would explain your lag if it takes 100 ms to ping your router. Have you tried just pinging your router (192.168.1.254) to see if it always gives you that kind of time? To a router should be <5ms (and that's a conservative estimate) so if you're getting 100ms I'd think there was something wrong between your pc and the router.

[Mr Chug]

C:\Users\Matt>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=5ms TTL=64
Request timed out.
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=248ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 248ms, Average = 85ms

C:\Users\Matt>ping 192.168.1.254

Pinging 192.168.1.254 with 32 bytes of data:
Reply from 192.168.1.254: bytes=32 time=7ms TTL=64
Reply from 192.168.1.254: bytes=32 time=2ms TTL=64
Reply from 192.168.1.254: bytes=32 time=90ms TTL=64
Reply from 192.168.1.254: bytes=32 time=7ms TTL=64

Ping statistics for 192.168.1.254:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 2ms, Maximum = 90ms, Average = 26ms

Always ends up something like that.

[CruelCow]

That's pretty bad. (You're not using wireless right?)

Try resetting the router

[Mr Chug]

I'm on wireless out of necessity (read: don't want to have to run a 15m cable through the entire house) but never had issues like this before. Resetting router didn't work last night, will warn my housemates and try again in a bit.

The only thing I can think of that's different since before Christmas is that our boiler's broken, but doesn't seem like the sort of issue to cause the same issue in the entire house.