Weird thing happening with connections

[#1]

Thanks orbrey.

[#2]

Re: Santiago & DG834Gv2    V3.01.38 problems
I had problems with my DG824 V2 & firmware V3.01.38 see http://forum1.netgear.com/showthread.php?t=25352&highlight=dg834
(I wish I knew how to substitute the word "here" for a web address!)
I downgraded back to firmware V3.01.31 & all my problems vanished.
This might not be relayed to your issues but it might be worth checking that you can access the routers admin page when the problems occur.
Richard

[#3]

Quote from: orbrey

Why couldn't you all use the same router?

That's the easy fix out the window then

[#4]

Thanks for the ideas about the router firmware I will check that out.
This is how you enter a link with text here or any other word.

here

here

[#5]

Well if you can get to the router's page then it's definitely an external issue somewhere along the line. We'll keep investigating.

[#6]

Just encountered slow resolves but not drops as before. Here are the two trace routes.:
[quote= 08/08/09 06:47]
Tracing route to www.bbc.net.uk [212.58.251.195] over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    34 ms    38 ms    34 ms  lo0-plusnet.ptn-ag1.plus.net [195.166.128.123]
  3    35 ms    34 ms    34 ms  gi2-2-303.ptn-gw01.plus.net [84.92.3.9]
  4    34 ms    34 ms    33 ms  te2-2.thn-gw1.plus.net [212.159.1.54]
  5    34 ms    34 ms    34 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  6  231 ms  214 ms  213 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7    34 ms    34 ms    34 ms  212.58.238.133
  8    33 ms    34 ms    34 ms  212.58.239.58
  9    34 ms    35 ms    34 ms  www-vip.telhc.bbc.co.uk [212.58.251.195]
Trace complete.
[quote=08/08/09 06:49]Tracing route to www.bbc.net.uk [212.58.253.67] over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.1.1
  2    35 ms    34 ms    34 ms  lo0-plusnet.ptn-ag1.plus.net [195.166.128.123]
  3    34 ms    34 ms    34 ms  gi2-2-303.ptn-gw01.plus.net [84.92.3.9]
  4    34 ms    34 ms    33 ms  te2-2.thn-gw1.plus.net [212.159.1.54]
  5  204 ms  206 ms  210 ms  te2-3.thn-gw2.plus.net [212.159.1.58]
  6    34 ms    34 ms    33 ms  rt0.thdo.bbc.co.uk [212.58.239.25]
  7    35 ms    34 ms    34 ms  212.58.238.149
  8    35 ms    35 ms    35 ms  te12-1.hsw1.cwwtf.bbc.co.uk [212.58.239.234]
  9    35 ms    35 ms    34 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67]
Trace complete.

[#7]

Further trace routes.

Quote

13/08/2009 11:04 Tracing route to www.bbc.net.uk [212.58.253.67] over a maximum of 30 hops:   1    1 ms    <1 ms    <1 ms  192.168.1.1   2    34 ms    34 ms    39 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]   3    *        *        *    Request timed out.   4    *        *        *    Request timed out.   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    *    1744 ms    34 ms  www-vip.cwwtf.bbc.co.uk [212.58.253.67] Trace complete.

Quote

13/08/09 11:05 Tracing route to www.bbc.net.uk [212.58.251.195] over a maximum of 30 hops:   1    <1 ms    <1 ms    <1 ms  192.168.1.1   2    34 ms    35 ms    33 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]   3  1569 ms    34 ms    33 ms  gi2-2-204.ptn-gw02.plus.net [84.92.3.93]   4    33 ms    33 ms    33 ms  te2-2.pte-gw2.plus.net [212.159.1.106]   5  236 ms  227 ms  223 ms  vl23.thn-gw2.plus.net [212.159.4.20]   6    34 ms    34 ms    33 ms  rt0.thdo.bbc.co.uk [212.58.239.25]   7    33 ms    34 ms    34 ms  212.58.238.133   8    34 ms    35 ms    34 ms  212.58.239.58   9    *      42 ms    49 ms  www-vip.telhc.bbc.co.uk [212.58.251.195] Trace complete.

[#8]

Just had another, at the same time as Spiders:
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  192.168.0.1
  2    24 ms    25 ms    25 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *    1698 ms    33 ms  vlan7.pih-gw3.plus.net [212.159.0.26]
  7    30 ms    33 ms    32 ms  if25.pih-lb04.plus.net [212.159.0.18]
  8    *        *        *    Request timed out.
  9  1078 ms    98 ms    43 ms  portal.plus.net [212.159.8.2]
Trace complete.

[#9]

Same problem creating aggro here http://forums.thinkbroadband.com/plusnet/f/3685749-more-tracert-fails.html
Perhaps a response from Comms wouldn't hurt

[#10]

Happened several times this morning here, the tracert I put up is just one example.
This was 12.51:
Tracing route to portal.plus.net [212.159.8.2]
over a maximum of 30 hops:
  1    1 ms    1 ms    1 ms  192.168.0.1
  2    24 ms    23 ms    23 ms  lo0-plusnet.ptn-ag2.plus.net [195.166.128.53]
  3    *        *        *    Request timed out.
  4    *        *        *    Request timed out.
  5    *        *        *    Request timed out.
  6    *        *        *    Request timed out.
  7    *        *    1273 ms  if25.pih-lb04.plus.net [212.159.0.18]
  8    *        *        *    Request timed out.
  9    *        *        *    Request timed out.
10    *        *        *    Request timed out.
11    *        *        *    Request timed out.
12    *        *        *    Request timed out.
13    *        *        *    Request timed out.
14    *        *        *    Request timed out.
15    *    1189 ms    31 ms  portal.plus.net [212.159.8.2]
That took 2 or 3 minutes to complete.
I notice that on the thread you mentioned, Oldjim, that it was ag2 that seemed to have the issue there, as well.

[#11]

We noticed an issue with one of the traffic management switches and have now reloaded this. I'll keep an eye on this thread to see if any more examples crop up.

[#12]

For me, it's been bad nearly all day - still no better now. 

[#13]

Are you getting the same timeouts as the others in this thread? If so can you provide the tracerts so we can look into it?

[#14]

Yes - timeouts and loss of VPN to my office.  Don't have any of the earlier traces, but as an example here are two done just seconds apart, the second one is normal, the first shows some big spikes in response time from some hops.  Normal web browsing has been very intermittent as well.  Sync has been solid all the time (apart from 5 mins just now in a power cut!)

P:\>tracert lonvpn.frk.com
Tracing route to lonvpn.frk.com [217.144.148.38]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.105.1
  2    33 ms    32 ms    33 ms  lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
  3  200 ms  219 ms  210 ms  gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
  4  114 ms  204 ms  202 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5    32 ms    32 ms    32 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    33 ms    32 ms    32 ms  xe-4-2-0.bb2.lon1.uk.gbxs.net [195.66.224.231]
  7  197 ms  216 ms  207 ms  xe-4-4-0.bb1.lon2.uk.gbxs.net [193.27.64.78]
  8    33 ms    32 ms    43 ms  fmn.vlan902.bb1.lon2.uk.gbxs.net [77.243.178.130
]
  9    33 ms    34 ms    32 ms  217.144.159.130
10    37 ms    37 ms    36 ms  217.144.148.33
11    42 ms    37 ms    46 ms  217.144.148.38
Trace complete.
P:\>tracert lonvpn.frk.com
Tracing route to lonvpn.frk.com [217.144.148.38]
over a maximum of 30 hops:
  1    <1 ms    <1 ms    <1 ms  192.168.105.1
  2    34 ms    33 ms    40 ms  lo0-plusnet.pcl-ag03.plus.net [195.166.128.109]
  3    31 ms    32 ms    32 ms  gi1-6-703.pcl-gw01.plus.net [84.92.0.181]
  4    33 ms    32 ms    32 ms  te2-2.pte-gw1.plus.net [212.159.0.186]
  5    31 ms    32 ms    32 ms  te2-4.pte-gw2.plus.net [212.159.1.102]
  6    33 ms    32 ms    32 ms  xe-4-2-0.bb2.lon1.uk.gbxs.net [195.66.224.231]
  7    32 ms    32 ms    31 ms  xe-4-4-0.bb1.lon2.uk.gbxs.net [193.27.64.78]
  8    32 ms    33 ms    31 ms  fmn.vlan902.bb1.lon2.uk.gbxs.net [77.243.178.130
]
  9    33 ms    32 ms    32 ms  217.144.159.130
10    37 ms    38 ms    37 ms  217.144.148.33
11    37 ms    36 ms    36 ms  217.144.148.38
Trace complete.
P:\>

[#15]

I don't think it's the same issue as the other posters as there is no timeout on the tracerts after the gateway hop and it's on a different gateway to the other issues we've seen today.
I'd suggest raising a ticket with a wireshark capture of your VPN traffic on it and we can make sure it's correctly prioritised.