Hi everyone!

I have a bizzare networking problem that i can't figure out and was hoping someone could give me some advice. I installed Suse 9.3 on my workstation (I can't use 10.0 because for some reason its SLOW as hell after install when booting gdm). The installation went fine and was very snappy. In fact all around the system is very snappy, but I digress.

My machine is extremely fast. Dual Core Opteron 270, 2GB's of Registered memory, 7200 RPM SATA drives, Geforce6600Gt, the works. The motherboard is an MSI K8N Master2-FAR utilizing the NForce4 Pro chipset.

The problem is during the last phase of the install (and this has occured on more than just my machine), Suse YAST opens YOU (Yast Online Update) to update the system. Its got about halfway through downloading the packages, and I lost network connectivity. It just stopped downloading packages. I aborted, and booted into Gnome. When i ran a basic ifconfig, I had no IP. DHCP refused to work on both the onboard NIC's despite having worked perfectly during the initial setup and package download (before it ceased). I figured it was something wrong with the lease perhaps, so i manually configured both the NIC's with static IPs, etc. I could NOT route to even the gateway (no destination to host returned from the system).

At this point, I have no idea what to do. I have tried both NIC's, a new switch, different gateway router. The motherboard isn't bad, the NIC's work fine in Windows XP, Ubuntu, and even Solaris 10 x86_64.

Any ideas? I'd be happy to provide logs, just tell me what you need and i'll provide it. Novell support is not going to be much of a help here I expect.

Why not go into the YAST GUI, Delete the NIC, reboot, and let SuSE re-detect and auto-configure?

Of course the simplest method of probably resolving this problem, is the one I didn't try. I'll test it and let you know.

Thanks

If that doesn't help, could you post the output of lspci and lsmod. Then try an ifconfig eth0 down followed by an ifconfig eth0 up and post the output. If no errors are reported could you then try the dhclient etho command. You say you've done some of this before but I'd like to see the screen output at each stage.