Frustrating connection problems in Lincoln/Newark/Notts area

[BuckoA51]

Hi everyone

This is my first post, I have been referred here from the official Xbox forums where I first posted about this issue.

This sorry story begins over a year ago, I started having Xbox live connectivity issues with certain friends. Whenever I tried to play them at a game or private chat with them the connection would just fail, or not let me join their game.

Each time I tried technical support Microsoft came back blank. I believe with a bit of poking around however that the problem is actually Virgin Media.

A few months ago, the same friend wanted to share some files with me. We both work together in our spare time doing PC repair and he needed some files for an antivirus disk. I set up a FTP server using dydns so that changes in my IP address would not affect him. He phoned me back saying he could not connect. I moaned at him for not being able to do something as simple as FTP and drove over and lo and behold he could not connect to my FTP, at all (did not even ask him for his password etc)

I messaged my friend in Scotland, he could connect, I messaged a friend in America, he could connect, I tried from work, I could connect.

At this point, I began to suspect something was amiss with the internet connection. There is a command which you can execute in a command prompt (dos prompt) window called tracert. This command shows you how your packets are being routed across the internet. I opened up my router so that it would accept ping and tracert commands. Here's what happens when I try and tracert to my friend:-

Tracing route to [82.30.xxx.xxx] (Yes I AM sure that is his correct IP address)
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 10 ms 7 ms 10.62.192.1
3 10 ms 23 ms 13 ms nott-t2cam2-b-v638.network.virginmedia.net [82.13.49.169]
4 19 ms 9 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.

When he tries to tracert back to me, here's what happens:-

Tracing route to 82.21.xxx.xxx

1 4 ms <1 ms <1 ms 192.168.1.1
2 18 ms 6 ms 23 ms 10.225.204.1
3 46 ms 7 ms 10 ms nott-t2cam1-a-v158.network.virginmedia.net [80.4.46.81]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.

Again failing around the 4th hop which looks like it is a Virgin media router?!

I think this proves that Virgin Media has some connection issues, does it not?
It seems to be one or more routers/switches in Newark that is really having problems, particularly the router/switch at cpc1-nwrk2-0-0-cust202.nott.cable.ntl.com [82.28.224.203]. I cannot ping or tracert to this router and I'm guessing anyone who I must connect to through this router.

I tried phoning their technical support team, they basically fobbed me off saying it was my firewall and they could not help me. I threatened to cancel but bottled out since my family depends on the internet for so many things I would have to arrange a BT line installation before I turned off the cable.

Can anyone help me at all? Please?

EDIT - Forgot to say that I can tracert to my IP address (via my dydns) from my works internet connection just fine.

[Axegrinder]

My connection keeps dropping also, its like someone randomly turns off the DNS server for a couple of minutes. Very annoying.

[BuckoA51]

I don't think this is related to DNS. The connection fails regardless of whether I use my DynDns or not.

[rtj70]

Me too but it's normally the same website.... so thought they had the problem. But when it goes wrong it affects other sites too. Then they come back but the other takes a while.

[BuckoA51]

Yes my connection does that too actually. Are you in Lincoln or Newark too?

[rtj70]

No Stockport, although connection is via Baguley.

[Broken Hope]

Started having this problem myself but it's only began to happen in the past week or so but it's happened every single day, websites will all time out, or my browser will be unable to resolve the host name and my tracert's also seem to drop on the 4th hop

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 7 ms 7 ms 30 ms 10.139.0.1
2 7 ms 7 ms 6 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4.46.133]
3 7 ms 8 ms 7 ms nott-t3core-1b-ae2-0.network.virginmedia.net [195.182.174.238]
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * 13 ms www.virginmedia.com [212.250.162.12]

[BuckoA51]

What can we do? three of my friends are in Newark and this makes it impossible for me to play them on Xbox live. But try explaining this to tech support at virgin they just fob you off (especially if you mention live)

Broken Hope, can you ping or tracert to cpc1-nwrk2-0-0-custxxx.nott.cable.ntl.com [xx.xx.xxx.xxx] ?

[eth01]

PM me the IP.

[BuckoA51]

PM me the IP.

Of?

[eth01]

PM me the IP.

5 osr-hsd-gw3-tenge81.network.virginmedia.net (194.117.136.146) 8.242 ms
6 ge3-0.pr1.lhr1.uk.above.net (195.66.224.76) 64.686 ms
7 so-0-0-0.mpr1.lhr3.uk.above.net (64.125.27.226) 8.258 ms
8 213.152.245.54 (213.152.245.54) 13.522 ms
9 nott-t3core-1a-as0-0.network.virginmedia.net (213.105.174.170) 15.722 ms
10 nott-t2cam1-a-pc201.network.virginmedia.net (195.182.174.214) 15.620 ms
11 nott-nwrk-ubr-2-ge01.network.virginmedia.net (81.109.166.110) 16.470 ms
12 *
13 *
14 *
15 *
16 *
17 *

and

6 7 ms 27 ms 8 ms man-bb-a-ae0-0.network.virginmedia.net [62.253.187.177]
7 12 ms 13 ms 13 ms nth-bb-b-so-300-0.network.virginmedia.net [212.43.162.214]
8 14 ms 14 ms 16 ms nott-t3core-1b-as0-0.network.virginmedia.net [213.105.174.174]
9 14 ms 15 ms 17 ms nott-t2cam1-b-pc200.network.virginmedia.net [195.182.174.233]
10 20 ms 18 ms 17 ms nott-nwrk-ubr-2-ge02.network.virginmedia.net [81.109.166.234]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

nwrk ubr2 has routing problems, could be fluctuating SNR or a misconfiguration. but i'm rather unsure atm. i'll have this raised -- ref to follow.

[BuckoA51]

eth01 a little explanation as to what your doing here please? Also where are you based?

[eth01]

eth01 a little explanation as to what your doing here please? Also where are you based?

they're traceroutes within the VM network (whilst missing out some of the pointless stuff). Manchester way.

[BuckoA51]

Oh I see you work for Virgin Media? So you might actually get this sorted without telling me it's my fault? You're my hero lol :)

[eth01]

Oh I see you work for Virgin Media? So you might actually get this sorted without telling me it's my fault? You're my hero lol :)

it does look like it's something to do with the uBr, yes. what -- i don't know (yet)

[DJ_Nik_Gnashers]

Could this be causing my problem here in Lincoln ?
My upload speed suddenly dies from 490kbps down to 10kbps or less, even tho my download speed remains unaffected, been doing this for a week or so. New modem fitted thismorning by virgin engineer, speedtest showed normal speed, 10 mins after engineer left my upload died to 6kbps.

[Joxer]

We seem to be having a lot of routing issues lately.

Just out of interest can you run a trace from tools.virginmedia.com ?

[DJ_Nik_Gnashers]

Just ran tracert tools.virginmedia.com
10 hops all complete, 35ms was slowest.

[BuckoA51]

This isn't a recent problem for me, it has been like this for the better part of a year. Xmas was the last time I could definitely connect to my friend in Newark.

Tracing route to tools.virginmedia.com [62.30.31.87]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 56 ms 16 ms 7 ms 10.62.192.1
3 23 ms 33 ms 11 ms nott-t2cam2-b-v638.network.virginmedia.net [82.1
3.49.169]
4 13 ms 13 ms 11 ms nott-t3core-1b-ae3-0.network.virginmedia.net [19
5.182.175.141]
5 15 ms 16 ms 31 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
6 35 ms 17 ms 16 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
7 24 ms 18 ms 16 ms pop-bb-b-ae0-0.network.virginmedia.net [213.105.
174.230]
8 47 ms 28 ms 43 ms gsr-hsd-gw2-ge1000.network.virginmedia.net [213.
105.175.126]
9 43 ms 84 ms 78 ms gsr-hsd-gw1-pos00.network.virginmedia.net [194.1
17.136.173]
10 37 ms 63 ms 34 ms rabat-pos100.network.virginmedia.net [194.117.13
6.157]
11 39 ms 47 ms 53 ms 62.30.31.87

Trace complete.

[Joxer]

Does it work ok from there as well?

[Broken Hope]

5 osr-hsd-gw3-tenge81.network.virginmedia.net (194.117.136.146) 8.242 ms
6 ge3-0.pr1.lhr1.uk.above.net (195.66.224.76) 64.686 ms
7 so-0-0-0.mpr1.lhr3.uk.above.net (64.125.27.226) 8.258 ms
8 213.152.245.54 (213.152.245.54) 13.522 ms
9 nott-t3core-1a-as0-0.network.virginmedia.net (213.105.174.170) 15.722 ms
10 nott-t2cam1-a-pc201.network.virginmedia.net (195.182.174.214) 15.620 ms
11 nott-nwrk-ubr-2-ge01.network.virginmedia.net (81.109.166.110) 16.470 ms
12 *
13 *
14 *
15 *
16 *
17 *

and

6 7 ms 27 ms 8 ms man-bb-a-ae0-0.network.virginmedia.net [62.253.187.177]
7 12 ms 13 ms 13 ms nth-bb-b-so-300-0.network.virginmedia.net [212.43.162.214]
8 14 ms 14 ms 16 ms nott-t3core-1b-as0-0.network.virginmedia.net [213.105.174.174]
9 14 ms 15 ms 17 ms nott-t2cam1-b-pc200.network.virginmedia.net [195.182.174.233]
10 20 ms 18 ms 17 ms nott-nwrk-ubr-2-ge02.network.virginmedia.net [81.109.166.234]
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.

nwrk ubr2 has routing problems, could be fluctuating SNR or a misconfiguration. but i'm rather unsure atm. i'll have this raised -- ref to follow.

Any idea if Nottingham is having UBR problems also? The odd thing is in my case it will be fine for most of the day, then it will have problems for a short period of time and then it will fix itself and be fine for the rest of the day again.

Though yesterday when it happened I tried restarting the modem and it took about 10 minutes for the ready light to stop flashing.

[BuckoA51]

Does it work ok from there as well?

From my friend in Newark? Yes he says tracert gets through ok to tools.virginmedia.com

[Joxer]

Sorry if you go to the webpage tool.virginmedia.com - it allows you, among other things, to run a traceroute - does that work ok (to you own ip)? It probably will if you can trace to it but worth a try.

[BuckoA51]

Joxer - The trace seems to fail.

1 62.30.31.130 (62.30.31.130) 0.676 ms
2 194.117.133.226 (194.117.133.226) 0.726 ms
3 rabat-pos150.network.virginmedia.net (194.117.136.178) 8.370 ms
4 gsr-hsd-gw1-pos60.network.virginmedia.net (194.117.136.158) 8.352 ms
5 osr-hsd-gw3-tenge81.network.virginmedia.net (194.117.136.146) 8.199 ms
6 ge3-0.pr1.lhr1.uk.above.net (195.66.224.76) 9.405 ms
7 so-1-0-0.mpr2.ams5.nl.above.net (64.125.27.178) 21.848 ms
8 so-0-0-0.mpr1.ams1.nl.above.net (64.125.26.45) 22.102 ms
9 213.152.245.50 (213.152.245.50) 20.485 ms
10 nth-bb-b-so-230-0.network.virginmedia.net (213.105.175.138) 22.507 ms
11 nott-t3core-1b-as0-0.network.virginmedia.net (213.105.174.174) 24.060 ms
12 nott-t2cam2-b-pc201.network.virginmedia.net (195.182.175.146) 24.198 ms
13 nott-linc-ubr-7-ge02.network.virginmedia.net (82.13.49.170) 28.044 ms
14 *
15 *
16 *

etc

---------- Post added at 14:12 ---------- Previous post was at 14:10 ----------

My friend in Newark was online too, I got him to try it from his end:-

11 nott-nwrk-ubr-2-ge01.network.virginmedia.net (81.109.166.110) 16.398 ms
12 *
13 *

etc etc

Note - Can't be sure my friend has set his router up to accept traceroutes though.

[eth01]

Joxer - The trace seems to fail.

1 62.30.31.130 (62.30.31.130) 0.676 ms
2 194.117.133.226 (194.117.133.226) 0.726 ms
3 rabat-pos150.network.virginmedia.net (194.117.136.178) 8.370 ms
4 gsr-hsd-gw1-pos60.network.virginmedia.net (194.117.136.158) 8.352 ms
5 osr-hsd-gw3-tenge81.network.virginmedia.net (194.117.136.146) 8.199 ms
6 ge3-0.pr1.lhr1.uk.above.net (195.66.224.76) 9.405 ms
7 so-1-0-0.mpr2.ams5.nl.above.net (64.125.27.178) 21.848 ms
8 so-0-0-0.mpr1.ams1.nl.above.net (64.125.26.45) 22.102 ms
9 213.152.245.50 (213.152.245.50) 20.485 ms
10 nth-bb-b-so-230-0.network.virginmedia.net (213.105.175.138) 22.507 ms
11 nott-t3core-1b-as0-0.network.virginmedia.net (213.105.174.174) 24.060 ms
12 nott-t2cam2-b-pc201.network.virginmedia.net (195.182.175.146) 24.198 ms
13 nott-linc-ubr-7-ge02.network.virginmedia.net (82.13.49.170) 28.044 ms
14 *
15 *
16 *

etc

---------- Post added at 14:12 ---------- Previous post was at 14:10 ----------

My friend in Newark was online too, I got him to try it from his end:-

11 nott-nwrk-ubr-2-ge01.network.virginmedia.net (81.109.166.110) 16.398 ms
12 *
13 *

etc etc

Note - Can't be sure my friend has set his router up to accept traceroutes though.

I suggest your friend resets his router to factory defaults or just buys another... either way... it's leaving the VM network fine... (however, please ask him to call TS on 151)

[BuckoA51]

Lol now you sound like a Virgin Media employee :)

It's probably just blocking the tracert, many routers do that by default

[Joxer]

Hmm, could still be your router blocking it I think that site uses UDP based traces rather than icmp based so might stil be blocked, you could try here http://member.dnsstuff.com/pages/tools.php?ptype=free it runs icmp tcp and udp traces - we were using it so much at work they banned us. :-)

[eth01]

Lol now you sound like a Virgin Media employee :)

It's probably just blocking the tracert, many routers do that by default

It does not matter whether i'm a "Virgin Media employee" or not -- the point is, this is a problem related to the router itself IMO and not VM... Like I told you, get him to call TS on 151 just to double check. ;)

[BuckoA51]

I thought you said earlier this was definitely a Virgin Media issue :( "nwrk ubr2 has routing problems" you said, now it's back to blaming my router :(

There's no way we're ringing tech support, they won't have a clue what we are talking about. I need to go back to work and make sure I can traceroute him from there. *sigh*

Joxer - Tried tracing my IP address from your link, got through to me fine.

[Joxer]

Cool, on all 3 traces? if so you can call tech support and get them to run it and the one from virginmedia and maybe www.iptools.com and there you have proof of network issues.

[eth01]

I thought you said earlier this was definitely a Virgin Media issue :( "nwrk ubr2 has routing problems" you said, now it's back to blaming my router :(

There's no way we're ringing tech support, they won't have a clue what we are talking about. I need to go back to work and make sure I can traceroute him from there. *sigh*

Joxer - Tried tracing my IP address from your link, got through to me fine.

Don't be so stereotypical. Extensive tests were performed to give nothing.

[BuckoA51]

"Cool, on all 3 traces? if so you can call tech support and get them to run it and the one from virginmedia and maybe www.iptools.com and there you have proof of network issues."

No, only T1

"Don't be so stereotypical. Extensive tests were performed to give nothing."

Sorry I don't understand

Would it help if I plugged my cable modem directly into my PC and did the tests again?

[Joxer]

It looks like something (probably your router) is blocking udp basedx traces so that is why the trace from tools.virginmedia.com is failing it runs on a unix based server and therefore probably uses UDP based traces. Testing direct to the modem will help or put you pc in a DMZ on your router if you can.

[BuckoA51]

Ok I will have a look at my router settings and try direct to my cable modem if I can't see anything but I will have to wait because others in the house are using the net at the moment.

I still don't see how this problem can be my router when everyone but 2 people in Newark can connect and ping and tracert to me, but I understand we need to eliminate all possibilities.

---------- Post added at 15:34 ---------- Previous post was at 15:25 ----------

Sucess! Turning the firewall off in my router and now I can traceroute from tools.virginmedia.com

Still having the connection problems with Newark though!

[Joxer]

Darn, I was hoping it would fail - gives you something to take to tech support - but at least you can use it to prove nothing your end blocking the connection. the original trace you posted is that from you friends place or your own? If he still can't ping you you'll need someone from 2nd line to log on to either ubr and try to ping the other one or the modem and get the same result you are to get it raised up as a fault. You'll need something to bring up your friends account or the ubr they are on (the connection link at the top of the page will do that) but the modem mac would be handy (DO NOT post that here).

[BuckoA51]

First trace was me to him, then next him to me. I guess me to him might fail anyway since his router could be blocking.

He still can't ping, tracert FTP or Xbox live to me.

I have two friends in Newark with the same issue.

[Ignitionnet]

At the time those original traces were made it pointed to an issue between

3 46 ms 7 ms 10 ms nott-t2cam1-a-v158.network.virginmedia.net [80.4.46.81]

and

4 19 ms 9 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]

This is where the traceroutes died, looks as though t2cam1-a isn't getting the route for that IP range, 82.30.xxx.xxx from the core which is why it went so far in one direction, used default routes, but had no return path.

Fluctuating SNR on the cable modem or w/e is irrelevant the uBRs advertise the entire IP scopes to the t2cams so even if an individual modem is offline a traceroute should get to the uBR.

Suggest that someone checks out the configs and routing tables on both t2cams.

Another traceroute showed a bit of a mess as well:

5 osr-hsd-gw3-tenge81.network.virginmedia.net (194.117.136.146) 8.242 ms << Ex Telewest
6 ge3-0.pr1.lhr1.uk.above.net (195.66.224.76) 64.686 ms << Erm, Above.net?!
7 so-0-0-0.mpr1.lhr3.uk.above.net (64.125.27.226) 8.258 ms
8 213.152.245.54 (213.152.245.54) 13.522 ms << Ex-ntl
9 nott-t3core-1a-as0-0.network.virginmedia.net (213.105.174.170) 15.722 ms
10 nott-t2cam1-a-pc201.network.virginmedia.net (195.182.174.214) 15.620 ms
11 nott-nwrk-ubr-2-ge01.network.virginmedia.net (81.109.166.110) 16.470 ms

It looks as though Virgin Media are using 3rd party transit from Above.net to link the ex-Telewest and ex-ntl networks. Interesting.

[BuckoA51]

what should I do? I was going to make sure I can traceroute and ping my friend and myself from my work connection and from the tools.virginmedia.com site to prove our connections are open.

Then traceroute ping each other to prove that that does not work... then, ask Virgin to send an engineer?

[Ignitionnet]

what should I do? I was going to make sure I can traceroute and ping my friend and myself from my work connection and from the tools.virginmedia.com site to prove our connections are open.

Then traceroute ping each other to prove that that does not work... then, ask Virgin to send an engineer?

An engineer isn't going to be able to do anything, it seems like a core network issue.

Unfortunately you need to find someone who understands the fault and will escalate it to VM's NMC. It's a very specific fault that you on your Lincoln uBR cannot contact your mate on that Newark uBR so investigation needs doing on the t2cam routers those uBRs hook up to to confirm what routes they are both advertising, then in turn the routes they are receiving.

[BuckoA51]

"An engineer isn't going to be able to do anything, it seems like a core network issue."

An engineer might at least believe me unlike the tech support people who probably won't.

What does uBR mean btw?

[dafry]

bucko sent you a pm m8 :)

[Joxer]

I believe you - if you where on the phone to me I would have called 2nd line by now. You could try the newsgroups - that way you can copy and paste the traces - PITA doing that over the phone.

[BuckoA51]

OK well I'll try support again (dreading it) once I can confirm that both myself and my friend (hopefully both my friends) can be pinged/tracert'ed from my connection at work and on your tools.virginmedia site but not from each other.

[Ignitionnet]

"An engineer isn't going to be able to do anything, it seems like a core network issue."

An engineer might at least believe me unlike the tech support people who probably won't.

What does uBR mean btw?

universal Broadband Router in the case of Virgin Media apart from the new DOCSIS 3 kit the Cisco uBR7246VXR.

[BuckoA51]

Managed to get in touch with another friend from Newark, their tracert to me fails on the 3rd hop - nott-t2cam1-b-v158.network.virginmedia.net 80.4.46.213

This could be affecting lots of people who don't have the technical know-how to troubleshoot something like this..

Ooh and look what happens when I try and tracert to nott-t2cam1-b-v158.network.virginmedia.net 80.4.46.213:-

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 7 ms 12 ms 10.62.192.1
3 18 ms 18 ms 12 ms nott-t2cam2-b-v638.network.virginmedia.net [82.13.49.169]
4 10 ms 23 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
etc

[Broken Hope]

Having problems again today, appears to be packet loss, it's also causing extremely high latency in online games

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 33 ms 10 ms 35 ms 10.139.0.1
2 11 ms 8 ms 19 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4
.46.133]
3 * 9 ms * nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
4 32 ms 13 ms 22 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
5 16 ms 40 ms 15 ms pop-bb-a-so-100-0.network.virginmedia.net [213.1
05.172.14]
6 29 ms 22 ms 37 ms win-bb-b-so-010-0.network.virginmedia.net [62.25
3.185.202]
7 122 ms 102 ms 79 ms win-dc-b-v903.network.virginmedia.net [213.105.1
74.38]
8 * * * Request timed out.
9 * * * Request timed out.
10 14 ms 16 ms 16 ms www.virginmedia.com [212.250.162.12]

Trace complete.

[eth01]

Managed to get in touch with another friend from Newark, their tracert to me fails on the 3rd hop - nott-t2cam1-b-v158.network.virginmedia.net 80.4.46.213

This could be affecting lots of people who don't have the technical know-how to troubleshoot something like this..

Ooh and look what happens when I try and tracert to nott-t2cam1-b-v158.network.virginmedia.net 80.4.46.213:-

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 7 ms 12 ms 10.62.192.1
3 18 ms 18 ms 12 ms nott-t2cam2-b-v638.network.virginmedia.net [82.13.49.169]
4 10 ms 23 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
etc

it's leaving the VM network fine -- bottleneck involved somewhere?

[Ignitionnet]

Now now, extensive tests were performed to give nothing.

Sounds like t3cores struggle with that subnet generally. Not good.

Hopefully someone will push this to the right people who will actually understand the fault rather than apparently the wrong troubleshooting steps and a conclusion that makes no sense.

[eth01]

universal Broadband Router in the case of Virgin Media apart from the new DOCSIS 3 kit the Cisco uBR7246VXR.

what does docsis 3 have anything to do with this? you don't know which uBr's VM use either, why speculate?

[Ignitionnet]

it's leaving the VM network fine -- bottleneck involved somewhere?

....

Since when were the t3cores the edge of the VM network?

t3cores connect to the cams, Cable Access Modules, on one side, and the T640 backbone routers on the other side. They couldn't be much more inside the VM network.

---------- Post added at 15:34 ---------- Previous post was at 15:33 ----------

what does docsis 3 have anything to do with this? you don't know which uBr's VM use either, why speculate?

Actually yes I do know what uBRs VM use I've been in hubsites and seen them in person, I've even worked on them. The question was asked what a uBR was, I duly answered that the one this chap is connected to is a 7246VXR.

[eth01]

universal Broadband Router in the case of Virgin Media apart from the new DOCSIS 3 kit the Cisco uBR7246VXR.

Now now, extensive tests were performed to give nothing.

Sounds like t3cores struggle with that subnet generally. Not good.

Hopefully someone will push this to the right people who will actually understand the fault rather than apparently the wrong troubleshooting steps and a conclusion that makes no sense.

that won't be happening. this is a misconfiguration imo with the router in question.

I'll say it again.

This is a problem related to the router and not VM.

[Ignitionnet]

I'm not even going to dignify this or waste my breath by responding.

Actually I have a bit of time so I will :)

Care to explain how a misconfiguration on a home router means they can't ping an interface on a router on VM's network, while I can?

11 17 ms 17 ms 17 ms nott-t3core-1b-as0-0.network.virginmedia.net [213.105.174.174]
12 17 ms 16 ms 16 ms nott-t2cam1-b-v158.network.virginmedia.net [80.4.46.213]

As far as I'm aware home routers have pretty basic configuration, routing works fine to the 'misconfigured router' from anywhere apart from his subnet. If you actually have any idea how IP works it's not rocket science to have a fair guess at the fault.

EDIT: Point is it's not a fault with the home router. The traces you posted in this thread proved nothing, they weren't related to the fault in question they just showed that the router didn't respond to pings. The fault is in the routing between the Lincoln and Newark subnets which is why traces from one to the other don't even get to uBR let alone the 'misconfigured router'.

Those are my last words on it though. You either have no idea what you're talking about or are trolling.

It's tricky to decide which when you post traceroutes which are fine and blame SNR / routing, then try and say that t3cores are the edge of the VM network, but either way knock yourself out :)

OP - Get this onto the newsgroups for checking out.

[Raistlin]

Let's try to keep this constructive/helpful shall we people?

Thanks :)

[BuckoA51]

This is why I dread ringing Virgin's technical support because they will fob me off saying it is my router when there's no way on earth it could possibly be down to my router in fact I've even tried disconnecting the router and plugging into my cable modem directly (both ends) and yes we still cant ping, tracert, ftp or anything between each other.

Thanks Broadbandings for agreeing with me as you can probably imagine I'm pretty annoyed at this whole matter.

[whydoIneedatech]

This is why I dread ringing Virgin's technical support because they will fob me off saying it is my router when there's no way on earth it could possibly be down to my router in fact I've even tried disconnecting the router and plugging into my cable modem directly (both ends) and yes we still cant ping, tracert, ftp or anything between each other.

Thanks Broadbandings for agreeing with me as you can probably imagine I'm pretty annoyed at this whole matter.

You ring them up without your router connected and do not even mention that you use a router.

Tech Support is open 24/7 on the numbers below.

For help with your TV or Phone and for Broadband Technical Support:

Call Product Support/Faults on 151 option 3 from your Virgin Media Phone. It's absolutely free.

Or call 0845 454 1111 from any other phone line.

[BuckoA51]

I'm going to make damn sure my two friends firewalls can accept pings and traceroutes by testing them from my work connection first. Any oversight on my part and I'll be told it's not a VM problem again.

Also, where are the newsgroups? I know how to use nntp but I haven't used it in ages, do I need to use Virgins news server to access them?

[eth01]

I'm going to make damn sure my two friends firewalls can accept pings and traceroutes by testing them from my work connection first. Any oversight on my part and I'll be told it's not a VM problem again.

Also, where are the newsgroups? I know how to use nntp but I haven't used it in ages, do I need to use Virgins news server to access them?

I told you it was -- sorry for the messing about. :hugs:

[Cobbydaler]

I'm going to make damn sure my two friends firewalls can accept pings and traceroutes by testing them from my work connection first. Any oversight on my part and I'll be told it's not a VM problem again.

Also, where are the newsgroups? I know how to use nntp but I haven't used it in ages, do I need to use Virgins news server to access them?

virginmedia.support.broadband.cable

Should be able to access them from other news servers...

[Ignitionnet]

This is why I dread ringing Virgin's technical support because they will fob me off saying it is my router when there's no way on earth it could possibly be down to my router in fact I've even tried disconnecting the router and plugging into my cable modem directly (both ends) and yes we still cant ping, tracert, ftp or anything between each other.

Thanks Broadbandings for agreeing with me as you can probably imagine I'm pretty annoyed at this whole matter.

No need for thanks, if the traces aren't even getting to Newark / Lincoln and back how can your or your mate's broadband routers be at fault :confused:

Read your traces again you'll see they die at nodes with nott in their name - those boxes are in Nottingham, your trace never gets to Newark and if it does the reply never gets back.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 10 ms 7 ms 12 ms 10.62.192.1
3 18 ms 18 ms 12 ms nott-t2cam2-b-v638.network.virginmedia.net [82.13.49.169]
4 10 ms 23 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]
5 * * * Request timed out.
6 * * * Request timed out.

1 <1 ms <1 ms <1 ms 192.168.1.1
2 15 ms 10 ms 7 ms 10.62.192.1
3 10 ms 23 ms 13 ms nott-t2cam2-b-v638.network.virginmedia.net [82.13.49.169]
4 19 ms 9 ms 12 ms nott-t3core-1b-ae3-0.network.virginmedia.net [195.182.175.141]
5 * * * Request timed out.

1 4 ms <1 ms <1 ms 192.168.1.1
2 18 ms 6 ms 23 ms 10.225.204.1
3 46 ms 7 ms 10 ms nott-t2cam1-a-v158.network.virginmedia.net [80.4.46.81]
4 * * * Request timed out.
5 * * * Request timed out.

[BuckoA51]

virginmedia.support.broadband.cable

Should be able to access them from other news servers...

Tried Virgins news server but according to Thunderbird it doesn't have any newsgroups?!

I do have an easynews account though so I'll try that later.

[Ignitionnet]

Virgin's groups won't be carried by Easynews. I don't have access so I can't explain to you what's going on there...

[BuckoA51]

Newsbin pro says the same thing! news.virginmedia.net has 0 newsgroups! Lol nothing works correctly on Virgins network - Think this should be a separate thread though.

[Broken Hope]

Yet again it's happening. This makes no sense how can it happen for a short period every single day but then be fine for the rest of the time? I don't do anything to fix it, It just fixes itself. Tired of all these timeouts and address not found errors in Firefox, it also prevents me playing online games.

[BuckoA51]

The problems could be related, if there is a faulty router along the path as far as I know (correct me if I'm wrong) the TCP protocol is intelligent enough to route around it? Unfortunately that isn't an option for myself and my friend because he is too close to the affected router... I'm guessing here a little.

[Cobbydaler]

Newsbin pro says the same thing! news.virginmedia.net has 0 newsgroups! Lol nothing works correctly on Virgins network - Think this should be a separate thread though.

It's news.virginmedia.com

[Joxer]

It's news.virginmedia.com

Yup I get 75246 groups on there.

[Ignitionnet]

The problems could be related, if there is a faulty router along the path as far as I know (correct me if I'm wrong) the TCP protocol is intelligent enough to route around it? Unfortunately that isn't an option for myself and my friend because he is too close to the affected router... I'm guessing here a little.

TCP has no routing knowledge at all, it relies on routers to route IP and it sits on top of IP. TCP can only handle flow control, if the flow doesn't get to the destination there's nothing it can do.

[BuckoA51]

Yes I got it working now.. Going over to friends house to collect some more data tomorrow, armed with ping and tracert on my phone.. Then we'll see if I can't get Virgin to fix this for me...

"TCP has no routing knowledge at all, it relies on routers to route IP and it sits on top of IP. TCP can only handle flow control, if the flow doesn't get to the destination there's nothing it can do."

Oh I misunderstand then I thought it was designed by the military so that it could re-route around broken connections... or is that the IP bit... I get confused embarrassing because I did basic networking at uni ;)

[Broken Hope]

Looks like it's that time of the day again, had 10 mins of problems yesterday then it's been fine ever since till just now. How Virgin not have fixed this yet after almost 2 weeks?

[eth01]

if your modem SYNC light was flashing this afternoon... VM do know, afaik it's been fixed (stkp-manc was affected iirc)

[Broken Hope]

if your modem SYNC light was flashing this afternoon... VM do know, afaik it's been fixed (stkp-manc was affected iirc)

That's the problem the modem lights aren't affected, the connection will just stop working for no apparent reason and then start working again without me changing anything, but in the time it isn't working all websites will time out and domain names can't be resolved and if I'm playing an online game at the time I'll have extremely high latency in the reagon of 2000 or more. It seems like a huge packet loss issue. My modem signal levels haven't changed, they are what they have been for months if not years, I'm also inclined to believe it isn't a problem on my end or why would it only happen for a short period of time each day and be perfect the rest of the time?

[Ignitionnet]

Oh I misunderstand then I thought it was designed by the military so that it could re-route around broken connections... or is that the IP bit... I get confused embarrassing because I did basic networking at uni ;)

Yep it's IP that can reroute around broken links but needs a dynamic routing protocol to make the routing decisions for it. IP in itself supplies best effort delivery and its' only mechanism for ensuring integrity is checksumming.

http://en.wikipedia.org/wiki/Internet_Protocol

---------- Post added at 18:36 ---------- Previous post was at 18:34 ----------

if your modem SYNC light was flashing this afternoon... VM do know, afaik it's been fixed (stkp-manc was affected iirc)

Poster is in Nottingham, Stockport comes off Manchester and is on different HFC network and different platform.

---------- Post added at 18:37 ---------- Previous post was at 18:36 ----------

That's the problem the modem lights aren't affected, the connection will just stop working for no apparent reason and then start working again without me changing anything, but in the time it isn't working all websites will time out and domain names can't be resolved and if I'm playing an online game at the time I'll have extremely high latency in the reagon of 2000 or more. It seems like a huge packet loss issue. My modem signal levels haven't changed, they are what they have been for months if not years, I'm also inclined to believe it isn't a problem on my end or why would it only happen for a short period of time each day and be perfect the rest of the time?

You say that, but if the issue is something causing a ton of upstream noise you won't see the modem levels change, only VM can see that.

Does it happen at a consistent time every day? Looking at your posts it doesn't but I'm thinking that something happens that throws burst noise onto the HFC network briefly.

[Broken Hope]

You say that, but if the issue is something causing a ton of upstream noise you won't see the modem levels change, only VM can see that.

Does it happen at a consistent time every day? Looking at your posts it doesn't but I'm thinking that something happens that throws burst noise onto the HFC network briefly.

What could cause a ton of upstream noise? It doesn't happen at the same time every day but it usually occurs between 2pm and 5pm, it hasn't occurred at night time yet.

[Ignitionnet]

What could cause a ton of upstream noise? It doesn't happen at the same time every day but it usually occurs between 2pm and 5pm, it hasn't occurred at night time yet.

Take your pic really, anything that makes a lot of RF. I've known pagers cause issues with network that wasn't properly sealed. Microwaves, lighting, etc, etc.

[Broken Hope]

Started happening today at around 2:55 PM, still on and off right now, here's a few traces I've run when I started to notice the problem.

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * 7 ms 8 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4
.46.133]
3 6 ms 8 ms 8 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
4 9 ms 17 ms 14 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
5 11 ms 14 ms 11 ms gfd-bb-a-so-100-0.network.virginmedia.net [213.1
05.175.137]
6 25 ms 16 ms 17 ms win-bb-b-so-210-0.network.virginmedia.net [212.4
3.162.206]
7 17 ms 21 ms 18 ms win-dc-b-v903.network.virginmedia.net [213.105.1
74.38]
8 16 ms 34 ms 15 ms www.virginmedia.com [212.250.162.12]

Trace complete.

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 6 ms 5 ms * 10.139.0.1
2 17 ms 8 ms 7 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4
.46.133]
3 8 ms 7 ms 8 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
4 11 ms 8 ms 28 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
5 15 ms 13 ms 14 ms gfd-bb-a-so-100-0.network.virginmedia.net [213.1
05.175.137]
6 18 ms 17 ms 17 ms win-bb-b-so-210-0.network.virginmedia.net [212.4
3.162.206]
7 17 ms 17 ms 18 ms win-dc-b-v903.network.virginmedia.net [213.105.1
74.38]
8 36 ms 16 ms 15 ms www.virginmedia.com [212.250.162.12]

Trace complete.

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 21 ms 8 ms 5 ms 10.139.0.1
2 9 ms 31 ms 6 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4
.46.133]
3 18 ms 7 ms 8 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
4 19 ms 7 ms 17 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
5 42 ms 19 ms 14 ms gfd-bb-a-so-100-0.network.virginmedia.net [213.1
05.175.137]
6 26 ms 51 ms 17 ms win-bb-b-so-210-0.network.virginmedia.net [212.4
3.162.206]
7 19 ms 24 ms 19 ms win-dc-b-v903.network.virginmedia.net [213.105.1
74.38]
8 16 ms 15 ms 14 ms www.virginmedia.com [212.250.162.12]

Trace complete.

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 6 ms 9 ms 6 ms 10.139.0.1
2 8 ms 7 ms 6 ms nott-t2cam1-b-v120.network.virginmedia.net [80.4
.46.133]
3 7 ms 8 ms 17 ms nott-t3core-1b-ae2-0.network.virginmedia.net [19
5.182.174.238]
4 10 ms 12 ms 8 ms nth-bb-b-as1-0.network.virginmedia.net [213.105.
174.173]
5 25 ms 12 ms 16 ms gfd-bb-a-so-100-0.network.virginmedia.net [213.1
05.175.137]
6 48 ms 31 ms 15 ms win-bb-b-so-210-0.network.virginmedia.net [212.4
3.162.206]
7 * * * Request timed out.
8 * * 14 ms www.virginmedia.com [212.250.162.12]

Trace complete.

tracert www.virginmedia.com
Unable to resolve target system name www.virginmedia.com.

[Joxer]

So can you still ping/tracert to 212.250.162.12 ?

[Broken Hope]

So can you still ping/tracert to 212.250.162.12 ?

Not when I'm having the problem no, it will time out like if I'm using a url. I've tried OpenDNS also to rule out a possible DNS server issue.

[Joxer]

If it is a DNS issue you will get unkown host pinging the URL but replies using the ip address. If it times out using the URL then the DNS is working ok or you pc has cached the address. Try ipconfig /flushdns and then ping the URL again - if it still times out it is not a DNS issue as the URL is being resolved to the ip address.

[Broken Hope]

If it is a DNS issue you will get unkown host pinging the URL but replies using the ip address. If it times out using the URL then the DNS is working ok or you pc has cached the address. Try ipconfig /flushdns and then ping the URL again - if it still times out it is not a DNS issue as the URL is being resolved to the ip address.

I don't have the DNS Client service running on my machine so it won't be caching anything.

[BuckoA51]

This issue has now been resolved for me! I posted in the technical support newsgroup all the evidence I collected and it got fixed :)

[Joxer]

Cool, glad you got it sorted.

[Ignitionnet]

That's great news, did they give any explanation what the issue was?

[BuckoA51]

Not really

"Hi Bucko,

There is clearly an issue here, it may help if you could email me the IP
addresses of the 2 people you cant trace to. Could you email me at
news-support@ntlworld.com and post again once you've done that."

I did that and after that it was fixed... I thought it was going to take days but all credit to them it was fixed very quickly.

[Ignitionnet]

Evidently not a faulty home router unless VM have access to those too :)

Good result, gold star to VM.

[Broken Hope]

Connection has been perfect since the drop at 2:55pm till now, but just out of interest how do these modem levels look, bare in mind that when I had the modem replaced from an Ambit 120 to the 250 I specifically asked the engineer to check the levels because I thought the upload power was too high and they said it was fine.

Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Receive Power Level : 0.2 dBmV
Downstream SNR : 40.1 dB

Upstream Frequency : 29200000 Hz
Upstream Modulation : QAM16
Upstream transmit Power Level : 56.0 dBmV

These levels have been the same for years and I've never had problems with dropped connections before the last week or two and I've always reached the advertised speed of my connection most of the time.

[Ignitionnet]

The engineer was wrong, your upload power is not acceptable and the connection needs work to drop it. 56dBmV is out of spec for 16QAM.

[Broken Hope]

The engineer was wrong, your upload power is not acceptable and the connection needs work to drop it. 56dBmV is out of spec for 16QAM.

Heh and how am I to get it lowered? It wasn't the first engineer to say the levels are fine. Do I just call faults and say my upstream power is too high?

[Ignitionnet]

Tell them that you are having problems with the connection being unstable and freezing at times.

That's about the only thing that comes to mind. The other idea is to try the newsgroups.

[Broken Hope]

Heh I don't know if to laugh or cry. I used the web form on Virgins website to report my problem, included a link to this thread and also included signal levels from the modem's info page, I just got the following reply back in an e mail.

Thanks for getting in touch with the Virgin Media Support team.

You will be please to know we have ordered a new modem to you, which
will come through the post. The package will contain instructions on how
to set up and contain a self-addressed envelope to post your old modem
back to us. It can take up to 10 working days to arrive, if it is not
delivered by then please call us free on 151 via a Virgin landline or on
0845 454 1111 at the cost of local rates.


I'm not quite sure how a new modem will fix signal levels.

[edit]

Connection seems to be acting up again.

ping -n 25 www.virginmedia.com

Pinging www.virginmedia.com [212.250.162.12] with 32 bytes of

Reply from 212.250.162.12: bytes=32 time=16ms TTL=120
Request timed out.
Request timed out.
Reply from 212.250.162.12: bytes=32 time=16ms TTL=120
Reply from 212.250.162.12: bytes=32 time=15ms TTL=120
Reply from 212.250.162.12: bytes=32 time=14ms TTL=120
Reply from 212.250.162.12: bytes=32 time=14ms TTL=120
Reply from 212.250.162.12: bytes=32 time=17ms TTL=120
Reply from 212.250.162.12: bytes=32 time=16ms TTL=120
Request timed out.
Reply from 212.250.162.12: bytes=32 time=16ms TTL=120
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Reply from 212.250.162.12: bytes=32 time=18ms TTL=120
Reply from 212.250.162.12: bytes=32 time=17ms TTL=120
Reply from 212.250.162.12: bytes=32 time=17ms TTL=120
Reply from 212.250.162.12: bytes=32 time=17ms TTL=120
Reply from 212.250.162.12: bytes=32 time=31ms TTL=120
Reply from 212.250.162.12: bytes=32 time=15ms TTL=120
Reply from 212.250.162.12: bytes=32 time=16ms TTL=120
Reply from 212.250.162.12: bytes=32 time=17ms TTL=120
Reply from 212.250.162.12: bytes=32 time=14ms TTL=120
Reply from 212.250.162.12: bytes=32 time=39ms TTL=120

Ping statistics for 212.250.162.12:
Packets: Sent = 25, Received = 18, Lost = 7 (28% loss),
Approximate round trip times in milli-seconds:
Minimum = 14ms, Maximum = 39ms, Average = 18ms

[Ignitionnet]

Heh I don't know if to laugh or cry. I used the web form on Virgins website to report my problem, included a link to this thread and also included signal levels from the modem's info page, I just got the following reply back in an e mail.



I'm not quite sure how a new modem will fix signal levels.

It might, the transmitter in your modem might not be working too well which is why it is transmitting at such high power.

Can't say 100% it's that but it's a possibility. Not sure about it though as it only happens for a part of the day and is fine otherwise.

[Joxer]

Some modems seem to handle high power levels better - the EPC2100 will work up to 61db - no info on how the ambits behave yet as we have not issued them long enough to be able to tell.

[whydoIneedatech]

Some modems seem to handle high power levels better - the EPC2100 will work up to 61db - no info on how the ambits behave yet as we have not issued them long enough to be able to tell.

The Ambit 255/6 has been issued for over a year in EX-NTL areas and are similar to the Webstars for that power level.

[Broken Hope]

I just find it strange they are sending a new modem, I only got this one when the 20Mb upgrade came out because my old Ambit 120 would constantly reboot when using a bit torrent client. I would have thought they would have arranged an engineer to look at the levels considering I did provide them in the webform.

[edit]

What does a flashing ready light indicate btw? I tried rebooting the modem to solve the issue and then it was stuck with the sync light lit and the ready light flashing, this carried on for over half an hour, then the ready light finally stayed lit but it took a further 5 minutes or so before I could actually get an IP address from the DHCP.

[Joxer]

Flashing ready indicates some kind of upstream issue or registration issue, I don't think a new modem will fix it.

And cheers for the info whydoineedatech.

[Broken Hope]

Just got off the phone with faults they claim that the problem has been escalated and that I have to wait for it to be fixed. I was under the impression that an engineer would need to come out in order to fix power levels. Personally feels like I was fobbed off.

[Ignitionnet]

Some modems seem to handle high power levels better - the EPC2100 will work up to 61db - no info on how the ambits behave yet as we have not issued them long enough to be able to tell.

61dB is out of spec for 16QAM - no modem should even attempt to go that high at that modulation and a loss of signal due to distortion / bad SNR is likely.

Modems thwacking a node and overdriving the laser transmitting at that level can cause clipping and other joyously unpleasant results. 16QAM is in itself much more stressful than QPSK on the lasers without having modems screaming at them.

---------- Post added at 00:04 ---------- Previous post was at 00:03 ----------

Just got off the phone with faults they claim that the problem has been escalated and that I have to wait for it to be fixed. I was under the impression that an engineer would need to come out in order to fix power levels. Personally feels like I was fobbed off.

Bad power levels can be affecting just you or could be affecting multiple people. If affecting multiple people it needs a network tech to have a looksie and line up the area again. Sadly the people who come to your house to check your power levels aren't necessarily qualified to play with the lasers.

[Broken Hope]

Okay fitted my new modem today, it's an Ambit 256, for some reason this modem is using QPSK for upstream modulation, is this better/worse than QAM? Though upstream transmit power is still 55-57, every time I phone up faults and mention my upstream power being too high they just basically ignore the fact I've even said it.

What can I do to get this power problem resolved if CS aren't willing to do anything it seems?

[Ignitionnet]

From your point of view QPSK is more tolerant of bad signals, so you may find it more stable.

[Broken Hope]

Once again the problem returns, I'm getting really frustrated now. Calling CS/faults isn't helping because I always end up at an Indian call centre where they just ask me to reboot the modem and ask what lights on the modem are lit, being an IT technician for a living I've already checked these things. I know what the issue is, my power levels are too high, what can I do to get this resolved without going through the same BS with CS every time I phone?

It seems the modem is back on QAM also btw, here are my levels at the time of writing this.

Upstream Lock : Locked
Upstream Channel ID : 2
Upstream Frequency : 29200000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 55.0 dBmV
Upstream Mini-Slot Size : 2

Downstream Lock : Locked
Downstream Channel Id : 5
Downstream Frequency : 402750000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 1.5 dBmV
Downstream SNR : 40.0 dB

This is pretty awsome too

Tracing route to www.virginmedia.com [212.250.162.12]
over a maximum of 30 hops:

1 * * * Request timed out.
2 * * * Request timed out.
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * 19 ms 20 ms win-dc-b-v903.network.virginmedia.net [213.105.174.38]
8 17 ms 26 ms 17 ms www.virginmedia.com [212.250.162.12]

Trace complete.

[Axegrinder]

Hmm...yes the upstream power is too high for QAM16. Thats most likely causing connection problems. Try using the newsgroups as they are usually more helpful than CS.

[Broken Hope]

Made a post in the newsgroup around half 5 between connection problems, then lost the connection completely for about 3 hours, still no answer to my post however. Doesn't look like this will be resolved any time soon heh.

[edit]

Looks like a tech is coming out Friday, lets hope they can resolve the problem. Though the newsgroup CS post said that the power levels are only borderline and if I wasn't having problems they would consider them fine.

[Broken Hope]

Just had a tech visit, he plugged the co-ax into a reader of some sorts and then said the power levels are fine, so I'm still stuck with an upstream power of 55.0 dBmV. He then said he would change the connection in the cab and then left.

Heh it's worrying that I continue to get told my power levels are fine by Virgin Media staff and yet told they aren't here :/

[Broken Hope]

Apparently my problem is due to low SNR at the UBR at certain times of the day, any idea how long something like this takes to resolve?

[Ignitionnet]

Thought so:

61dB is out of spec for 16QAM - no modem should even attempt to go that high at that modulation and a loss of signal due to distortion / bad SNR is likely.

That's a piece of string question. Low SNR on upstream does explain the high upstream transmit power though, your modem is increasing its' transmit power to try and be 'heard' over the noise that's causing the low SNR.

Depends what the issue is. If something in your area is causing the noise they have to go through the network and find what it is and mitigate it :(

[Broken Hope]

Thought so:



That's a piece of string question. Low SNR on upstream does explain the high upstream transmit power though, your modem is increasing its' transmit power to try and be 'heard' over the noise that's causing the low SNR.

Depends what the issue is. If something in your area is causing the noise they have to go through the network and find what it is and mitigate it :(

What's odd is I've had these power levels for at least 3 years, it's only recently it's started to affect my connection.