Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations IamaSherpa on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

network connection dropped 2

Status
Not open for further replies.

timbooher

Programmer
Oct 20, 2004
8
US
Hello. I have lost linux internet connectivity. I am not able to ping anything from Fedora 3 when I type ifconfig, I don't get any errors (eth0 is found with no errors) but when I type dhclient I get: sit0: unknown hardware address type 776 as part of the message.

physically everything is connected and I have two other windows pc's working on the network and the router is assigning ip's just fine.

everything was working great for 3 years with this computer. the computer runs samba as a back-end server. I was not working with the computer at all when it stopped working.


please help/advise, any help greatly appreciated. in windows i would just release/renew the ip address, should i restart the linux box -- i would hate to do that?

Oh, and I need to remark that this problem is intermittent. A PC (windows 2000) on my network hung and when I rebooted, the linux box accessed the internet just fine for about 5 minutes.

Regards,

Tim
 
Dead/Dying NIC? Had a strange problem this morning after a power failure that was similar to yours, except mine was a fixed IP but couldn't connect to anything on the network. After a half-hour of poking around, I noticed during the POST that my NIC is now assigned IRQ9 instead of the regular IRQ11. Had to delete the hwconf file and ran kudzu again to redetect.


--== Anything can go wrong. It's just a matter of how far wrong it will go till people think its right. ==--
 
I would agree with Zeland. It could be an error with your NIC. I've never seen a device swap IRQs like that, but I don't doubt that wacky things happen like that (which Microsoft usually fails to compensate adequately for). Another thing you might also try is to manually configure the NIC and then see if you can ping anything. Then you know where you problem is. I usually use pump for DHCP client-side, but I've found that sometimes there's a slight hiccup in the communications, and the NIC got stuck halfway through the acquire, and then doesn't have the rest of the information.
 
Without restarting, you can always restart network resources with --
RedHat machines:
/etc/init.d/network restart

Debian based machines:
/etc/init.d/networking restart

If the card is still alive, and nothing under /etc/sysconfig or the hosts files, resolv file have changed -- this should work. If not, I'd swap NICs and try it again.

[plug=shameless]
[/plug]
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top