| 1 |
Am Thu, 5 Mar 2015 21:19:46 +0000 |
| 2 |
schrieb Mick <michaelkintzios@×××××.com>: |
| 3 |
|
| 4 |
> On Thursday 05 Mar 2015 18:33:23 Todd Goodman wrote: |
| 5 |
> > * Marc Joliet <marcec@×××.de> [150305 04:47]: |
| 6 |
> > [..SNIP..] |
| 7 |
> > |
| 8 |
> > > 1.) The NIC is brought up (some built-in Intel model). |
| 9 |
> > > |
| 10 |
> > > 2.) A DHCP client configures it. |
| 11 |
> > > |
| 12 |
> > > 3.) The network connection is lost at some point (the amount of time this |
| 13 |
> > > takes |
| 14 |
> > > |
| 15 |
> > > varies, but it can be as little as 20 minutes). |
| 16 |
> > > |
| 17 |
> > > 4.) Eventually the lease runs out and the DHCP client tries to renew it, |
| 18 |
> > > but |
| 19 |
> > > |
| 20 |
> > > gets no response. Sometimes, after many hours (at least 6), it will |
| 21 |
> > > get a DHCPACK, but that's it. One of our sysadmins says that not |
| 22 |
> > > only does the DHCP server never see the packets, but the managed |
| 23 |
> > > switch that the PC is directly attached to *also* never does (again, |
| 24 |
> > > except for when the occasional DHCPACK comes). |
| 25 |
> > > |
| 26 |
> > > 4.) Restart the network device. A reboot is not required, but it is |
| 27 |
> > > necessary |
| 28 |
> > > |
| 29 |
> > > to terminate the DHCP client. After that everything works again. |
| 30 |
> > > |
| 31 |
> > > 5.) GOTO 3. |
| 32 |
> > |
| 33 |
> > [..SNIP..] |
| 34 |
> > |
| 35 |
> > Is this a WiFi NIC? |
| 36 |
> > |
| 37 |
> > Is it possible the device is powering down? |
| 38 |
> > |
| 39 |
> > I've had lots of problems with WiFi devices powering down (both driver |
| 40 |
> > issues as well as just trying to disable the default setting of powering |
| 41 |
> > down.) |
| 42 |
> > |
| 43 |
> > Todd |
| 44 |
> |
| 45 |
> If not a WiFi, have you also tried to mirror a port at the router where the |
| 46 |
> DHCP server is running and sniff packets there? Does the router see the |
| 47 |
> DHCPREQ coming through from the client PCs? |
| 48 |
|
| 49 |
They apparently don't even reach the managed switch, which is what the PC is |
| 50 |
directly connected to (but again: the third affected PC is on a different |
| 51 |
switch). I find this very confusing :-/ (and so does our local sysadmin, or |
| 52 |
so I'm told). |
| 53 |
|
| 54 |
(I have to mention that the best I can do is relay ideas here to my boss and the |
| 55 |
aforementioned sysadmin, as I don't have access to any of the network |
| 56 |
hardware and software, save for the affected PCs. I am mostly trying to |
| 57 |
collect ideas.) |
| 58 |
|
| 59 |
-- |
| 60 |
Marc Joliet |
| 61 |
-- |
| 62 |
"People who think they know everything really annoy those of us who know we |
| 63 |
don't" - Bjarne Stroustrup |
Archives