Cant Resolve IP Address

[linskyjack]

Hello,

I just went from DSL to Cable. My problem is that my nic 3Com gigbit LOM doesn't seem to be able to resolve an IP---I get 0.0.0.0 I know its not the 3com because it works fine when I discconect and go back to DSL (man am I glad I diddn't cancel my DSL yet) Reloaded drivers, rebooted cable modem etc. Just as a long shot, I thought I would ask in here before canceling the service. Its OOL by the way.

 

[natcom]

Get the latest drivers for your network card and did you get some kind of setup cd ?

 

[tronh]

you need to check with your ISP. The cable modem may be configured as a bridge or as a router, but you should be getting an IP address from the ISP edge router (if your modem is in bridge mode) or from the modem itself if it is in router mode. DHCP may not be enabled by default on the cable modem, or they may have accidentally sent you one that was not configured, or it may be fubar and in need of replacement. ISP should be able to access it remotely if it is working at all.

 

[JohnWill]

Since your DSL is probably using PPPoE, you may have to reconfigure your networking or uninstall the DSL software that you installed to use the DSL service.

 

[linskyjack]

Nope---to all of the above. I never installed PPPoe for my DSL, I have the latest drivers, already checked with my ISP (Cablevision--OOL ) and they reset modem. Just one of those technological mysteries.

 

[tronh]

back to the basics:
do you get a link light when you connect to the ethernet port of the cable mdoem?
can your ISP access your modem (you say they reset it, but can the ping and telnet to it?)
Have they verified that the cable modem has DHCP enabled? (or that it's in bridge mode and that you should be getting an address from their network)?
What OS are you using? If you are set for DHCP and there is no response to the DHCP broadcast request, you should default to the "autoconfiguration" IP address, not 0.0.0.0 (but that may be a config option in network properties).
Do you see any packet activity on the ethernet port of your cable modem (assuming there is an activity LED) when it is attempting DHCP negotiation?
Have you tried (at the command prompt): ipconfig /release, then ipconfig /renew? Or, in XP, a "repair" operation when looking at the connection status?

 

[linskyjack]

I can ping and telenet it--I get a perfectly lit display. No packet activity, I have renewed. IP's are assigned via Cable Vision--it wont assign me one. Wierd thing is that it has worked. although briefly--on reboot it wont work.

 

[tronh]

what operating system do you use? and do you have more than 1 network adapter?

You said you can ping and telnet it - from where? Not from your PC if you don't have an IP address. Did you mean that CableVision can ping and telnet to the modem?

Might be time for CableVision to come out and fix it.

 

[linskyjack]

I use Windows XP and only have the 3Com gigabit LOM chip as my NIC. I'm sorry--I meant to say I can't ping it----By the way---I had cable vision out here already--they got it running but as soon as I turned it off and then rebooted it wont work.

 

[linskyjack]

cable vision

 

[downtime]

Well, if they charged you for it, you might want to ask them to complete the job. If they didn't, call them back.

 

[linskyjack]

Found out that the problem is that my DHCP process was set to manual and thus it couldn't resolve the IP--now all works well

 

[natcom]

with in the cable moden ?