Taking the advice from Chris one step further, you could try to set the
MAC property of the existing NIC to something else temporarily if for
some reason you can't change hardware around. It would be ill-advised
to just pick a random MAC as there's a small chance that could collide,
but say perhaps, the MAC of an old card you have lying around your
space? Depending on how the driver, etc behaves it may or may not relay
this information correctly to the DHCP server, but if the setting takes
and works as intended; it should provide a new lease I believe. Just
remember to probably undo this in the future, like say after you find
the rogue machine which still should be located. Also make note of the
current MAC for the sake of easily setting it back later.
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of David McFarlane
Sent: Thursday, February 26, 2009 5:12 PM
To: [log in to unmask]
Subject: Re: [MSUNAG] How to force a new IP address from DHCP?
Ken,
>Install a new NIC in the machine and register it?
>
>Use wireless? (possibly/probably requires installation as well)
Hmm, indeed, that would force a new DHCP assignment. Well done.
Thanks,
-- dkm
>-----Original Message-----
>From: MSU Network Administrators Group [mailto:[log in to unmask]] On
>Behalf Of David McFarlane
>Sent: Thursday, February 26, 2009 4:21 PM
>To: [log in to unmask]
>Subject: Re: [MSUNAG] How to force a new IP address from DHCP?
>
>Ken,
>
>Thanks, of course we did that right off. But my question stands -- in
the
>short term, what could we do to restore network service to the user
while
>waiting for ATS to track and shut down the rogue?
>
>-- dkm
__________ Information from ESET NOD32 Antivirus, version of virus
signature database 3893 (20090226) __________
The message was checked by ESET NOD32 Antivirus.
http://www.eset.com
No virus found in this incoming message.
Checked by AVG.
Version: 7.5.557 / Virus Database: 270.11.3/1973 - Release Date:
2/26/2009 7:03 AM
|
