Menu
Reply
  • 8
  • 1
  • 0
tangletwigs
Tuning in
162 Views
Message 1 of 7
Flag for a moderator

(Area 4) DNS issues and disconnects

For the past week or so my connection has frequently (hard to average the time but more often than once every 30 minutes) failed to acquire DNS services leading to host resolving failure errors on webpages, and more seriously insta-disconnect in online games. I have changed the DNS servers at the Router end (not a superhub) to use OpenDNS and Google DNS but this has not changed anything. I have run the online diagnosis (which ironically gave resolving issues halfway through the test ...) but it claims to find nothing wrong. Weirdly if I connect too a VPN service which provides its own DNS, the problem seems to stop
0 Kudos
Reply

Helpful Answers
  • 1.22K
  • 92
  • 229
stevedh2
Knows their stuff
219 Views
Message 6 of 7
Flag for a moderator
Helpful Answer

Re: (Area 4) DNS issues and disconnects

I have a feeling you're meant to be changing your modem as everything is being migrated to DOCSIS 3, although maybe thats happening on an area by area basis.

And still solid red BQM, and allow WAN ping is enabled..

pity the 500n doesn't port mirroring or you could look at the DNS packets to see what happening.

however I think all you can do is get a technician to sort you out..

0 Kudos
Reply
  • 8
  • 1
  • 0
tangletwigs
Tuning in
207 Views
Message 7 of 7
Flag for a moderator
Helpful Answer

Re: (Area 4) DNS issues and disconnects

I have received and activated a Superhub v3. This problem seems to now be resolved. If mods read this please mark as solved!

0 Kudos
Reply

All Replies
  • 8
  • 1
  • 0
tangletwigs
Tuning in
150 Views
Message 2 of 7
Flag for a moderator

Re: (Area 4) DNS issues and disconnects

Update - problem went away for about 2 hours on VPN but returned with a vengence at around 12.55pm. Disconnecting about every 2 minutes, which made posting this edit a real PITA.

0 Kudos
Reply
  • 8
  • 1
  • 0
tangletwigs
Tuning in
142 Views
Message 3 of 7
Flag for a moderator

Re: (Area 4) DNS issues and disconnects

Still the same

Event Log:

Tue Feb 28 12:06:59 2017	Tue Feb 28 12:06:59 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:07:09 2017	Tue Feb 28 12:07:09 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:07:39 2017	Tue Feb 28 12:07:39 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:07:49 2017	Tue Feb 28 12:07:49 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:08:19 2017	Tue Feb 28 12:08:19 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:08:29 2017	Tue Feb 28 12:08:29 2017	Critical (3)	Ranging Request Retries exhausted
Tue Feb 28 12:08:29 2017	Tue Feb 28 12:08:29 2017	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted
Tue Feb 28 12:08:59 2017	Tue Feb 28 12:08:59 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:09:09 2017	Tue Feb 28 12:09:09 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:09:39 2017	Tue Feb 28 12:09:39 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:09:49 2017	Tue Feb 28 12:09:49 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:10:19 2017	Tue Feb 28 12:10:19 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:10:29 2017	Tue Feb 28 12:10:29 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:10:59 2017	Tue Feb 28 12:10:59 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:11:09 2017	Tue Feb 28 12:11:09 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:11:39 2017	Tue Feb 28 12:11:39 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:11:49 2017	Tue Feb 28 12:11:49 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:12:19 2017	Tue Feb 28 12:12:19 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:12:28 2017	Tue Feb 28 12:12:28 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:12:58 2017	Tue Feb 28 12:12:58 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:13:08 2017	Tue Feb 28 12:13:08 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:13:38 2017	Tue Feb 28 12:13:38 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:13:48 2017	Tue Feb 28 12:13:48 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:14:18 2017	Tue Feb 28 12:14:18 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:14:28 2017	Tue Feb 28 12:14:28 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:14:58 2017	Tue Feb 28 12:14:58 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:15:08 2017	Tue Feb 28 12:15:08 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:15:38 2017	Tue Feb 28 12:15:38 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:15:48 2017	Tue Feb 28 12:15:48 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:16:18 2017	Tue Feb 28 12:16:18 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:16:28 2017	Tue Feb 28 12:16:28 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:16:58 2017	Tue Feb 28 12:16:58 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:17:08 2017	Tue Feb 28 12:17:08 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:17:38 2017	Tue Feb 28 12:17:38 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:17:48 2017	Tue Feb 28 12:17:48 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:18:18 2017	Tue Feb 28 12:18:18 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:18:28 2017	Tue Feb 28 12:18:28 2017	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out
Tue Feb 28 12:18:58 2017	Tue Feb 28 12:18:58 2017	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out
Tue Feb 28 12:19:08 2017	Tue Feb 28 12:19:08 2017	Critical (3)	Ranging Request Retries exhausted
Tue Feb 28 12:19:08 2017	Tue Feb 28 12:19:08 2017	Critical (3)	Unicast Maintenance Ranging attempted - No response - Retries exhausted

Downstream:

DS-1	DS-2	DS-3	DS-4
Frequency	235000000	243000000	251000000	259000000
Lock Status 
(QAM Lock/FEC Sync/MPEG Lock)	Y/Y/Y	Y/Y/Y	Y/Y/Y	Y/Y/Y
Channel Id	1	2	3	4
Modulation	256QAM	256QAM	256QAM	256QAM
Symbol Rate 
(Msym/sec)	6.952	6.952	6.952	6.952
Interleave Depth	I=12
J=17	I=12
J=17	I=12
J=17	I=12
J=17
Power Level 
(dBmV)	8.55	8.06	7.76	7.38
RxMER 
(dB)	37.36	36.84	37.36	37.36
Correctable
Codewords	22	34	13	5
Uncorrectable
Codewords	978	299	286	303

Upstream:

Channel Type	2.0	N/A	N/A	2.0
Channel ID	2	N/A	N/A	1
Frequency 
(Hz)	39400000	N/A	N/A	46200000
Ranging Status	Success	N/A	N/A	T4 Timeout
Modulation	64QAM	N/A	N/A	64QAM
Symbol Rate 
(KSym/sec)	5120	N/A	N/A	5120
Mini-Slot Size	2	N/A	N/A	2
Power Level 
(dBmV)	37.00	N/A	N/A	34.50
T1 Timeouts	0	0	0	0
T2 Timeouts	0	0	0	0
T3 Timeouts	5	0	0	150
T4 Timeouts	0	0	0	134

Live graph:

http://www.thinkbroadband.com/ping/share/dbd1127548c0ccdfeacb65846f5a4aa1.html

 

0 Kudos
Reply
  • 1.22K
  • 92
  • 229
stevedh2
Knows their stuff
136 Views
Message 4 of 7
Flag for a moderator

Re: (Area 4) DNS issues and disconnects

You're internet looks broken. I don't think its a DNS issue, but just that you have a very unstable connection. Have you tried switching the hub off and on?

If you wait around a week a member of Virgin staff will have a proper look at this and probably arrange an engineer visit, or you can phone up and attempt to explain your problem.

As far as I can see your power levels are ok, but those t4 timeouts and your BQM graph just shows no connection at all..

0 Kudos
Reply
  • 8
  • 1
  • 0
tangletwigs
Tuning in
130 Views
Message 5 of 7
Flag for a moderator

Re: (Area 4) DNS issues and disconnects

Yeah I dont get the solid red ping tests, my router (D-Link DSR 500n) is temporarily set to allow all ICMP stuff through, even GRC is saying Pings are still blocked. Not sure whats blocking them lol.

EVERYTHING has been rebooted on the network, cable modem, two routers, all clients. The Works (tm)

Have tried connecting to WAN2 on DSR 500n in case it was a failing NIC in the router. Nope no joy.

I dont have a Superhub, its one of the old black VMNG300 modems ("Ambit" rebadge ?). Always been a little go 'er.

But thank you very much for replying.

EDIT

After changing WAN interface on Router I was assigned a new ip address. So heres the new real time graph:

http://www.thinkbroadband.com/ping/share/0599be95c9a10d919e04747cc5d6c885.html

 Also running a traceroute on thinkbroadband shows the last hop as being 

wolv-cmts-19-tenge512.network.virginmedia.net

0 Kudos
Reply
  • 1.22K
  • 92
  • 229
stevedh2
Knows their stuff
220 Views
Message 6 of 7
Flag for a moderator
Helpful Answer

Re: (Area 4) DNS issues and disconnects

I have a feeling you're meant to be changing your modem as everything is being migrated to DOCSIS 3, although maybe thats happening on an area by area basis.

And still solid red BQM, and allow WAN ping is enabled..

pity the 500n doesn't port mirroring or you could look at the DNS packets to see what happening.

however I think all you can do is get a technician to sort you out..

0 Kudos
Reply
  • 8
  • 1
  • 0
tangletwigs
Tuning in
208 Views
Message 7 of 7
Flag for a moderator
Helpful Answer

Re: (Area 4) DNS issues and disconnects

I have received and activated a Superhub v3. This problem seems to now be resolved. If mods read this please mark as solved!

0 Kudos
Reply