Modem stopped responding 4 times tonight playing WoW

[TommyTomTom]

Hi, I've been playing WoW tonight and my modem's stopped working 4 times. I've cycled the power to bring it back every time. When it happens I can't access 192.168.100.1. I live in the Staffordshire area (ST17), using an NTL: 250 modem. Here's my log just in case.

First Time Last Time Priority Description
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) The s/w filename specified in the config file is the same as ...
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) A software upgrade filename was specified in the config file.
Sat Aug 21 03:11:42 2010 Sat Aug 21 03:11:42 2010 Information (7) Authorized
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Registration complete!
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) We registered with a DOCSIS 1.1 config file!
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Received a REG-RSP message from the CMTS...
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) Sending a REG-REQ to the CMTS...
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) CableModem SNMP configure complete
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) IP init completed ok
Sat Aug 21 03:11:41 2010 Sat Aug 21 03:11:41 2010 Information (7) CableModem TFTP init ok
Time Not Established Time Not Established Information (7) CableModem DHCP client init ok
Time Not Established Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Sat Aug 21 03:09:03 2010 Sat Aug 21 03:09:03 2010 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Sat Aug 21 03:09:03 2010 Sat Aug 21 03:09:03 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:53 2010 Sat Aug 21 03:08:53 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:52 2010 Sat Aug 21 03:08:52 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:49 2010 Sat Aug 21 03:08:49 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:44 2010 Sat Aug 21 03:08:44 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:37 2010 Sat Aug 21 03:08:37 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:28 2010 Sat Aug 21 03:08:28 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:16 2010 Sat Aug 21 03:08:16 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:10 2010 Sat Aug 21 03:08:10 2010 Critical (3) No Ranging Response received - T3 time-out
Sat Aug 21 03:08:01 2010 Sat Aug 21 03:08:01 2010 Critical (3) No Ranging Response received - T3 time-out

[TommyTomTom]

I phoned up technical support and they're going to send a new modem. I've managed to get back on after the guy on the phone told me the modem is "corrupted", somehow Windows assigned an IP address other than 192.168.100.10 which was originally what DHCP was setting, this seems to allow me to connect to the internet at least temporarily.

---------- Post added at 10:15 ---------- Previous post was at 09:19 ----------

Out of curiosity, and I meant to ask the technical support guy this, does anyone know what a standard IP address issued by NTL is supposed to look like?

Also, any idea whether I'll get a newer model of modem? I asked him that and he wasn't privy to such information apparently. The 250's must be quite old by now, I remember the big grey boxes from seeing my friends, so obviously they do do revisions but I wonder at what frequency.

[Peter_]

A Virginmedia IP would be in the 62,77,81,82,86,92,195 and 213 ranges the IP you have quoted is likey from your router and is not a public IP so it sounds like you have been given duff information.

You will receive either an Ambit 256 or a Cisco EPC2100 modem and you will need to ring up to get it added to your account and activated.

[TommyTomTom]

The 192.168.100.10 address is what Windows was using, I'm not sure how to word it correctly but it was what the modem was telling the Windows machine to use via DHCP I guess. I was looking at it from the network adapter status.

[Peter_]

Originally Posted by TommyTomTom

The 192.168.100.10 address is what Windows was using, I'm not sure how to word it correctly but it was what the modem was telling the Windows machine to use via DHCP I guess. I was looking at it from the network adapter status.

The modem would take your MAC address and send it to Virginmedia's servers where it would be given a IP address in the range I posted above so the modem cannot give you that IP address as it is not a Virginmedia IP address it one that would be given via a router on the LAN side.

[TommyTomTom]

via a router on the LAN side

The modem was plugged directly into the machine.

As far as technical support were concerned the fact it was being assigned this incorrect IP address was reason enough to regard the modem as defective and issue a new one.

[Peter_]

Originally Posted by TommyTomTom

The modem was plugged directly into the machine.

As far as technical support were concerned the fact it was being assigned this incorrect IP address was reason enough to regard the modem as defective and issue a new one.

I would say that he was talking through his behind as I have never come across a modem dong such a thing as the modem receives the IP from Virginmedia which would never be in the 192 range.

You can believe what that agent told you but he was quite wrong.

[TommyTomTom]

It was me who was telling him what the IP was not vice versa, I was only looking at the network adapter status while it was set to DHCP with the modem being plugged directly into the machine.

Basically at regular intervals the modem will stop working, the ready light will start flashing and if I check either my network adapter status or my router (when it's connected) I can see the modem's for some reason started using 192.168.100.10.

When it works it's using a conventional address beginning with 82 like you said.

// For the sake of science I'm going to post the event log of the modem, I obviously have no idea what significance any of it has.

First Time Last Time Priority Description
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) The s/w filename specified in the config file is the same as ...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) A software upgrade filename was specified in the config file.
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Authorized
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Registration complete!
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) We registered with a DOCSIS 1.1 config file!
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Received a REG-RSP message from the CMTS...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) Sending a REG-REQ to the CMTS...
Sun Aug 22 14:33:40 2010 Sun Aug 22 14:33:40 2010 Information (7) CableModem SNMP configure complete
Sun Aug 22 14:33:39 2010 Sun Aug 22 14:33:39 2010 Information (7) IP init completed ok
Sun Aug 22 14:33:39 2010 Sun Aug 22 14:33:39 2010 Information (7) CableModem TFTP init ok
Time Not Established Time Not Established Information (7) CableModem DHCP client init ok
Time Not Established Time Not Established Critical (3) DHCP WARNING - Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) Beginning initial ranging...
Time Not Established Time Not Established Information (7) downstream time sync acquired...
Time Not Established Time Not Established Information (7) Downstream sync ok
Time Not Established Time Not Established Information (7) starting ds time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream lock ok
Time Not Established Time Not Established Information (7) Sync Start
Sun Aug 22 12:35:45 2010 Sun Aug 22 12:35:45 2010 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Sun Aug 22 12:34:29 2010 Sun Aug 22 12:34:29 2010 Critical (3) DHCP WARNING - Non-critical field invalid in response.
Sun Aug 22 12:34:26 2010 Sun Aug 22 12:34:26 2010 Critical (3) DHCP FAILED - Discover sent, no offer received
Sun Aug 22 12:34:12 2010 Sun Aug 22 12:34:12 2010 Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC f...
Sun Aug 22 12:33:57 2010 Sun Aug 22 12:33:57 2010 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Sun Aug 22 12:32:35 2010 Sun Aug 22 12:32:35 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:29 2010 Sun Aug 22 12:32:29 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:27 2010 Sun Aug 22 12:32:27 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:22 2010 Sun Aug 22 12:32:22 2010 Critical (3) Init RANGING Critical Ranging Request Retries exhausted
Sun Aug 22 12:32:22 2010 Sun Aug 22 12:32:22 2010 Critical (3) No Ranging Response received - T3 time-out
Sun Aug 22 12:32:21 2010 Sun Aug 22 12:32:21 2010 Critical (3) No Ranging Response received - T3 time-out

[TonyHoyle]

The modem always responds to 192.168.100.1 (for diagnostics etc.) so it's not impossible that it uses 192.168.100.10 if it can't get an IP from the local DHCP server. Bit surprised though.

Best to get a virgin engineer to look at it.

[Peter_]

Originally Posted by TonyHoyle

The modem always responds to 192.168.100.1 (for diagnostics etc.) so it's not impossible that it uses 192.168.100.10 if it can't get an IP from the local DHCP server. Bit surprised though.

Best to get a virgin engineer to look at it.

It is more likely to be a static IP for a router as the modem has no inbuilt DHCP server unlike a router.

[Ignitionnet]

Originally Posted by Masque

It is more likely to be a static IP for a router as the modem has no inbuilt DHCP server unlike a router.

Yes it does - disconnect modem from coax and release/renew your IP to confirm.

[pip08456]

You been on holiday Igni?????

[Ignitionnet]

Originally Posted by pip08456

You been on holiday Igni?????

Nope.

[pip08456]

Ain't seen you post for a while (at least in this section)

[TommyTomTom]

If I receive the new modem and problem occurs again, indicating a line fault, what should I do then? If I were to phone up again and get someone abroad, what should I say to them?

The modem seems to be working fine now by the way.