Online for only 5 minutes

[drewmerc]

T4 ( Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received )

Explanation: The cable modem did not received a station maintenance opportunity in which to transmit a Ranging Request (RNG-REQ) message within the T4 timeout period (30 to 35 seconds). The cable modem is resetting its cable interface and restarting the registration process. Typically, this indicates an occasional, temporary loss of service, but if the problem persists, check for possible service outages or maintenance activity on this particular headend system. This error message is DOCSIS event message is R04.0, Ranging Request.

god knows

[SniperV]

I know it is driving me crazy. My sub modem is running fine no reboots because of loss signal. I even swapped the 2 coax inputs and the modded one still goes and reboots and then it is a pickle to get back online. Sometimes I have to give it a different mac..Right now I am sending a ping to yahoo ever 3 seconds and its been up for like 7 minutes..Fingers Crossed lol..

[SniperV]

Well that lasted about 9 minutes. Not sure what to do with it now. I even took the splitter out and hooked straight to the coax. No change

---

One of my observations if I leave the modem hooked up and I don't force the computer that I am using to get online it doesn't reboot. Seems it only wants to reboot when I push traffic through it.

[SniperV]

Tried another nic mac address still a no go...I'm thinking splitting atoms is easier lol...

[drewmerc]

right now to work this out i'm gonna need a full telnet output log of the reboot

Before you start, download and install putty:

Code:

http://the.earth.li/~sgtatham/putty/latest/x86/putty.exe

Method 1 is preferred in all cases, method 2 will do tho


Method 1) Using MAX232

Remove power from the modemConnect your MAX232 adapter to the modem header and the PC. This guide assumes you're using COM1.

Open Putty. Click the logging section of the settings panel. Select the following options:

Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'

Click back onto the 'session' section of the settings panel:

Connection type: Serial
Serial line: COM1
Speed: 115200
Close window on exit: Never

Click 'open', then plug the power into the modem.
You should see the boot process and connection attempt appear.

Wait for about 20s after the connection has reached the failure point, then close putty and it'll save the txt log as putty.txt on your desktop.


Method 2) Using ethernet or USB (USB requires that USB drivers are correctly installed)

Remove power from the modem.

Set manual NIC IP 192.168.100.10.

Open Putty. Click the 'session' section of the settings panel:

Session logging: All session output
Click 'browse' and browse to your desktop folder.
Filename: putty.txt
'Always overwrite it'
Untick 'flush log file frequently'

Click back onto the 'session' section of the settings panel:

Connection type: Telnet
Host Name: 192.168.100.1
Port: 23
Close window on exit: Never


Click 'open', enter username and password and press enter. Type 'run' and press enter. The modem will try to connect.

Wait for about 20s after the connection has reached the failure point, then close putty and it'll save the txt log as putty.txt on your desktop.

Once you've finished you'll need to set auto_console back to 0 in telnet, or you'll have to type 'run' every time you reboot modem.

[SniperV]

Thanks Drew I will get that to you later this evening...as soon as I get away from this work thingy..