Sign in with
Sign up | Sign in
Your question

Router cannot connect to the internet (via cable-modem)

Last response: in Networking
Share
November 1, 2006 5:28:51 AM

Hy everyone!

I searched this forum for some topics that are related to mine but couldn't solve the problem.

I connect to the internet with my PC via a Motorola SURFboard SB5100E. I obtain an IP address dynamically from my ISP and had to give my MAC-adresse to them. Everything works fine ... so far.

Now I want to connect the MN-700 as a router between my PC and my cable modem. I get perfect connection the the LAN and I'm able to copy the MAC-adresse of my former LAN-card. Now the MN-700 has my "old MAC" as new WAN-MAC and is switched to "dynamic connection".

Problem: the cable modem isn't able to get connection to the router. The MN-700 will not get a dynamic WAN-IP ... it is always saying "no connection" (also Modem-Lights are green).

I tryed to enter the "old" dynamic IP, DNS, ... as static WAN-IP. This works ... for about 5 minutes. Then the connection is gone and i need to reset both - cablemodem and router.

Would be fine if you can help me. I am out of ideas how to go on.


Summary:

Cable-Modem => PC (dynamic IP) works
Broadband-Router (LAN) => PC (dynamic or static IP) works

Cable-Modem => Broadband-Router (WAN-port) doesnt work

Problem: Router isn't able to get a correct dynamic IP from modem
November 1, 2006 8:39:27 PM

Most all cable modems have what they call a MAC table. When ever you switch devices NIC, Router or Xbox you have to restart the modem to clear the MAC table in the modem. Soooo restart the modem and once it sync's up restart the router or renew on the router web flash. Let me know if this works.

As for a static IP on the WAN address this is a BIG NO NO. When I would monitor the network and I would find ppl that had there WAN IP static I would block there accounts. Leave the WAN IP dynamic or obtain IP automatically.
November 2, 2006 5:54:02 AM

I already cloned the MAC-address and additionally asked my ISP to change their settings to the original MAC-address of the router.

No success so far.

Is it possible, that the different subnet-maskes (WAN: 255.255.0.0 / LAN: 255.255.255.0) cause this problem? I cannot change both - the first is assigned by the ISP and the second is not changeable.


So the WAN-net is class B and my LAN is class C.

There is no chance to change that. But is this really a problem?



I disabled DHCP for my LAN, so there is a fixed 192.168.0.xx (xx is 2-99) for the clients.

The problem is, that the router shows me, that it cannot connect to the modem. There must be some kind of inkompatibility between the SB5100 (Motorola) and my MN-700 (Microsoft).

I spoke with my ISP and they have no idea. As far as that people knew, i spoke to, their cable-servers are only MAC-specific and have no other security options or other preferences, which could interfere with my router.

I'm really out of ideas now...
Related resources
November 2, 2006 8:11:46 PM

This has been way over complicated.

1. The MAC address that is on your NIC clone it to the router.
2. Set the Router to obtain IP address automatically or dynamic. All AUTO.
3. set your pc to obtain a IP automatically, then hit repair.
4. do not set any subnet mask or DNS manually in the PC or router.
5. restart modem to clear the MAC table.
6. restart the router.
7. done.

If you connect the pc to the modem and your online then this will work if the pc will not connect then they put the wrong MAC on your account. There should be a online registration page that should allow you to switch devices. Let me know we are almost there.
November 2, 2006 8:25:30 PM

That's what i did:

1. I cloned the MAC that already worked with my PC-LAN-card -> no connection
2. I asked my ISP to change the MAC to the ORIGINAL router-MAC-address -> no connection
3. Router is set to obtain IP automatically (every part ... DNS, gateway, subnet)
4. Tried both: LAN dynamic and static -> LAN is working fine with both options
5. Restarted every device more then 10 times, with different starting-sequences and different power-off-times -> no connection

If you wanna have a look at my setting, watch this picture: http://www.khelben.de/network.jpg

It shows the setting and the IPs, i get dynamically.

Try your best to find the error ...


I finally guess, that this is a rare hardware conflict between these both devices (MN-700 and SB5100E). Another possibility is that my dynamic ISP-settings are not compatible with that, what the router awaits.
Correct me, if this is bullshit :) 
November 2, 2006 8:57:17 PM

no conflict between the modem and the PC at ALL.

ok so your pc can connect fine to the modem and you surf ok done.
now we need to make sure the MAC address on your NIC is correct with the cloned MAC in the router. so right click net my network places Icon on your desktop then hit properties, double click the local area connection icon and hit support tab, then hit the details button and get the physical address ( MAC ). make sure you typed it in correctly into the router. ALSO make sure the ethernet cable from your modem is in the WAN port of the router or in the port next to the power connection on the router.

If your WAN IP in the router is a 10. address the the MAC is not registered is why you cant connect. btw who is your ISP?
November 2, 2006 11:04:46 PM

PC <-> Modem works fine ...

MAC address is the same. I also tried to change the ISP settings, so they accept the original MAC-address of the router.

Modem-Cable is on WAN port - right!


I tried to enter this dynamic IP as a static one. This works for 4-5 minutes ... then the router and all client lose connection to the internet.
Sometimes ... its random ... the router gets a part of the right dynamic settings ... e.g. the DNS and gateway ... but it never obtains the right IP from the modem.


I'm from Germany and my ISP is a lokal company which is most propably not know to you.
November 2, 2006 11:53:25 PM

If the wan ip on the on the router is nothing then there is a issue with the Ethernet cable or the wan port on the router. the ethernet port on the modem is fine cause you can surf fine with the pc. Is there a way to exchange the router for another? Like a linksys?
November 3, 2006 6:50:28 AM

The cable is OK ... i have 3 of them here and tryed all. I cannot test the WAN-port because i dont have another modem.

And switching the router is not possible too, because I dont have another one.


The only thing left to try is to change the type of modem. My ISP has to different types ... the newer Motorola with dynamic IP and an old one with fixed IP.

But changing the modem will need some time and I am not sure if this can fix the problem. When my router is incompatible with the kind of IP, I obtain, then it wont work too. Maybe I will try this next week ...
November 3, 2006 6:45:00 PM

Its not the modem trust me, do this to test the wan port on the router. Unplug the coax cable from the back of the modem and restart the router, the router should then pull a 192.168.100.2 , why you ask cause the SB5100 like the one im using has DHCP built in, once the modem sees that is has no connection to the internet it enables DHCP and will push a 192.168.100.... to the router or PC connected to it.

Also have you tried reseting the router to the factory defaults? this sux cause I know if I was there I could get you going in 5 mins.
November 4, 2006 9:22:30 AM

I'm not at home atm, but I can reply to your suggestion, cause I tried the DHCP.


As one of my uncountable tests last week i pushed the "offline"-button on the modem. (is almost like pulling the coax-cable, i guess)

The router now gets the IP, you mentioned (192.168.100.xx)

But its offline ... so no connection to the I-net.

Now I made the modem online again ... and got no connection. No wonder so far, because the router hasn't renewed his IP (still ...-...-100-...)

I waited some times if it will do this automatically ... no response. Then i pushed the "release and renew-button" in the router options ... and it got ... nothing. It lost every IP-setting and returned to "disconnected".


I got the router with factory-default, i resetted it to factory-default 2 or 3 times and i updated the firmware to the newest one. No satisfying result :( 
November 4, 2006 12:22:05 PM

well all your hardware seems to work fine man, your wan port on your router is able to pull a IP address from the modem. you connect your pc and you pull a IP address from the ISP just fine. You chould be able to clone that mac off the pc to the router and it should pull an IP address from your ISP in seconds. When you clone the MAC to your router is there blocks of 2 like XX XX XX ... or is it one long block you type into? If it one long block are you doing XX-XX-XX-XX....? The other thing is if your ISP wrote down the wrong MAC for the router if this is true then your PC wouldn't be able to connect either. This is just retarded I know your frustrated as I would be.

The ISP I worked for for years did it this way for the first few years I was there.
1. the modem MAC was put on the account at the start.
2. when you had the modem up and you connected the PC, XBOX, Router to the modem any of these devices would pull a 10. address which would take you to a registration site.
3. Once at the registration site HTTP, it would say this device is new would you like to switch this device as the NEW device you would hit yes and it would put the new device's MAC address in and you would restart the device and pull the public IP address and then would be able to surf. DONE.

Then later they got rid of this to where you could plug any device behind the modem and it would work fine as long as you restarted the modem and cleared the MAC table. This saved me like tons of dumb phone calls.

The problem im trying to figure out is how in the hell your ISP is working when you plug a new device into the modem. 1 does it not pull any IP at all if so thats stupid. This means you have to call in every damn time you hook a new PC, router, Xbox to the modem.
November 4, 2006 1:34:04 PM

The one thing, i know for sure is, that the tech on the other side of the phone is really busy. Atm I have been waiting for 4 days to change my connection-speed from 128kbit to 2100kbit. It should have been done on November 1st.
But there is no alternative ... Germany isn't a country of cable users. Most of us view TV by ASTRA satelite and surf with DSL 6-16k which is cheaper and more reliable.

And my only opportunity to get I-net is the cable thing (I'm student and cable is only 20€ per month incl. everything (flatrate, TV))

I troubled you longer than I intended and the situation is stuck. Just to answer some of the last questions you had:

After my ISP changed the MAC to the original router-LAN-MAC (which i cloned too, because router-settings show always 2 MACs: LAN and WAN) i got no connection with my PC. So I guess, the guy typed in correctly.

I also asked him, if he can disable the MAC-specific registration but he said, that this is not possible. It is also not possible to register an alternative MAC.


I have some last questions to you:

Is it possible to access the router more "deeper"? I tried almost every setting which is accessable by the HTML-site of it. Are there hidden options?

Is it possible to access the cable-modem (by IP)? Or is the ISP the only one, who might change settings on the modem? Can I update the firmware of the modem? (i searched the net for this hardware, but wasn't able to find anything helpfull)


My ISP offered me to change the modem to an older one. This older one has no dynamic IP but is accessable by fixed IP, which I would recieve by my ISP. This wouldn't be perfect because that kind of modem is ugly, huge (it has a cooling grill upside!!!) and i guess not that fast or reliable.

The thing is: the IP wouldn't change completely. It is very similar to the one, i obtain automatically. So if the router has a problem with that specific kind of IP the problem won't be solved.
Othervise the modem-changing is time-expensive and will cost me 2 or 3 days of stress with my ISP, lacks of I-net-connection and study-time. Atm I consider if it's worth it.

The current setting is, that I connect to the modem with my PC and provide this connection with the LAN over a second LAN-card. The router is now only for splitting my LAN. This works, but I need to leave my PC online all the time. The other option is much more comfortable!

Nevertheless, thanks for your help, mate!

I really appreciate that and it gives me some kind of sedation to know, that it's not my fault if that stupid configuration isn't working. Maybe that ISP-modem-router-setting is just not compatible for what-ever reason.
November 4, 2006 9:08:43 PM

From everything I have read, it possiable that you router is not cloaning your mac address, BAD Router, RMA it.

I discovered on a couple of router I set up one time soon as a I made the wan setup with the clone MAC I had to reboot the router for the setting to take place. Then if you change the default lan IP, reboot is also required for the router and PC. Or Disable port for 10 sec then enable for it to get the proper IP address.

Just a thought.
November 4, 2006 9:15:10 PM

After my ISP changed the MAC to the original router-LAN-MAC That is the problem man.

First device is the modems cable connection then to the Ethernet or USB connection (ethernet on this one). Then it goes to the WAN MAC not the lan mac on the router.

So with that said the device behind the modem is the WAN MAC of the router or the MAC of your PC the NIC. So if your pc is online then all you need to is take your PC's NIC MAC and clone it to the WAN MAC on your router so your ISP thinks its your PC connected thus fooling the ISP in thinking its your PC connected to the modem not the router.

The ISP only cares about what MAC is connected to the modem to authenticate to get a public IP address to surf. I usta have techs I worked with put the LAN MAC of the router into our system and the router would never surf this is a huge common problem of dumb techs.
November 6, 2006 5:35:47 AM

I tried to do everything, you adviced:

Quote:


Modem disabled
LAN-PC disabled
Router restarts after reset to factory default


1999/06/01 12:00:04 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:04 **** Device Booted: Version 02.01.02.0590
1999/06/01 12:00:05 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:09 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:12 RF Reset...Pass
1999/06/01 12:00:18 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:19 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:21 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:25 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:33 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:34 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255
1999/06/01 12:00:35 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255

LAN-PC (dynamic IP) enabled

1999/06/01 12:00:36 192.168.2.68 login successful
1999/06/01 12:00:39 DHCP Client : Request sent from 0.0.0.0 to 255.255.255.255

LAN-DHCP disabled
LAN-PC (static IP) enabled


1999/06/01 12:01:44 192.168.2.68 logout
1999/06/01 12:01:44 192.168.2.2 login successful

MAC-address cloned -> Router restarts

1999/06/01 12:00:05 **** Device Booted: Version 02.01.02.0590
1999/06/01 12:00:10 192.168.2.2 login successful

Current Base station information:

Runtime code version: 02.01.02.0590
Boot code version: 02.01.02.0590
LAN MAC address: 00-0D-3A-23-FB-97
MAC address: 00-C1-26-0A-D5-B4 (this is the original LAN-MAC, which is registered at my ISP)
Serial number: 468090175555
Hardware version: 00.00.00.0004



Router disabled (switched power off)
Modem enabled (Power on, Recieve on, Send on, Online on)
Router enabled



1999/06/01 12:00:05 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:05 **** Device Booted: Version 02.01.02.0590
1999/06/01 12:00:07 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:08 DHCP Client : Obtained lease for 0.0.0.0 on 1969/12/31 15:59:59 ; lease expires on 1901/12/17 00:16:31
1999/06/01 12:00:11 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:12 RF Reset...Pass
1999/06/01 12:00:14 192.168.2.2 login successful
1999/06/01 12:00:21 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:22 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:23 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:27 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:35 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:37 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:40 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:00:44 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22


==> Broadband connection: Disconnected

Modem offline
Router: renew dynamic IP


1999/06/01 12:03:28 DHCP Client : Server response sent from 192.168.100.1 to 192.168.100.11
1999/06/01 12:03:28 DHCP Client : Server response sent from 192.168.100.1 to 192.168.100.11
1999/06/01 12:03:28 DHCP Client : Server response sent from 192.168.100.1 to 192.168.100.11
1999/06/01 12:03:28 DHCP Client : Server response sent from 192.168.100.1 to 192.168.100.11
1999/06/01 12:03:31 DHCP Client : Obtained lease for 192.168.100.11 on 1999/06/01 12:03:28 ; lease expires on 1999/06/01 12:03:48

WAN-status:

Broadband connection: Connected
WAN IP address: 192.168.100.11
Subnet mask: 255.255.255.0
Default gateway: 0.0.0.0
Primary Domain Name System (DNS): 0.0.0.0
Secondary DNS:


Modem online
Router: renew dynamic IP


1999/06/01 12:04:27 DHCP Client : Request sent from 192.168.100.11 to 192.168.100.1
1999/06/01 12:04:27 DHCP Client : Server response sent from 192.168.100.1 to 192.168.100.11
1999/06/01 12:04:27 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
1999/06/01 12:04:29 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22
.
.
.

This will be repeated 10-20 times without results

WAN-status:

Broadband connection: Disconnected
WAN IP address: 0.0.0.0
Subnet mask: 0.0.0.0
Default gateway: 0.0.0.0
Primary Domain Name System (DNS): 0.0.0.0
Secondary DNS:




And here is, what the modem-log says (i cannot put this in order, cause time isnt compareable)
Read from bottom to top (newest is top)!

Quote:


1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:22 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:23 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:23 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:14 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:17 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:21 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:21 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:02:54 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:30 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:30 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:23 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:23 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:20 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:19 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:18 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:15 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:14 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:11 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:10 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:10 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:09 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:02:03 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:02:03 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:55 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:55 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:39 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:39 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:38 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:37 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:35 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:35 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:34 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:34 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:17 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:17 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:01:08 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:01:08 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:52 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:52 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:48 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:48 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:47 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:47 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:27 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:27 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:26 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:25 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:25 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:24 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:24 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:21 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:21 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:20 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:13 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:13 3-Critical 0x0501BD64 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing
1970-01-01 00:00:02 3-Critical 0x0501BDC8 SYNC Timing Synchronization failure - Failed to acquire FEC framing
1970-01-01 00:00:18 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:18 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:21 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:21 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:20 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:19 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:14 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:22 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:22 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 01:20:21 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:16 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:19 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:18 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:15 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:15 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:13 4-Error 0x040D9A93 ToD request sent- No Response received
1970-01-01 00:00:13 3-Critical 0x040D9A2C DHCP WARNING - Non-critical field invalid in response.
1970-01-01 00:00:16 4-Error 0x040D9A93 ToD request sent- No Response received



I dont know, if you can trust the modem-log because i didn't see any changes when i restart it or unplug any cables.

So any idea, how to clear it?
November 6, 2006 5:39:33 AM

I forgot modem status and signal:

Quote:
Acquire Downstream Channel - Done
Obtain Upstream Parameters - Done
Establish IP Connectivity using DHCP - Done
Establish Time Of Day - Done
Transfer Operational Parameters through TFTP - Done
Register Connection - Done
Cable Modem Status - Operational
Initialize Baseline Privacy - Skipped


Quote:
Downstream - Value
Frequency - 610000000 Hz Locked
Signal to Noise Ratio - 35 dB
Power Level - 5 dB
(The Downstream Power Level reading is a snapshot taken at the time this page was requested. Please Reload/Refresh this Page for a new reading )


Quote:
Upstream - Value
Channel ID - 21
Frequency - 44000000 Hz Ranged
Power Level - 45 dBmV
November 6, 2006 7:09:38 PM

DUDE just like I said your wan port on your router pulled a 10. address.
1999/06/01 12:04:29 DHCP Client : Server response sent from 10.10.255.254 to 10.10.2.22

Is there a DNS address when you pull a 10.10.2.22 from your ISP. Once you pulled this 10.10.2.22 did you restart the modem and release and renew again? If you keep pulling a 10.10.2.22 then the ISP see's this as a diff MAC. Whats the MAC address of your NIC.
November 6, 2006 7:36:28 PM

I fear, you are wrong in this point. When I get a dynamic IP with my original LAN-card i get following:

IP: 10.10.2.22
Subnet: 255.255.0.0
Gateway: 10.10.255.254
DNS: 83.221.230.130


The MAC address which works is visible in the log (at current base-station-information) (00-C1-26-0A-D5-B4)
This one is my LAN-MAC and the cloned WAN-MAC.

Is there a chance to test, if it is really the WAN-MAC? I tried to plug in my LAN-card into the WAN-port but I cannot read out anothers device's MAC.



Other Point: What is wrong with this time-stamp? May this be a problem for the DHCP (lease-timings)?
November 6, 2006 8:29:35 PM

WTF a 10. address is a private address not a public address. something is way weird here man. dude whats your MSN nick? PM me. Are you on a campus of a school or something? This is to funny sorry man.
November 7, 2006 7:41:47 AM

I got nothing, I see what your saying, unless you can somehow disable your Router internally... Can you even turn off the router gateway if it isnt a combi-modem?

I never really liked Dynamic on the Cable Modems. The old manual settings were much more, intuitive, and not prone to drive you insane.
November 8, 2006 3:22:11 PM

Yes, it is a seperated part of a campus network.


I finally got another modem, which works. It is old and huge, but has a static IP.

Now the router is sharing the connection properly.


Thanks for your help, but me and my ISP were not able to set the dynamic modem in the right way to work with my router ... maybe it is just impossible ;) 

Bye,

Kronos
!