My wired NIC is being retarded, please help

[Hybrid_theory]

The other night I was browsing the web or something, and my internet connection killed out. Pretty sure my brothers did as well. So i reset the router/modem(1 unit) and my bro had internet but I did not. I look at it the next morning and neither of my onboard wired NICs will get an IP address. On the current task bar it shows as no internet access.

I can connect with my PCI wireless card just fine and it receives an IP as it should. Not sure what else to try here. My internet speed is fine on wireless. But i know it will hurt if i want to transfer anything over our network.

 

[twilyth]

I would try another cable - one you know for sure is working. If that isn't it, and other machines are getting through on the same router, then the next logical suspect is the NIC. But I think you'll get better odds on the cable. The guage of the stranded wire inside is super fine and it doesn't take much to damage 1 or 2 wires - especially if the cable is just hanging off the back and gets jostled regularly.

 

[Hybrid_theory]

I had forgot to mention that I had tried another cable. And both ends looks to be meeting and there's no kinks in the cable. Also there is a green light at each port. I tried 2 different ports on the router.

 

[allen337]

either the wired connections on your router is bad or both your nics, reset that router again make sure you push the reset button not just unplug it

 

[twilyth]

I think he said his bro was getting through on the same router though. Of course if you're the only one on the router, then, yeah, you definitely need to check that.

If not, then it has to be the NIC. Of course this assumes that there weren't any software changes that were made at the same time that this started happening. In that case, all bets are off.

I don't think I've ever had a NIC go bad on me, but I'm sure it happens. Maybe it was next to a hot video card, a little too much dust build up, whatever. But I think you also said that neither card was working. That's too much of a coincidence. Are there any other cards in the PCI bus and do they seem to be working?

IDK. I'm stumped.

 

[Hybrid_theory]

Both NICs are onboard. All PCI devices are functioning properly. So i tried installing nvidia ethernet drivers. It didnt work. Windows is basically telling me its having trouble obtaining a proper IP address. It gives its 169.x.x.x where it should be 192.168.2.x.



Stupid networking. Take a course for 2 years and cant figure it out.

 

[AsRock]

Is the IP\DNS setup to detect automatically ?.
And is DHCP and DNS services turned on ?

 

[hat]

Network cards are not exensive.
http://www.newegg.com/Product/ProductList.aspx?Submit=ENE&N=2050400027 4024&name=$0 - $10

 

[Hybrid_theory]

Is the IP\DNS setup to detect automatically ?.
And is DHCP and DNS services turned on ?

Yeah, the tcp v4 settings are all obtain automatically. And the router is handing out addresses just fine to my wireless card and bros computer.

Those are cheap NICs but in Canada im looking at $30+ which isnt bad still. But im hopeful theres another solution.

 

[Mussels]

try with another OS - a bootable linux CD, format and install on a spare 20GB clunker in the spare parts bin - something that allows you to rule out software changes causing this, and diagnose if its hardware.


169.x.x.x addresses are given by windows when it cant find a DHCP server - it assigns them so that windows machines can communicate with each other, without a DHCP server running. As far as windows is concerned - that cable is plugged into nothing.

 

[Hybrid_theory]

try with another OS - a bootable linux CD, format and install on a spare 20GB clunker in the spare parts bin - something that allows you to rule out software changes causing this, and diagnose if its hardware.


169.x.x.x addresses are given by windows when it cant find a DHCP server - it assigns them so that windows machines can communicate with each other, without a DHCP server running. As far as windows is concerned - that cable is plugged into nothing.

Thanks for the idea mussels. It appears to be the hardware for sure. Booted to a fedora 10 live cd i had, did dhcp on the one ethernet port. After trying for 40 seconds or something, failed to receive an address. Just so weird that they crapped out like this.

 

[twilyth]

I would have need 'jumper cables to the nads' type persuasion to belief that they just happened to go out together in some kind of suicide pact.

I'd like to hear ideas for possible causes.

A power surge comes to mind, but wouldn't that hit the power supply before it would damage anything on the bus? And why aren't other PCI cards affected.

A surge from the router is another idea, but I have to believe that anything strong enough to damage a NIC would also fry the router.

IDK.

 

[Hybrid_theory]

I would have need 'jumper cables to the nads' type persuasion to belief that they just happened to go out together in some kind of suicide pact.

I'd like to hear ideas for possible causes.

A power surge comes to mind, but wouldn't that hit the power supply before it would damage anything on the bus? And why aren't other PCI cards affected.

A surge from the router is another idea, but I have to believe that anything strong enough to damage a NIC would also fry the router.

IDK.

They are onboard NICs so its possible some controller piece got screwed up when the router was reset. And it only affected me and not my brother. Youd think it would fry the router too...

 

[Ripper3]

That's quite strange that it's not picking up an IP by default, but it could be the router that's stopping you from auto-obtaining by blocking the MAC addresses. It sounds stupid to me, before anyone else says it, but frankly, can you rule anything out yet?
Just assign your own IP within the subnet. Windows will auto-generate the Subnet mask, just type in 192.168.2.13 or something that's definitely not in use on your network (I usually just go for something above about 7, that always works for me) for your computer's IP address, and assign the DNS server to 192.168.2.1 or whatever your router's IP is.

If that doesn't work, then just buy a cheap NIC from the States as it's definitely an unfixable problem, without an RMA. Surely Customs won't charge you for something less than $20 or something, unless Canadian Customs is really tight.

Oh, you could also try trawling through your router's configuration, see if it's blocking access to devices at all, if not, add one of your NIC's MAC addresses to the list of devices to use DHCP. I had to do that once for my old router to properly assign an IP on DHCP, but only to one PC.

 

[Hybrid_theory]

Alright I decided to give Bell support a try. LOL. Im in the middle of chat right now. Should see what this guy has asked me.

Balaji (SCI-285541)
could you please explain me as how do you connect to the Internet?
You
the modem itself is connected as instructed, to the wall jack. Im connected to the modem through a PCI wireless NIC
Balaji (SCI-285541)
Do you connect to the Internet by clicking on the icon?
You
its automatic...
Balaji (SCI-285541)
Are you able to connect to the Internet where you get that 169 ip address?
You
no
You
the connection at that point says no internet access
You
cant ping the router at 192.168.2.1 it says unreachable at the 169.x.x.x address

 

[Mussels]

idea: in the past i've seen a BIOS setting on nforce boards, that allowed you to change your MAC address - i had seen a BIOS flash clear that once, and had to be manually re-entered (the mac addies were on a sticker on top the ports)

have a looksee, see if the setting is there.

 

[Hybrid_theory]

Well received a new modem from bell. And it worked. Not sure why it did, but it did.