Connection Problems 50mb

[Pixel8ted]

Connection dropping on daily basis.Not sure how often as i have not been on the computer much of late due to ill health.Also have problem when downloading large demo files on Xbox360(ethernet cable to modem WRN2000) - continually stopping & having to restart download.

Connection does restart itself on occasion,however a reboot is often needed. Stats below.My downstream Power levels look a bit high but not sure.Any help is much appreciated..Thanks in advance



Cable Modem Downstream
DS-1 DS-2 DS-3 DS-4
Frequency 299000000 307000000 315000000 323000000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y
Channel Id 13 14 15 16
Modulation 64QAM 64QAM 64QAM 64QAM
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.03 6.71 6.24 6.76
RxMER
(dB) 38.21 38.21 38.55 39.35
Correctable
Codewords 0 0 1 0
Uncorrectable
Codewords 241 774 243 792



Cable Modem Upstream
US-1 US-2 US-3 US-4
Channel Type 1.0 N/A N/A N/A
Channel ID 3 N/A N/A N/A
Frequency
(Hz) 37500000 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) 2560 N/A N/A N/A
Mini-Slot Size 2 N/A N/A N/A
Power Level
(dBmV) 36.21 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 18 0 0 0
T4 Timeouts 1 0 0 0



Tue Jun 1 21:30:55 2010 Wed Jun 2 02:01:23 2010 Critical (3) No Ranging Response received - T3 time-out;
Wed Jun 2 02:01:53 2010 Wed Jun 2 02:01:53 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Wed Jun 2 02:01:58 2010 Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Thu Jun 3 19:57:09 2010 Thu Jun 3 19:57:20 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Thu Jun 3 23:46:47 2010 Sat Jun 5 19:02:36 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 07:28:37 2010 Sun Jun 6 07:28:37 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 08:12:06 2010 Sun Jun 6 08:12:06 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 08:12:08 2010 Sun Jun 6 08:12:08 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 08:48:56 2010 Sun Jun 6 08:48:56 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 10:04:28 2010 Sun Jun 6 12:45:35 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 14:41:02 2010 Sun Jun 6 21:04:24 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 21:04:54 2010 Sun Jun 6 21:04:54 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 21:04:58 2010 Sun Jun 6 21:05:04 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 21:05:05 2010 Sun Jun 6 21:05:05 2010 Warning (5) B-INIT-RNG Failure - Retries exceeded;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 21:05:15 2010 Sun Jun 6 21:53:57 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 22:01:14 2010 Sun Jun 6 22:05:12 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 22:38:06 2010 Sun Jun 6 22:38:06 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 23:36:03 2010 Sun Jun 6 23:36:03 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Sun Jun 6 23:36:47 2010 Sun Jun 6 23:37:20 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 04:43:07 2010 Mon Jun 7 04:43:07 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 09:01:25 2010 Mon Jun 7 09:01:25 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 12:22:03 2010 Mon Jun 7 14:33:14 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 16:10:51 2010 Mon Jun 7 18:09:17 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 18:29:12 2010 Mon Jun 7 18:29:12 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 19:20:03 2010 Mon Jun 7 23:13:42 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:14:00 2010 Mon Jun 7 23:14:00 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:17:52 2010 Mon Jun 7 23:17:52 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:20:36 2010 Mon Jun 7 23:20:36 2010 Critical (3) SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:21:02 2010 Mon Jun 7 23:21:02 2010 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:21:10 2010 Mon Jun 7 23:23:36 2010 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:23:39 2010 Mon Jun 7 23:23:39 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:0d:66:23:f8:01;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:24:00 2010 Mon Jun 7 23:24:22 2010 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:24:34 2010 Mon Jun 7 23:24:34 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:0d:66:23:f8:01;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:24:41 2010 Mon Jun 7 23:28:16 2010 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:28:29 2010 Mon Jun 7 23:28:29 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=00:0d:66:23:f8:01;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:28:36 2010 Mon Jun 7 23:30:39 2010 Warning (5) MDD message timeout;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;
Mon Jun 7 23:30:54 2010 Mon Jun 7 23:31:15 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 8 08:25:46 2010 Tue Jun 8 08:25:46 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 8 11:24:30 2010 Tue Jun 8 11:24:30 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;
Tue Jun 8 11:26:49 2010 Tue Jun 8 12:07:28 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=;CMTS-MAC=:a0;CM-QOS=1.1;CM-VER=3.0;

[Kymmy]

MAC's removed from post, please do not post MAC's of cable modems and/or serial numbers

[Pixel8ted]

Originally Posted by Kymmy

MAC's removed from post, please do not post MAC's of cable modems and/or serial numbers

Thank you & my apologies.

[Peter_]

If you call in on 0800 052 0431 one of my colleagues will be able to help you.

[merlintt]

I only use my 50meg for my xbox its plugged straight into modem.I also noticed that my downloads get stuck,usually around 10%.

I never noticed this snag on the 20meg connection.

I`ve spoken to the uk 50meg team about problems when using xbox but tbh they weren`t much help.( no offense meant to anybody who works there)

My connection seems ok ,good ping and downloads.

The only thing I`ve noticed that seems to help is rebooting the modem before I turn on my xbox.

[Gavin78]

Seems to be happening to a lot of people lately this with downloading files with the same modem.

Would be interesting to see the outcome of this. When I rang V today they did a line test and couldn't find anything. they told me to call back when modem goes off.

I've been connected direct today and it seems ok but then it can go like this for hours and then stop working again.

[Ignitionnet]

Power Level (dBmV) 36.21

Excessive power adjustments most likely. This is not a possible upstream power level.

[General Maximus]

Originally Posted by Ignitionnet

Excessive power adjustments most likely. This is not a possible upstream power level.

Because it is too high or too low? I have been having the same problem as the OP over the last 24 hours and my upstream power level is 48.25 atm?

Where does everyone live? I am in Lincoln. The Indian dudes have told me my modem is faulty but if you guys are in the same area I know the modem is fine and the problem lies elsewhere.

[Chrysalis]

there seems to be a lot of modem swaps that occur on VM

either high failure rate or a swap and hope policy

[pip08456]

Originally Posted by Ignitionnet

Excessive power adjustments most likely. This is not a possible upstream power level.

Could you expand on this please Igni as Masque's sticky states

"* Upstream signal levels (from the modem) should be between 34 and
55dBmV."

[Peter_]

Originally Posted by pip08456

Could you expand on this please Igni as Masque's sticky states

"* Upstream signal levels (from the modem) should be between 34 and
55dBmV."

Power adjustments within the modem caused by FEC errors, T3's and such like.

[Ignitionnet]

Power adjustments are a standard part of operation as network conditions change due to heat, etc, however if a modem has to increase or decrease its' transmit power by 3dBmV or more at one time this is abnormal. These are considered to be indicative of possible upstream issues.

There is a target receive power at the CMTS and the modem adjusts its' transmit power as directed by the CMTS in order to reach this target. If a connector comes loose or an amplifier runs into strife and the power level that reaches the CMTS from the modem drops from say 0dBmV, which is the target receive power level, to -4dBmV the next time periodic station maintenance happens the CMTS will direct the modem to increase its' transmit power by 16 0.25dBmV increments to get the receive power back to 0dBmV and increments the power-adjust counter it holds for the modem in its' flap list.

They are not caused by FECs or T3s, they are caused by electrical and optical changes on the return path, these same changes can cause FECs and T3s.

36.21dBmV is an impossible transmit value because the modems increment transmit power in 0.25dBmV steps, all transmit power should end in .00, .25, .50 or .75 with the exception of 58.21dBmV which the Ambit 300 uses to indicate that it is transmitting at maximum.

[pip08456]

Thanks for that Igni. As usual you enlighten us.

[Chrysalis]

Originally Posted by merlintt

I only use my 50meg for my xbox its plugged straight into modem.I also noticed that my downloads get stuck,usually around 10%.

I never noticed this snag on the 20meg connection.

I`ve spoken to the uk 50meg team about problems when using xbox but tbh they weren`t much help.( no offense meant to anybody who works there)

My connection seems ok ,good ping and downloads.

The only thing I`ve noticed that seems to help is rebooting the modem before I turn on my xbox.

xbox live is hard to diagnose, sometimes downloads may seem slow but of course you cannot view live throughput speeds in the xbox gui. Also the xbox live servers I think do not have particurly high capacity and are certianly not as high performing as the rest of microsoft's network.

[pip08456]

As with any network server load can cause problems.