[37683] in Resnet-Forum
DHCP Windows 7 issue
daemon@ATHENA.MIT.EDU (Mike King)
Tue Nov 27 09:12:00 2012
MIME-Version: 1.0
Content-Type: multipart/alternative; boundary=f46d04083f3b08455a04cf7a7cd1
Message-ID: <CANtPpk6bqTpovoVpLhHhFYN4pAdgWgh+mWjXUQQ1P_612MQ4Uw@mail.gmail.com>
Date: Tue, 27 Nov 2012 09:01:20 -0500
Reply-To: Resnet Forum <RESNET-L@LISTSERV.ND.EDU>
From: Mike King <me@mpking.com>
To: RESNET-L@LISTSERV.ND.EDU
--f46d04083f3b08455a04cf7a7cd1
Content-Type: text/plain; charset=ISO-8859-1
I have a bit of a Weird one.
We had a DHCP issue yesterday (DHCP server crashed hard, took a little
while to restore)
This morning we noticed in one of our lab of 24 computers, that 12 of them
still had APIPA addresses.
The machines are Windows 7. Here's where it get's weird.
If I do an IPCONFIG /ALL on them, they show they have a gateway (correct
gateway) but they have an APIPA address. (169.254.x.x).
If I do an IPCONFIG /release, it does not release the address, it still
shows it having the APIPA address. (Same if I do a IPCONFIG /renew).
It's instantaneous as well, it doesn't think about it for awhile
Rebooting the machine seems to correct the issue. Since this is a
non-critical lab, I've been asked to investigate. Concern here if there
was some similar problem, to fix the underlying cause, or at least
understand it before wiping it out. (It's not hard to imagine
the scenario playing out in all labs at once)
Anyone have thoughts?
___________________________________________________
You are subscribed to the ResNet-L mailing list.
To subscribe, unsubscribe or search the archives,
go to http://LISTSERV.ND.EDU/archives/resnet-l.html
___________________________________________________
--f46d04083f3b08455a04cf7a7cd1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
I have a bit of a Weird one.<div><br></div><div>We had a DHCP issue yesterd=
ay (DHCP server crashed hard, took a little while to restore)</div><div><br=
></div><div>This morning we noticed in one of our lab of 24 computers, that=
12 of them still had APIPA addresses.</div>
<div><br></div><div>The machines are Windows 7. =A0Here's where it get&=
#39;s weird.</div><div><br></div><div>If I do an IPCONFIG /ALL on them, the=
y show they have a gateway (correct gateway) but they have an APIPA address=
. (169.254.x.x).</div>
<div><br></div><div>If I do an IPCONFIG /release, it does not release the a=
ddress, it still shows it having the APIPA address. (Same if I do a IPCONFI=
G /renew). =A0It's=A0instantaneous=A0as well, it=A0doesn't=A0think =
about it for awhile</div>
<div><br></div><div>Rebooting the machine seems to correct the issue. =A0Si=
nce this is a non-critical lab, I've been asked to investigate. =A0Conc=
ern here if there was some similar problem, to fix the underlying cause, or=
at least understand it before wiping it out. =A0(It's not hard to imag=
ine the=A0scenario=A0playing out in all labs at once)</div>
<div><br></div><div>Anyone have thoughts?</div>
___________________________________________________
You are subscribed to the ResNet-L mailing list.
<p>
To subscribe, unsubscribe or search the archives,
go to <a href=3D"http://LISTSERV.ND.EDU/archives/resnet-l.html" target=3D"_blank">http://LISTSERV.ND.EDU/archives/resnet-l.html</a>
___________________________________________________
--f46d04083f3b08455a04cf7a7cd1--
