sudden loss of wired connection to router

[HelenBN]

(This doesn't seem to be a router problem. Original post in Linksys forum with no help.)

set up:
WRT54GS - G router
SURFBoard SB3100
XP home wired CPU
serveral wireless connections with WEP security, index key assignment, MAC list authorization
all ZoneAlarm free
IP configuration working correctly

Everything works fine for over a year.
Electrical power loss home wide for a minute or less.
Boot up Modem
Boot up Router
Wireless connections re-established
CPU doesn't think cable is connected
Router doesn't light up port showing connection

changed cables - not working
changed ports - not working
remove router and connect to modem - working
restored cpu to day prior to event - not working
turn off ZoneAlarm - not working
(turn ZoneAlarm back on)
replace WRT54GS with old BEFW11S4 v. 2 (B router)- working
reset WRT54GS to defaults through reset button - not working
replaced WRT54GS with brand new one same model - not working
connect/wired different CPU through brand new WRT54GS - working
connect/wired different CPU through original WRT54GS - working
(rebox brand new model to return to store)
(reprogrammed original WRT54GS through second cpu)
updated driver for ethernet card - not working
reconnect original cpu to modem - working

could ethernet card functionality be spotty and need replacing? would this ONLY show up on G router? could the NIC port/slot be faulty...?

I am baffled!

 

[BadFrog]

I'm with Lawnboy on this one. What is your NIC set to as far as speed is concerned? 10? 100? or auto negotiate? Auto neg is recommended and should be default. Try all three settings and I bet you get some contivity with at least one. If not I wouldn't hesitate to replace the NIC altogether. Based on the fact that it worked when connected directly to the modem but not the router really makes me think its a speed mis-match.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[HelenBN]

Auto neg. I tried the other settings... but I can't remember if I rebooted btw each change. Probably not. Does this matter..? None worked. Should I try again with rebooting?

 

[BadFrog]

Yes you should reboot. I think I would just replace it at this point, or better yet swap it with the one in the CPU that did work. Also check the duplex setting and confirm it matches what the router is set to, full or half.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[LawnBoy]

Well I'm confused. I was assuming that when you've reffered to the B and G routers you meant that they were both wireless base stations, one doing 802.11b and one doing 802.11g, which then routed to your cable/dsl/t1/whatever broadband connection. I see now this is not the case. Also, according to the specs you posted, neither one is a router. These are simple network switches.

Regardless, if you're not getting a link light a lot of these details are irrelevant. We need to simplify, looks like we're all getting lost in the details.

Unhook everything from the WRT54GS, then only hook up the pc you want attached to it. Does the link light come on?
If not, try another port on the WRT54GS. If another port lights up, the original port you tried on the WRT54GS is bad. If no port on the WRT54GS lights up, then you have either a bad cable or the NIC in the pc is flakey.

Just because some other piece of equipment works with that pc's NIC does not mean that NIC is in perfect condition. Been there, done that...

 

[LawnBoy]

Good point about the duplex/speed settings, BadFrog. However, I can get a link light on my linksys kit even when the speed/duplex settings are way off. That link light is simply saying that it sees the terminator, therefore has a valid copper path. After I get a link, then I configure it to actually pass data.

 

[BadFrog]

Ya I'm thinkin the NIC is probably bad.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[LawnBoy]

err, it is possible that all 4 ports on the WRT54GS are bad (unlikely, but possible). If you can't get a light on any port using the NIC, hook something else up to the WRT54GS and see if you can get a link light on any port. If you can't get any port to light up with any piece of equipment, the WRT is fried.

 

[HelenBN]

Lawnboy, I might not be using the term "router" correctly, but I thought I was.

The cable goes into the cable modem
the modem goes into the WAN on the Linksys Broadband Router
all PCs but mine are wireless
mine is /would be wired to a port

My PC will not generate a light on the Linksys. So, the Linsys doesn't think it's there. And my PC does not think it is connected to anything. True on all ports.
If I wire the PC across the room that is normally wireless (running the CAT5 over my sleeping dog) it will generate a light. It works fine.

Sorry, I don't even know what I don't know.

 

[BadFrog]

I smell a bad NIC....

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[HelenBN]

But if I wire directly to the modem, I am sitting pretty.

 

[BadFrog]

But if I wire directly to the modem, I am sitting pretty.

True but that doesn't mean the NIC isn't bad. It just means it works with the modem and not with the router. You could easily isolate this by swapping NICS with cpu that did work.

"Once you can accept the universe as matter expanding into nothing that is something, wearing stripes with plaid comes easy"
Albert Einstein

 

[cdogg]

Helen,
It's starting to smell like this is turning into a game of Devil's advocate.

You've got to accept that either the router, cable, NIC, or Windows setting is the problem. You have reasons that all seem to say that the problem is "none of the above". But we know the answer must lie with one of them.

In my experience, a failing or bad NIC card (especially after a power surge/failure) can play games like this. Since it is the cheapest component, it is often replaced first when other logical troubleshooting is exhausted. Because this normally fixes weird issues, it has become the "norm" to expect the unexpected with bad NICs.

~cdogg
"Insanity: doing the same thing over and over again and expecting different results." - Albert Einstein
[tab][navy]For general rules and guidelines to get better answers, click here:[/navy] faq219-2884

 

[rvnguy]

Just to bring a bit of humor to your situation.

If I wire the PC across the room that is normally wireless (running the CAT5 over my sleeping dog) it will generate a light. It works fine.

Have you tried running the CAT5 over sleeping dog from your PC??

Seriously, get you checkbook ready, try swaping NIC's with other PC. If makes your PC work, try the other with your NIC.

1. It also works, but in the other PC not yours.

2. It does not work in either, get a new NIC.

rvnguy
"I know everything..I just can't remember it all

 

[HelenBN]

This is just so exciting! I feel like I'm sitting at King Arthur's round table.

With a heavy snow falling today in Virginia, I will take the time to swap the NICs. Stay tuned....

 

[firewolfrl]

HelenBN....LOL

I love the snow...but, where I live we just got done with 100 mph wind storm on the coast. so now its dealing with insurance companies....I prefer the wind storm to that.
it sounds like you have time to play with the lan. lot of the people who posted had great fixes.
though I do like the idea of the CAT5 over the dog..LOL

make sure you have time to play in the snow.

 

[HelenBN]

Installed a new(er) NIC and ......

TA-DA! It's fixed.

What a weird bunch of issues that lead to this. Thanks EVERYONE for taking the time to help me think this through and for giving me GREAT advice.

Now I'll go play in the snow!

 

[LawnBoy]

In my experience, a failing or bad NIC card (especially after a power surge/failure) can play games like this.

Yeah, I've beaten my brains out over similar issues before as well. It can be very tough to troubleshoot.

Glad you got it fixed, Helen, and don't feel bad that it took so long. This was a tricky one.

 

[PRPhx]

It's even more fun when you can ping your NIC with the loopback test and it works, but you still can't get to the internet, etc.

 

[firewolfrl]

Aaaaah! yes!
I hate gateway issues....lol
fixed the router that had that problem....


Fourth of July fireworks and a test to see how high the router can fly...oh! it was so scientific. 15 feet and KABOOM.....HEE HEE...solved that router problem.