<HTML><HEAD>
<META content="text/html; charset=utf-8" http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16700"></HEAD>
<BODY style="MARGIN: 4px 4px 1px; FONT: 10pt Segoe UI">
<DIV>Rudi,</DIV>
<DIV>Sounds like a module conflict/misconfiguration, but anyway glad its working back. have you upgrade this system with the latest kernel build. I am guessing both onboard NICs are the same brand, take a look at messages and see if the card give me problems in the future. make sure you look for packet drops or errors that may hinder a bad NIC in the near future. Put your admin hat on a design a good plan to tackle this issue so you don't sweet it in the near future. Two cents.<BR><BR>>>> Rudi Ahlers <Rudi@SoftDux.com> 1/10/2011 6:18 AM >>><BR>On Mon, Jan 10, 2011 at 12:08 PM, Rudi Ahlers <Rudi@softdux.com> wrote:<BR>> On Mon, Jan 10, 2011 at 11:49 AM, compdoc <compdoc@hotrodpc.com> wrote:<BR>>> I love realtek - the resources they use tend not to conflict with other<BR>>> cards or hardware, they don't use much cpu time, the drivers are mature, and<BR>>> they don't cost much. What could be better? There does seem to be at least<BR>>> one onboard realtek chipset that can have driver issues, but I use the 8169<BR>>> without problems.<BR>>><BR>>> But hardware does fail. And any brand of nic can fail in odd ways. I'm<BR>>> guessing you've swapped it out?<BR>><BR>> Yes, the NIC might have failed, but how do I tell? lspci still shows<BR>> it as active.<BR>><BR>><BR>>><BR>>> Bios settings can change if the on-board battery is dead and the system<BR>>> loses power. (It can set to defaults) But bios settings rarely affect nics -<BR>>> you're more likely to see boot problems from a change in drive boot<BR>>> sequence.<BR>><BR>> I already checked, BIOS settings didn't change :)<BR>><BR>>><BR>>> I don't suppose you have a vpn on your lan? I noticed you use the<BR>>> 192.168.1.x address range, which is one of the most common ranges in the<BR>>> world. If someone connects to your vpn from home or workplace, and if they<BR>>> use the same range, and if theres a bridge, addresses are going to<BR>>> conflict.<BR>><BR>> This is purely cause the ADSL router in the office is on the<BR>> 192.168.1.0 subnet, so it's less hassle when it needs to be swapped<BR>> out to get it back up again. No VPN.<BR>><BR>><BR>>><BR>>> If you delete your ifcfg-eth0 or ifcfg-eth1 files, centos will recreate them<BR>>> if it sees the nics at boot. But it tends to enable eth0 and disable eth1 or<BR>>> higher. You should have backups of your originals for that reason...<BR>><BR>> I've already tried that, but eth0 doesn't automatically get detected.<BR>><BR>><BR>>><BR>>> I bet you wish you had a tcp/ip based kvm switch system about now...<BR>>><BR>><BR>> Yes, I supposed I could take one from a client server, or open a<BR>> sealed one, but it's not really necessary. For now I put in another<BR>> D-Link and got the server up that way, but would prefer to use the<BR>> onboard one since I had to take everything out of the 1U chassis,<BR>> which doesn't support more than 1 additional NIC.<BR>><BR>>><BR>>> _______________________________________________<BR>>><BR>><BR>><BR><BR>This is really weird, after I installed the 2nd D-Link card and booted<BR>up the server everyone could work again. But I noticed and eth2 being<BR>loaded as well, which could only make sense if the onboard NIC was in<BR>fact still working. And it was. So I took out the D-Link, deleted<BR>eth2, rebooted and it worked again as normal.<BR><BR>Why would this happen, or have happened in the first place? Why would<BR>a NIC just loose it's drivers like that?<BR><BR><BR>-- <BR>Kind Regards<BR>Rudi Ahlers<BR>SoftDux<BR><BR>Website: <A href="http://www.SoftDux.com">http://www.SoftDux.com</A><BR>Technical Blog: <A href="http://Blog.SoftDux.com">http://Blog.SoftDux.com</A><BR>Office: 087 805 9573<BR>Cell: 082 554 7532<BR>_______________________________________________<BR>CentOS mailing list<BR>CentOS@centos.org<BR><A href="http://lists.centos.org/mailman/listinfo/centos">http://lists.centos.org/mailman/listinfo/centos</A><BR></DIV></BODY></HTML>