Am Thu, 5 Mar 2015 13:33:23 -0500 schrieb Todd Goodman <t...@bonedaddy.net>:
> * Marc Joliet <mar...@gmx.de> [150305 04:47]: > [..SNIP..] > > 1.) The NIC is brought up (some built-in Intel model). > > > > 2.) A DHCP client configures it. > > > > 3.) The network connection is lost at some point (the amount of time this > > takes > > varies, but it can be as little as 20 minutes). > > > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, but > > gets no response. Sometimes, after many hours (at least 6), it will > > get a > > DHCPACK, but that's it. One of our sysadmins says that not only does > > the DHCP server never see the packets, but the managed switch that the > > PC > > is directly attached to *also* never does (again, except for when the > > occasional DHCPACK comes). > > > > 4.) Restart the network device. A reboot is not required, but it is > > necessary > > to terminate the DHCP client. After that everything works again. > > > > 5.) GOTO 3. > [..SNIP..] > > Is this a WiFi NIC? Nope, it's wired. > Is it possible the device is powering down? I mentioned the possibility, but don't find it *that* credible, since three different PCs (with different NICs) have shown the problem. Plus, sometimes the one affected PC I work on can still reach the internet (i.e., a browser works), even though it has already ceased to be reachable. [...] -- Marc Joliet -- "People who think they know everything really annoy those of us who know we don't" - Bjarne Stroustrup
pgpzmZvBUN2SC.pgp
Description: Digitale Signatur von OpenPGP
