I have a server with two statically addressed NICs that kept going to
the DHCP registration page and wouldn't stop until I disabled one of the
cards.
Today, as I went to finish working on it, I see that problem has gone
away.
--
Kim Geiger
WKAR Radio & Television, WKAR.org
East Lansing, Michigan
517-884-4766
>>> On 7/10/2015 at 8:43 AM, "Bosman, Don" <[log in to unmask]>
wrote:
> Possibly related, we’re seeing some student worker machines, under
group
> policy, that time out trying to connect to AD, before they can pick
up a
> group policy desktop. These are on static IPs. Prior to this morning,
I
> presumed it was our network. Now I have to wonder if it’s latency
of some
> sort on the campus network.
> This might be interesting - if there are more responses.
>
> Don Bosman
> Information Technologist
> MSU Libraries
> 366 W. Circle Drive - Rm.W441
> East Lansing, MI 48824-1048
> 517-884-0873
>
>
>
>
> From: STeve Andre' [mailto:[log in to unmask]]
> Sent: Thursday, July 09, 2015 11:10 PM
> To: [log in to unmask]
> Subject: Re: [MSUNAG] Dell not getting dhcp info at start up
>
> Interesting and depressing.
>
> --STeve
>
> On 07/09/15 16:47, Gary Schrock wrote:
> I just actually had two machines I just finished looking at that were
also
> having dhcp issues just now. Both a Dell and a printer had failed to
get
> dhcp addresses and had defaulted to their built in auto-ip addresses.
(Both
> of these were machines that would have gotten 35.15 addresses because
they
> weren't currently registered.) I just kinda wrote it off as a fluke,
but
> maybe there's something more widespread going on? Yesterday I had a
machine
> that I registered, got it's 35.10 ip address, then shortly after I
got a call
> saying that it wasn't working again, and sure enough, it had a 35.15
address
> once more, but when I went into the registration stuff, it was
recognized as
> having been registered (that machine I had to unregister and
reregister to
> get working again).
>
> Gary
>
> On Thu, Jul 9, 2015 at 4:41 PM, Stephen Andre
> <[log in to unmask]<mailto:[log in to unmask]>> wrote:
> So, here's a new one for me.
>
> A user reports that she isn't on the net when she boots up
> in the morning. After five minutes or so, she is.
>
> I'm on this system now. I had a 169 address, meaning dhcp
> failed. Doing a manual ipconfig release/renew fixes it.
>
> Any clues as to why this would fail this way?
>
> Thanks all..
>
>
> --STeve Andre'
|