If (for whatever reason) I do an 'ifdown eth0' and an 'ifup eth0' on the desktop computer, it asks for an IP and gets one, but then cannot communicate with any computer in the internal network, and cannot access the web. I cannot ping and get a reply on any internet address at all. Same goes for internal IPs. I cannot find anything in the message log that seems related.
If I do the same thing on the laptop, it gets an IP assigned and immediately has access to both the internal network, and the internet.
The only way I've found to get the desktop communicating with the network after I do an 'ifdown eth0' is to do a reboot.
So... any ideas of what to look for? Why would doing an ifdown followed by an ifup on this one machine block all future network access until a restart?
You can try and do after you tell the card to come back up you can do a dhcpcd eth0 and see then if you can get out of the internet. If not, then it seems like that you are not getting the default route during DHCP. If the above does not help, post the results of the ifconfig and route -n command and someone here will try and help you.
Whew, busy week.. this is the first time I've had a chance to get back to this. I'm still having this odd networking problem on my desktop computer... Here's some extra data.. # ifdown eth0 # ifup eth0 Starting DHCP Client Daemon on eth0... . . . . . . . . . . IP/Netmask: 192.168.1.2 / 255.255.255.0 # route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0 eth0 # dhcpcd eth0 **** dhcpcd: already running **** dhcpcd: if not then delete /var/run//dhcpcd-eth0.pid file # ping 192.168.1.1 PING 192.168.1.1 (192.168.1.1) 56(84) bytes of data. --- 192.168.1.1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 1999ms Now if I compare the settings with my laptop running the same basic install of SUSE9.0 I see the exact same as on the desktop... except the desktop won't connect after I do an ifdown eth0. On the laptop, I have no problems bringing the network down and back up again... the desktop will only reconnect after a reboot. So... Im still looking for ideas here.... C.