Cant hold the connection for more than 8 seconds.
 

This has been bothering me for the last week or so starting off as a little niggle and as of today has finally turned my 50mb connection from Heaven to being completely unusable.

I suddenly lose connection with no explanation (Ready light is on, Up and down are still flashing etc.) I reset the Modem and it connects again for about 8-10 seconds before doing exactly the same again. So to sum it up, I can use the Internet if I reset the modem every 8 seconds.

Virgin have told me all is well and there is not an issue. I've already phoned them about a dodgy signal level and they just said they would try resolve it when they come to install other services, So I'm looking at the possibility of a dead connection + superhub... Could it get any worse?

What could this be?

Dead modem?

Is there a possibility something on my Desktop is making an ass out of my connection because frankly.. Before April this connection has been perfect with no faults to report at all. Strangely enough this happens in the same month the whole WoW p2p kicks off again.

Re: Cant hold the connection for more than 8 seconds.
 

Where abouts in newcastle are you? Im in NE6 and connection seems fine here on 50Meg, no superhub, we're waiting until that gets sorted before we upgrade to 100meg

Current speeds :

https://www.cableforum.co.uk/images/...011/05/124.png

Re: Cant hold the connection for more than 8 seconds.
 

what modem are you using, the VMNG300 doesnt have any red lights?

post your modem stats, error log, speed test, and pingtest on here and myself, o someone else will take a look ;)

Re: Cant hold the connection for more than 8 seconds.
 

I'm in Washington mate.

I hit 50mb 99% of the time its on but as of late (Including today) I cant get the connection to stay on for more than 8-10 seconds. Using my Sky connection to post this :(

Will post all requested when I can, If it disconnects all the time as expected it may take longer than 5 minutes.

Re: Cant hold the connection for more than 8 seconds.
 

Who mentioned red lights?

Re: Cant hold the connection for more than 8 seconds.
 

Done in around 8-9 disconnects BUT I'm connected now lasting a good 5 minutes so far! VMNG300 Modem, As for the red lights thing, I assume he just misread 'Ready' :) Scan reading.

http://www.pingtest.net/result/40137212.png

https://www.cableforum.co.uk/images/...011/05/122.png

Item Status Comments
Acquired Downstream Channel 299 MHz Primary Downstream Locked
Ranged Upstream Channel 45.8 MHz Success
Provisioning State OK Operational
Ethernet Link Status Up 1000 Mbps/Full duplex



Cable Modem Downstream

DS-1 DS-2 DS-3 DS-4
Frequency 298750000 306750000 314750000 322750000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y
Channel Id 125 126 127 128
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) 7.39 7.22 6.27 6.01
RxMER
(dB) 37.36 37.09 37.36 37.09
Correctable
Codewords 0 0 0 0
Uncorrectable
Codewords 298 299 277 288


Cable Modem Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A N/A
Channel ID 4 N/A N/A N/A
Frequency
(Hz) 45800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM N/A N/A N/A
Symbol Rate
(KSym/sec) 5120 N/A N/A N/A
Mini-Slot Size 4 N/A N/A N/A
Power Level
(dBmV) 32.00 N/A N/A N/A
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 0 0 0 0
T4 Timeouts 0 0 0 0


Mon May 9 15:54:19 2011 Mon May 9 15:54:48 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 15:54:50 2011 Mon May 9 15:54:50 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 12:15:10 2011 Mon May 9 12:15:10 2011 Critical (3) Ranging Request Retries exhausted

Time Not Established Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 9 15:55:31 2011 Mon May 9 15:55:31 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 15:57:10 2011 Mon May 9 15:59:46 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 15:59:48 2011 Mon May 9 15:59:48 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 15:59:48 2011 Mon May 9 15:59:48 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:00:04 2011 Mon May 9 16:00:41 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:02:57 2011 Mon May 9 16:03:09 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:03:48 2011 Mon May 9 16:05:37 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:07:01 2011 Mon May 9 16:07:30 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:07:32 2011 Mon May 9 16:07:32 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:07:32 2011 Mon May 9 16:07:32 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:08:13 2011 Mon May 9 16:08:13 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:09:10 2011 Time Not Established Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:12:18 2011 Mon May 9 16:12:18 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:16:34 2011 Mon May 9 16:17:03 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:17:05 2011 Mon May 9 16:17:05 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:17:05 2011 Mon May 9 16:17:05 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:17:21 2011 Mon May 9 16:17:21 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:19:38 2011 Mon May 9 16:20:16 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:20:18 2011 Mon May 9 16:20:18 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:20:18 2011 Mon May 9 16:20:18 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:20:35 2011 Mon May 9 16:20:35 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:21:52 2011 Mon May 9 16:25:40 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:25:42 2011 Mon May 9 16:25:42 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:25:43 2011 Mon May 9 16:25:43 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:26:01 2011 Mon May 9 16:26:01 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:28:21 2011 Mon May 9 16:29:33 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:29:39 2011 Mon May 9 16:29:39 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:29:39 2011 Mon May 9 16:29:39 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:30:10 2011 Mon May 9 16:30:10 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:38:54 2011 Mon May 9 16:39:23 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:39:25 2011 Mon May 9 16:39:25 2011 Critical (3) Ranging Request Retries exhausted

Mon May 9 16:39:25 2011 Mon May 9 16:39:25 2011 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted

Mon May 9 16:39:39 2011 Mon May 9 16:39:41 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:39:46 2011 Mon May 9 16:44:27 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Mon May 9 16:46:05 2011 Mon May 9 16:46:05 2011 Critical (3) No Ranging Response received - T3 time-out

Mon May 9 16:46:48 2011 Mon May 9 16:51:00 2011 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f1:e3:5d;CMTS-MAC=00:30:b8:d1:c7:b0;CM-QOS=1.1;CM-VER=3.0;

Re: Cant hold the connection for more than 8 seconds.
 

I would like to see your upstream power increased as it is at rock bottom, downstream is a little high. You need a tech out to adjust your connection.

Re: Cant hold the connection for more than 8 seconds.
 

"ready light" haha, i had something on my screen and it looked like red, even now it looks like red, ill get a cloth to that haha

those downstream power level are slightly too high, only just out of spec, but its the upstream being too low thats killing your connection, and will need an engineer to adjust

Re: Cant hold the connection for more than 8 seconds.
 

Isn't that what I said?

Re: Cant hold the connection for more than 8 seconds.
 

it took me longer to type than yours, yours only popped up when i clicked reply!

Re: Cant hold the connection for more than 8 seconds.
 

No worries!

Re: Cant hold the connection for more than 8 seconds.
 

i couldnt even tell the difference between red and ready! how do you think im going to type that quick! :D:D

Re: Cant hold the connection for more than 8 seconds.
 

Learn!!!!!!!!!!!!!!

Re: Cant hold the connection for more than 8 seconds.
 

it would be quicker for me to walk to the OP's house and adjust their power levels!!

Re: Cant hold the connection for more than 8 seconds.