Trouble connecting to Internet- DPC2100R2

[sayonee]

Hello there I am trying to connect to the internet using a DPC2100R2( Scientific Atlanta)haxorware installed modem.I have successfully uploaded the config file with the desired Download & Upload speeds.

But if I try connecting to the internet it fails.I have tried to access the information from the overview link available from the URL- http://192.168.100.1 and I get messages like trying..scanning... and eventually the internet just doesn't work.

Is there a way the ISP can find out about the firmware in the modem and is there a way the ISP can come to know the make of the modem??

If I try deleting the haxorware config file and the autoserve config file then,the new config file obtained from the ISP server contains the old default values and the modem works and I am able to connect to the Internet.

But as just described above If I try uploading my own modified config file the modem just fails to connect to the internet!!

Is there anything that I am missing?? about how to correctly load the config file?? or any other setting in Haxorware??. I was able to connect to the Internet using my own config file for almost 6 months,but now since I had disconnected the Internet this issue has come up....

Please let me know if there is a way to put the modem back online using the modified config file.

Thanks

[drewmerc]

does the internet work when your not forcing a config? as if not stop trying to force and learn the basics first (see now i know you dont know the basics as you have no idea about spoof settings)

learn to walk before you start running

[sayonee]

Ok drewmerc sorry if I have disappointed you,I am just a newbie to this ...what I m trying to convey here is that the modem was working with the modified config file since past 6 months or so...but now I have tried to force the config file again and this time it doesn't work ....I would like to know if the ISP would be using some kind of checksum on the forced config file by the same name I have uploaded.

Also if you think that my basics aren't right then please let me know about the first step ..I can't access such forums when the internet is working for obviously the ISP has blocked certain sites like these ... I had successfully uploaded and forced the config file and was trying the same now...But now things are different ...please correct me where I would be going wrong precisely .....


Thanks and regards

---

I have already spoofed the MAC address of the new modem to an old one and I am using this old modem with spoofed MAC to connect using the forced config file...sorry about this got slipped from my mind while reading your reply....the same old modem was working flawlessy for the past 6 months or so but now this fails ...I haven't changed anything regarding the addresses ...just trying to change the speed rates in config file and trying to autoserve it ...

[drewmerc]

so the modem was working see it's this line in the first post that thru me off

Is there a way the ISP can find out about the firmware in the modem and is there a way the ISP can come to know the make of the modem?

as it's the reason haxorware has spoof settings (tho it's not foolproof)

but yes configs can be signed(over simplified) i myself have not been able to force for 2 years so i guess your isp is doing security updates

[sayonee]

Ok Drewmerc thanks for your reply the reason I asked this question "Is there a way the ISP can find out about the firmware in the modem and is there a way the ISP can come to know the make of the modem?" is because I was suspecting the modem wasn't working because there may be something at other end which can by some means detect a firmware change or modem make change thus denying that modem internet connectivity ....anyways I have to look for alternative and moreover just for your info the ISP here is providing a login page.

Only after successful login one can access the Internet ...I would like to know if there is any workaround to this issue.Inspite of this new login facility the modem was working fine at the speeds I had configured ...but now a mere autoserving of the config file just keeps the modem scanning and ultimately it can't connect....please let me know is there any means of restoring custom config file ..I use Vulture docsis editor and when I edit and save the config file by same name I get a dialog box message asking for security key which I just leave blank and click on Ok.


Whats strange is if I upload the config file with original values the modem works so I am suspecting it could be that once the config file is downloaded the "Checking security" feature as shown in Haxorware does a checksum (because along with the change in modem speed the checksum from my end will not match with the one from ISP) hope my logic is correct ..just a guess

I have been trying to overcome this issue since a week ...please let me know in case there is way to bypass this security update if any...

[ABMJR]

TFTP bypass is most likely enabled...What ISP is this?

[sayonee]

TFTP bypass is most likely enabled...What ISP is this?

TFTP bypass is not enabled and moreover sorry about ISP info ... I went to settings and checked "Tftp Enforce Bypass" while uploading the config file ...then restarted the modem and the IPaddress assigned is 192.168.100.11 ,and it keeps scanning forever ....config files is autoserved but doesn't seemed to be recognized by the server.... Please let me know the importance of this TFTP bypass

Do you think ISPs do MD5 checksum on these configs from the server ...because I see the scanning is stuck at these labels

"Negotiate security,Receive configuration,Register connection " when i open http://192.168.100.1/overview.html
Following is the log if incase this would be of some help

Time Priority Code Description
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
2012-01-20 21:41:47 Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-01-20 21:41:40 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:38 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:36 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:33 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:33 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:30 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:24 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:20 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:19 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:41:18 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:41:18 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
2012-01-20 21:41:16 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:41:07 Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted
2012-01-20 21:38:11 Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-01-20 21:37:42 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:37:40 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:37:39 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:36:59 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:36:58 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:36:39 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-01-20 21:36:08 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:36:06 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:36:05 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:35:50 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-01-20 21:35:44 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:42 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:35:33 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:32 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:35:31 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:31 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:35:30 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:35:27 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:26 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:35:26 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:25 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
2012-01-20 21:35:23 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:35:15 Notice M571.1 Ethernet link up - ready to pass packets
2012-01-20 21:35:08 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-01-20 21:35:07 Notice M571.4 Ethernet link dormant - not currently active
2012-01-20 21:35:00 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:35:00 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:34:59 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:34:43 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:34:18 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:34:18 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:34:17 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:33:44 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:33:43 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:33:43 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:33:43 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:33:39 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:33:38 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:32:58 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:32:43 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
1970-01-01 00:00:06 Notice M571.1 Ethernet link up - ready to pass packets
1970-01-01 00:00:05 Notice M571.4 Ethernet link dormant - not currently active
2012-01-20 21:28:27 Critical D006.0 TFTP failed - configuration file NOT FOUND
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
2012-01-20 21:28:04 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-01-20 21:28:04 Critical Resetting the cable modem due to docsDevResetNow
2012-01-20 21:27:58 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:27:36 Critical D006.0 TFTP failed - configuration file NOT FOUND
1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
2012-01-20 21:27:07 Notice M573.0 Modem Is Shutting Down and Rebooting...
2012-01-20 21:27:07 Critical Resetting the cable modem due to docsDevResetNow
2012-01-20 21:17:02 Critical R002.0 No Ranging Response received - T3 time-out (US 1)
2012-01-20 21:16:35 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:16:35 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:16:17 Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-01-20 21:15:48 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:48 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:47 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:47 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:46 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:15:35 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:33 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:24 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:23 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:22 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:22 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:21 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:20 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:18 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:17 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:15:16 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:15:15 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:14:58 Critical R002.0 No Ranging Response received - T3 time-out (US 4)
2012-01-20 21:14:49 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:14:48 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:14:47 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:14:29 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
2012-01-20 21:14:05 Critical T002.0 SYNC Timing Synchronization failure - Failed to acquire FEC framing
2012-01-20 21:14:04 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

---

if you can carefully look its strange that the year is 1970 and not 2012 when successfully connnected( default config file from server and not forced config file)...I don't understand why 01-01-1970 ...the modem doesn't have a internal clock ...just absurd to think of such a thing

1970-01-01 00:00:05 Notice M571.1 Ethernet link up - ready to pass packets
2012-01-20 21:41:47 Critical R002.0 No Ranging Response received - T3 time-out (US 2)
2012-01-20 21:41:40 Critical T001.0 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

[ABMJR]

the year is epoch time, then the TOD server gives you the time..

2012-01-20 21:41:18 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
2012-01-20 21:41:16 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:41:07 Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted

T-3 timeout T-2 timeouts?

Seems you have new security...Unless your smart, you may be done

TFTP bypass is forced on the CMTS..and yes, MD5 checksums are done for the config, so editing them wont help. There are a few tricks to making this work, but they are not posted anymore...

many issues...

Learn to use a TELNET log...what you posted is useless...

[sayonee]

the year is epoch time, then the TOD server gives you the time..

2012-01-20 21:41:18 Notice M572.0 Ds Lock Failed - Reinitialize MAC...
2012-01-20 21:41:16 Notice M572.0 Neg Or Bad Reg Rsp - Reinitialize MAC...
2012-01-20 21:41:07 Critical R003.0 Init RANGING Critical Ranging Request (17) Retries exhausted

T-3 timeout T-2 timeouts?

Seems you have new security...Unless your smart, you may be done

TFTP bypass is forced on the CMTS..and yes, MD5 checksums are done for the config, so editing them wont help. There are a few tricks to making this work, but they are not posted anymore...

many issues...

Learn to use a TELNET log...what you posted is useless...

OK many tricks such as what ...can you please give links and why are they not posted anymore ...please let me know ....atleast you can PM them to me ... I am desperate to get this working .....

Also i would like to know about the MD5 checksum on config file ..So you mean to say the forced config file's MD5 checksum is crossverified with the original from the server????

many issues indeed ....so please let me know about these...

Thanks and regards

[drewmerc]

you wont get links to the trick because they are not published, they are not published simply because if only a few people use the trick it's not worth the cable companys time and effort to fix it, if it becomes public it will stop working
the only way to the trick is to learn it yourself (look how many post i have and yet i don't even know it, but then i have never tried to discover it myself)