StarDestroyer.Net BBS

Nitram and I have a problem. The cable modem works, but there's something wrong with the router, we think. When the cable is run thru the router and split to both computers, both get "no connectivity" errors. When the cable's run straight (to Nitrams computer) there's no problems.

Nitram attempted to troubleshoot the router as per instruction booklet, but the router won't talk to the computer. Does anyone have suggestions?

Reset the modem to get it to talk to the computer. Also run connectivity check on your cables.

Eh, if the same problem's showing up on two systems, and the cable from the modem to the router works as seen by the direct-line test, that pretty much rules out cable trouble. What model of router do you have? Some of them let you log into the router and ping IP addresses from it, to test if it can see the net connection, or if it's stonewalling there.

Start with the basics.


1. On each computer, enable 'Obtain IP address automatically' and 'Obtain DNS server address automatically' under 'Internet Protocol (TCP/IP)' on the network controller's properties tab.

2. Perform a hard reset of the router. The instruction book should tell how.

3. Connect it to both computers.

4. Power it up.


If it lets you connect to the configuration page (usually 192.168.1.1 or 192.168.0.1), then configure the WAN to work with your cable modem.

If it doesn't connect to the computers and let you log in to the configuration page after this, you've got a bad router.
If it's under warranty or a recent purchase, return it to the store or call the manufacturer.
If not, buy a new router.

And at this point, let me pimp the Zyxel router that I have for sale over at the ars technica classified forums.

White Haven wrote:Eh, if the same problem's showing up on two systems, and the cable from the modem to the router works as seen by the direct-line test, that pretty much rules out cable trouble. What model of router do you have? Some of them let you log into the router and ping IP addresses from it, to test if it can see the net connection, or if it's stonewalling there.

Ask Nitram on that one, WHiteHaven. Hes' the one at home right now who can check. If he's online, I'm sure you can find him easier than I can

Compaq 'iPAQ' Connection Point CP-2E.

Can't establish a connection to even the router's configuration doodahs.

All attempts to connect through it have the computers hang on obtaining a network address. This is resolved instantly when connecting directly through the modem.

SirNitram wrote:Compaq 'iPAQ' Connection Point CP-2E.

Can't establish a connection to even the router's configuration doodahs.

All attempts to connect through it have the computers hang on obtaining a network address. This is resolved instantly when connecting directly through the modem.

And you are hooked through ethernet and not wireless? Try the hard reset, but if that doesn't work than you might have a fried router on your hands. A router should always respond to a configuration request as long as you are hard wired and it is working correctly.

If this is a wireless unit, it might not be so bad. Usually when a wireless router is reset, it resets the wireless profiles too, which means you have to go back in and reconfigure them through a wired connection.

Might you have accidently switched the crossover and through cables between the router and computers? Crossover has to go between the router and modem, and through has to go between router and computer.

It's wired...and yeah, sounds like you have a crispy router. Only thing left to try is to switch the jacks you're using around, see if you're lucky and it's just a few ports of the built-in switch giving you grief.

I told him it was fried.

So, any ideas on where to get a good router?

Are you looking for wireless, or will one without wireless connectivity be fine?

Belkin and D-Link make fine routes of both kinds, and while not the best in my opinion, Lynksys routers are also servicable.

We had fully wired router. We're not wanting to give connection to the whole apartment building.

LadyTevar wrote:We had fully wired router. We're not wanting to give connection to the whole apartment building.

Amazon.com is a fine place to get a good router for cheap, although you can try your local electronics store in a pinch. I recommend Linksys or Netgear, they are the two best brands in the router business in my experience and iI have owned several of each.

Dlink DI-604 is cheap and a hasslefree wired router.

The Kernel wrote:

LadyTevar wrote:We had fully wired router. We're not wanting to give connection to the whole apartment building.

Amazon.com is a fine place to get a good router for cheap, although you can try your local electronics store in a pinch. I recommend Linksys or Netgear, they are the two best brands in the router business in my experience and iI have owned several of each.

I personally prefer Newegg.com for all of my computer hardware purchases. (well... except refurbished 21" monitors, heh)

Newegg or Zipzoomfly are the places that I buy most of my hardware from.
As far as routers go, I prefer Zyxel, Linksys, and Netgear but my best luck has been with Zyxel.
The only reason I'm selling that Zyxel wired router is that I replaced it with a Zyxel wireless router.

That said, you might just want to get this wireless Netgear router because it'd be only $30 after rebate.
It's got a true SPI firewall and you can turn the wireless radio off to keep your network secure from your neighbors.

One problem with ordering online: We do not use credit cards.

A debit card works just as well. You've a check card, don't you?

nickolay1 wrote:A debit card works just as well. You've a check card, don't you?

First it'd have to have money on it

Well. I don't know if this is good news or not.. but it looks like the problem isn't the router, it's Katcomp's NIC card.

We found this out because Katcomp refused to find her ISP addy even when plugged straight into the cable modem. How this managed to keep both computers offline when running thru the router is one of those little annoying things about computers.

Nitcomp is working fine, of course.

So Nitcomp can connect through the router?

nickolay1 wrote:So Nitcomp can connect through the router?

I think so..... I don't know if he's tried that or not.

Have you reset the cablemodem after plugging it straight into Katcomp? Cablemodems are finicky when it comes to their hosts, unlike DSL. After switching hosts (computer to router, router to computer, computer to computer, etc.) you must reset the modem itself for it to recognize the new host.

BloodAngel wrote:Have you reset the cablemodem after plugging it straight into Katcomp? Cablemodems are finicky when it comes to their hosts, unlike DSL. After switching hosts (computer to router, router to computer, computer to computer, etc.) you must reset the modem itself for it to recognize the new host.

No kidding.
One time I was installing a router at a friend's house and I couldn't get the router to recognize the modem even after hitting the 'reset' switch on the front of the modem.

After calling the ISP, it turns out that the 'reset' switch on the front wasn't a true reset switch at all, merely a 'soft reset' switch.
I unplugged it from the wall, plugged it back in, and then we were on the net.

We found this out because Katcomp refused to find her ISP addy even when plugged straight into the cable modem. How this managed to keep both computers offline when running thru the router is one of those little annoying things about computers

Are you sure your machine is spy- and adware free?

I've worked on several machines over the last month that couldn't access the network due to adware screwing around with the networking properties.
It'd just keep saying 'Invalid IP address' <0.0.0.0>.

In true Shep fashion, I immediately exercised the 'nuclear option' of a complete OS reinstall after an hour of repeated Spybot runs did no good.

Sounds like you had a fragged Winsock LSP...which is something I really should have thought of. Remind me again, Kat, what version of Windows you have on there? It's been a while.