Thread Rating:
  • 1 Vote(s) - 5 Average
  • 1
  • 2
  • 3
  • 4
  • 5
Modem Went down!
foreveryoung Offline
Haxorware Enthusiast
***

Posts: 32
Threads: 4
Joined: Nov 2011
Reputation: 0
#1
Modem Went down!
Hey guys, I'm new. I was on sbhacker & C-H. Well I have a 5101 up for a year or so now. Then today I took it over to my friend and it was working fine, when I took it home back, it's stuck at ranging. Here's my info:

Frequency 315 MHz
Status Locked
Annex DOCSIS
Modulation QAM256
Symbol Rate 5360537 sym/sec
Receive Power -11.6 dBmV
Signal to Noise ratio 36.6 dB
Upstream
Frequency 33 MHz
Channel ID 11
Status Ranging
Mode ATDMA
Transmit Power 54.0 dBmV


Event Log
Time Priority Code Description
1970-01-01 00:03:18 Critical R004.0 Received Response to Broadcast Maintenance Request, But no Unicast Maintenance o
1970-01-01 00:02:06 Critical R002.0 No Ranging Response received - T3 time-out (US 11)
1970-01-01 00:01:40 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:40 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:36 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:35 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:25 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:58 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:57 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:53 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:53 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:51 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:51 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:27 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:27 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:07 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:07 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:02 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:02 Notice M573.0 Modem Is Shutting Down and Rebooting...
1970-01-01 00:01:02 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:04 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:04 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:23 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:23 Notice M573.0 Modem Is Shutting Down and Rebooting...
1970-01-01 00:00:22 Critical Resetting the cable modem due to docsDevResetNow
1970-01-01 00:00:06 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:06 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:06 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
14-11-2011, 01:20 AM
Find Reply
Mordeth Offline
Haxorware Enthusiast
***

Posts: 85
Threads: 0
Joined: Sep 2011
Reputation: 3
#2
RE: Modem Went down!
Posting the "event log" does not do SBH any justice. We need the telnet log to help you.
14-11-2011, 02:16 AM
Find Reply
skribblz Offline
Senior Member
****

Posts: 127
Threads: 0
Joined: Sep 2011
Reputation: 10
#3
RE: Modem Went down!
T3 is usually signal related, try putting closer to the drop as I can see your signals are pretty high. Also certs do matter, and your friend could just be in a node with not updated security.
No I will not help you if only have a few worthless post on the forum.
15-11-2011, 01:25 AM
Find Reply
Sesy79 Offline
Junior Member
**

Posts: 4
Threads: 0
Joined: Nov 2016
Reputation: 0
#4
RE: Modem Went down!
But I got that same problem and modem refused to connect to telnet or ssh server
18-04-2017, 09:15 AM
Find Reply
occalifornia Offline
Haxorware VIP

Posts: 939
Threads: 9
Joined: Apr 2011
#5
RE: Modem Went down!
lol at all of the people losing their stolen internet.
18-04-2017, 09:37 AM
Find Reply


Forum Jump:


Users browsing this thread: 1 Guest(s)