Need info!

[aebyss]

Hello there

I'm new to this forum as you can see. I registred to ask question about my modem and I want to know if its blocked somehow or something similar.


Well I've flashed to haxorware about 2 years ago was using it all untill now never had any problems.
This morning internet went down for a hour or so came back and then I tried to surf abit and went again down. So I checked my macs switched it same crap it wont pass upstream. I suspect that i got blocked somehow but I'm not quite sure if that is possible. If it is do I need to change modem and reflash it or?

Here is my Ds and Us


Frequency 754 MHz
Status Locked
Annex EuroDOCSIS
Modulation QAM256
Symbol Rate 6952000 sym/sec
Receive Power -19.5 dBmV
Signal to Noise ratio 28.5 dB

Upstream


Frequency 58 MHz
Channel ID 2
Status Ranging
Mode ATDMA
Transmit Power 40.2 dBmV

Thanks

E

[neo_]

Your cable is unplugged or something is wrong with your tuner.

[aebyss]

Thanks for reply but I guess thats not the problem here is my telnet log.

******************************************
DOWNSTREAM STATUS
******************************************
Tuner Frequency = 738000000 Hz
Carrier Offset = -6 Hz
Symbol rate = 6952000 sym/sec
SNR = 31 dB
QAM Mode = QAM256
Tuner AGC = 0xfff00000
IF AGC = 0x1a3395a1
Power Level = -18 dB
QAM = LOCKED
FEC = LOCKED
******************************************

CM> Selecting UCD for Us Channel 1

0x0004d3b4 [CmDocsisCtlThread] BcmCmDocsisCtlThread::TestAndLaunchDsTimeSync: ( CmDocsisCtlThread) starting ds time sync acquisition...
0x0004d652 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtl Thread) downstream time sync acquired...
0x0004d652 [CmDocsisCtlThread] BcmCmDocsisCtlThread:sSyncOkResumeUsInit: (CmD ocsisCtlThread) pre-REG upstream target case...starting initial ranging.
Beginning initial ranging...
Using default initial upstream power = 8.0 dBmV
0x0004d652 [CmDocsisCtlThread] BcmCmDocsisCtlThread::SyncDsSyncOk: (CmDocsisCtl Thread) rx unexpected kDsSyncOk indication...
Not logging event ID 2307948724, control for level 7 is 0.
CM> Adjusting the initial ranging power to 33.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 46.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> 0x0004ded6 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Serv er Thread) Callback request expired:
timerDuration secs = 1
current time secs = 319
elapsed time secs = 1
CM> Adjusting the initial ranging power to 21.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 52.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
Adjusting the initial ranging power to 39.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 27.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 14.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 55.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> 0x000509d8 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Server Thread) Callback request expired:
timerDuration secs = 1
current time secs = 330
elapsed time secs = 1
CM> Adjusting the initial ranging power to 49.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 42.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> Adjusting the initial ranging power to 36.0 dBmV...
Logging event: No Ranging Response received - T3 time-out (US 1)
CM> 0x000557b2 [DHCP Server Thread] BcmDhcpServerThread::ThreadMain: (DHCP Server Thread) Callback request expired:
timerDuration secs = 1
current time secs = 350
elapsed time secs = 1
0x000557b2 [DHCP Server Thread] BcmDhcpServerIf::ElapsedTimeSec: (DHCP ServerIf Instance(1) for IP Stack2) Lease 192.168.100.11 : htype=0, value=bc 5f f4 d2 d5 43 has EXPIRED!

[neo_]

Maybe a bad splitter, line damaged, etc...

It's a wiring issue. Your dbmv is outside of any reasonable spec.

[aebyss]

Could my cable provider screw something up intentionaly?

I'll begin testing my wiring.

[neo_]

If you have another modem, try it to rule out the modem's fault.

Try switching splitters to eliminate that.

Check every connecting point and ensure the connectors are screwed tight.


They technically can install a high pass filter on the tap, although I don't recall if it will still allow your modem to lock or not.

[aebyss]

Thank you Neo!

I discovered wiring problem!

Many thanks!

E

[neo_]

You're welcome.