Issues with your account? Bug us in the Discord!
Internet connection woes
ShadowDancer
When I say, "Why aye, gadgie," in my heart I say, "Och aye, laddie."London, UK
in Zocalo v2.0
Specifically, it seems to be frakked! My connection won't work at all, and windows is reporting that there is no internet access. When I run the diagnose function I get a 'cant communicate with dns server" message. I'm using the standard netgear vmdg280 gateway that I was sent, which I get the impression isn't the most reliable piece of junk on the market.
After doing some searching through the virgin help forums I've discovered I've got a similar problem that [URL="http://community.virginmedia.com/t5/Fibre-optic-broadband-cable/Cannot-communicate-with-Primary-DNS-Server/td-p/50936"]this[/URL] person had, altho with some differences
Pinging google gives this:
*
C:\Users\Jamie>ping google.co.uk
Pinging google.co.uk [74.125.230.144] with 32 bytes
Reply from 74.125.230.144: bytes=32 time=86ms TTL=5
Reply from 74.125.230.144: bytes=32 time=87ms TTL=5
Reply from 74.125.230.144: bytes=32 time=84ms TTL=5
Reply from 74.125.230.144: bytes=32 time=95ms TTL=5
Ping statistics for 74.125.230.144:
*** Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
*** Minimum = 84ms, Maximum = 95ms, Average = 88ms
*
*
*
C:\Users\Jamie>tracert google.co.uk
Tracing route to google.co.uk [74.125.230.144]
over a maximum of 30 hops:
* 1**** 1 ms*** <1 ms*** <1 ms* 172.20.10.1
* 2** 989 ms** 558 ms** 549 ms* 172.30.152.4
* 3** 518 ms** 568 ms** 539 ms* 172.31.154.212
* 4** 428 ms** 519 ms** 519 ms* 217.171.129.125
* 5**** ******** ******** ***** Request timed out.
* 6**** ******** ******** ***** Request timed out.
* 7** 446 ms** 549 ms** 609 ms* 66.249.94.78
* 8*** 79 ms*** 81 ms*** 77 ms* 209.85.251.202
* 9*** 98 ms*** 79 ms*** 89 ms* 74.125.230.144
Trace complete.
*
*
pinging bbc.co.uk gives:
*
C:\Users\Jamie>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=76ms TTL=116
Reply from 212.58.224.138: bytes=32 time=75ms TTL=116
Reply from 212.58.224.138: bytes=32 time=82ms TTL=116
Reply from 212.58.224.138: bytes=32 time=83ms TTL=116
Ping statistics for 212.58.224.138:
*** Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
*** Minimum = 75ms, Maximum = 83ms, Average = 79ms
*
*
*
C:\Users\Jamie>tracert 212.58.224.138
Tracing route to virtual-vip.thdo.bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
* 1*** <1 ms*** <1 ms*** <1 ms* 172.20.10.1
* 2*** 93 ms*** 71 ms*** 67 ms* 172.30.152.4
* 3*** 84 ms*** 83 ms*** 85 ms* 172.31.154.212
* 4*** 74 ms*** 79 ms*** 89 ms* 217.171.129.125
* 5*** 91 ms*** 99 ms*** 99 ms* 195.50.90.197
* 6**** ****** 120 ms** 136 ms* 195.50.90.197
* 7*** 95 ms*** 83 ms*** 75 ms* 195.50.90.162
* 8*** 85 ms*** 79 ms*** 97 ms* 212.58.238.149
* 9*** 87 ms*** 89 ms*** 78 ms* virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Trace complete.
*
I've been trying and failing to get anywhere with Virgin's tech support, so I'm guessing the next step is to demand a new router. I've got a thread on their forums as well, but so far no response.
*
Any help would be much appreciated!
After doing some searching through the virgin help forums I've discovered I've got a similar problem that [URL="http://community.virginmedia.com/t5/Fibre-optic-broadband-cable/Cannot-communicate-with-Primary-DNS-Server/td-p/50936"]this[/URL] person had, altho with some differences
Pinging google gives this:
*
C:\Users\Jamie>ping google.co.uk
Pinging google.co.uk [74.125.230.144] with 32 bytes
Reply from 74.125.230.144: bytes=32 time=86ms TTL=5
Reply from 74.125.230.144: bytes=32 time=87ms TTL=5
Reply from 74.125.230.144: bytes=32 time=84ms TTL=5
Reply from 74.125.230.144: bytes=32 time=95ms TTL=5
Ping statistics for 74.125.230.144:
*** Packets: Sent = 4, Received = 4, Lost = 0 (0% l
Approximate round trip times in milli-seconds:
*** Minimum = 84ms, Maximum = 95ms, Average = 88ms
*
*
*
C:\Users\Jamie>tracert google.co.uk
Tracing route to google.co.uk [74.125.230.144]
over a maximum of 30 hops:
* 1**** 1 ms*** <1 ms*** <1 ms* 172.20.10.1
* 2** 989 ms** 558 ms** 549 ms* 172.30.152.4
* 3** 518 ms** 568 ms** 539 ms* 172.31.154.212
* 4** 428 ms** 519 ms** 519 ms* 217.171.129.125
* 5**** ******** ******** ***** Request timed out.
* 6**** ******** ******** ***** Request timed out.
* 7** 446 ms** 549 ms** 609 ms* 66.249.94.78
* 8*** 79 ms*** 81 ms*** 77 ms* 209.85.251.202
* 9*** 98 ms*** 79 ms*** 89 ms* 74.125.230.144
Trace complete.
*
*
pinging bbc.co.uk gives:
*
C:\Users\Jamie>ping bbc.co.uk
Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=76ms TTL=116
Reply from 212.58.224.138: bytes=32 time=75ms TTL=116
Reply from 212.58.224.138: bytes=32 time=82ms TTL=116
Reply from 212.58.224.138: bytes=32 time=83ms TTL=116
Ping statistics for 212.58.224.138:
*** Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
*** Minimum = 75ms, Maximum = 83ms, Average = 79ms
*
*
*
C:\Users\Jamie>tracert 212.58.224.138
Tracing route to virtual-vip.thdo.bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:
* 1*** <1 ms*** <1 ms*** <1 ms* 172.20.10.1
* 2*** 93 ms*** 71 ms*** 67 ms* 172.30.152.4
* 3*** 84 ms*** 83 ms*** 85 ms* 172.31.154.212
* 4*** 74 ms*** 79 ms*** 89 ms* 217.171.129.125
* 5*** 91 ms*** 99 ms*** 99 ms* 195.50.90.197
* 6**** ****** 120 ms** 136 ms* 195.50.90.197
* 7*** 95 ms*** 83 ms*** 75 ms* 195.50.90.162
* 8*** 85 ms*** 79 ms*** 97 ms* 212.58.238.149
* 9*** 87 ms*** 89 ms*** 78 ms* virtual-vip.thdo.bbc.co.uk [212.58.224.138]
Trace complete.
*
I've been trying and failing to get anywhere with Virgin's tech support, so I'm guessing the next step is to demand a new router. I've got a thread on their forums as well, but so far no response.
*
Any help would be much appreciated!
Comments
Have you tried sniffing your network communication stream with a tool like WireShark to see what's going on?
Because of the weird way our house is wired up, DSL isn't an option either
:p
Which could also indicate that the modem was not the source of the problem. Anyway with cable your are SOL. ;)
I was actually pleasantly surprised at Verizon actually having a phone tree that did something other than annoy :p
Though I hear that the phone trees for PHONE usage from them are absolutely awful :D
The only thing that was really a pain about it was that I needed that line up and running to do PCI Compliance on the new credit card terminal. the Credit card industry is pretty gung how about security, so I maintain a separate DSL line that does nothing but process Credit cards. It adds a bit to my processing charges, (which are already high) but if it means that I won't be the source of a data leak... then it's good