Read Me: Can't Connect With Cable Modem

Wired · #1 04-18-2004, 11:17 PM

Here's a quick and dirty guide on what to do if you can't get online with your cable modem (and yes, I do see the irony in this

)

1. Take out the power cord from the cable modem for at least 30 seconds. Note: This is often referred to as power cycling a cable modem. Hitting the power button or standby button is not sufficient.

2. Plug it back in, and wait for the lights to resume their normal pattern. Not sure what that is? Check out this place! http://www.neotechcc.org/cablemodem.htm Note: Not all of the links are up to date, and some of the newer modems aren't listed as of yet.

3. Try to get online. No go? You may have to reboot your computer as well depending on which operating system you are using. Also, if you have a router and/or hub, power cycle them as well.

4. Still not online? Check to see what your IP is.

If you are running Win98 or WinME, type in WINIPCFG (this is not case sensitive) into the RUN command from the START menu. Change your adapter to your Network Interface Card (NIC).

In Win2K / WinXP, you can open up a command prompt, then type in the command IPCONFIG. In WinXP, you can alternatively go to your Control Panel -> Network Connection -> Local Area Connection -> Support

More to come later!

capybara · #2 04-19-2004, 11:20 PM

alt step 4. in internet explorer, goto tools,
internet options, connections.
dialup settings should say "never dial"
5. click on lan settings. should say " autodetect"
6. proxy server box should be NOT checked
(unless of course you have a proxy server in which case
you will probably have set up the proxy server yourself
but having a proxy server is RARE)
7. shut down previous open internet explorers.
8. open up a new internet explorer. still no go?
9. run ipconfig
10. if ipconfig starts with 169, run
ipconfig / release and then ipconfig /renew
if you get an ip NOT starting with 169, ping yahoo or msn. if you can ping them, your internet explorer is bad.
if your still getting an ip starting with 169, go to next step
TO BE CONTINUED :)

capybara · #3 05-03-2004, 11:16 PM

step 11. if your still getting an ip starting with 169, reboot the cable modem, then, reboot the router if any, then reboot your computer.
12. still ip 169? remove the router and repeat step 11.
13. still ip 169? its a hardware problem. does the green light on your
ethernet card come on? if not try a new cable, or a new ethernet card.
14. if the green light on your enet card is on, calll up your isp's tech support,
and ask them what the correct lights that should be lit on your cable modem.
your isps tech support will be very cooperative and if necess send a tech to your house to figure out signal levels and so on.
15. i usually keep an old computer around, so if your good computer wont go online, you can try the old computer, and so suss out: is it the computer,
or is it other issues.

Wired · #4 05-03-2004, 11:41 PM

Note: Rebooting a device means pulling the power cable and letting it sit for at least 30 seconds.

Also, if you're getting a 169 when you're connected directly to the modem, try disconnecting the coax line, then reboot the modem. In rare cases, signal flux can confuse the modem.

capybara · #5 05-04-2004, 10:39 PM

also, if your using a router, get an ip starting with 10, it
means your getting a good connection between computer & the router,
but u still have to suss out if there is a good connection
between router and cable modem, and if cable modem is working or not.

Wired · #6 05-05-2004, 01:23 AM

???????????????????????????????????????????????

capybara · #7 05-23-2004, 10:15 PM

and 192.168.*.* is also a good lan address

baileyca · #8 08-09-2005, 04:39 AM

I find ipconfig /release /renew /etc. to have a questionable success rate. (My favourite is when it releases then hangs renewing.)

The most reliable way I've found is Start -> Control Panel -> Network and Dial Up. Right click on whatever you've named your LAN connection and choose "Disable." Once it's disabled (with a red X through the icon), double-click it to re-enable it.

C

Wired · #9 08-09-2005, 05:55 PM

One I used to use at work (supposedly it'd reset the winsock):
netsh int ip reset reset.txt

roadrun777 · #10 10-09-2005, 12:39 AM

capybara,

I think ultimately you are going to confuse people by telling them that certain IP numbers are better and faster than others. If you are as smart as I hope you are, then you know that your IP number has squat to do with how 'good' your connection is.

Different routers/cable modems all default to different IP address ranges.
Some actually use 169.* addresses as its internal private IP numbers.
So sticking with ping and trace route to verify connection and dns is probably more to the issue.
You should also run IPCONFIG /ALL in a command prompt box to see what your gateway address is assigned to. If your gateway is 169.* and its not the same number as your IP then you are fine! Your internet explorer has nothing to do with that.

baileyca · #11 10-16-2005, 07:38 PM

Quote:

Originally Posted by roadrun777

...going to confuse people by telling them that certain IP numbers are better and faster than others. If you are as smart as I hope you are, then you know that your IP number has squat to do with how 'good' your connection is.

I don't think he meant that 10.* was better/faster, I think he was implying that a 10.*/192.* are good NAT'd addresses. This definitely requires further explanation, but I think it's just how each person interprets it.

Quote:

Originally Posted by roadrun777

Different routers/cable modems all default to different IP address ranges.
Some actually use 169.* addresses as its internal private IP numbers.

If your router does this, it's a very bad thing. The 169.* range has been reserved for APIPA addressing (Automatic Private IP Addressing). These ranges should only be assigned when there's no DHCP service and no static IP.

For shame on whichever routers those are! Using IPs that are not in the proper private IP ranges is bad... (Trust me, we had a system at work that was designed to use TCP/IP but would "never be connected to the network". They randomly chose to use [and hardcode] 17.* for the IPs; guess what happened 15 years later when they decided the system needed to go on the network?) :)

C

Xtreeme · #12 02-10-2008, 11:40 AM

The problem with IP ranges is all modems have diff defaults. Linksys like the 192 ranges. Older speedtouch starts with 10 newer has 10 and 192 ranges. Its very modem specific. Regardless, the IP ranges can be changed too along with the range. Dont forget multi user modems which are also routers and make it even harder to explain.

Then there is the hard reset which varys. Cycling power usually wont help if the modem is bugged (like the log file being too large) you usually have to reset it. That means youll loose your log in info and will have to setup again. Linksys and Netgear are finicky when it comes to a reset and have diff methods like holding reset unplugging waiting 10 second while holding reset plugging in then waiting for the lights to all flash then releasing the reset. In the end you have to really explain specific modems or you may just confuse the person in trouble all the more.

There is no down and simple easy network guide since there are so many variables. Though what you have here sure is a good start! Good job guys.

The shortest guide is.....

If your network is down, call your ISP. They know the specific modem you have also thats what your paying them for. Get the help, you payed for it.

charlie4u · #13 08-15-2011, 01:38 PM

thanks for suggestions..
HP Lserjet Printer Drivers