 |
 |
On further thought, how about this-- Release the "bad" IP from the computer where you're having trouble. Maybe even unregister the computer as well. Take a spare computer that is not registered for DHCP, boot it up, hook it to the network, set up DHCP, and register it. Would the DHCP server then give the "bad" IP to it, so you would have that IP safely tied up on a computer you don't care about? This wouldn't work if the server continues to "reserve" that IP for the original computer for some period of time rather than giving it out again right away. -----Original Message----- From: MSU Network Administrators Group [mailto:[log in to unmask]] On Behalf Of Chris Wolf Sent: Thursday, February 26, 2009 5:03 PM To: [log in to unmask] Subject: Re: [MSUNAG] How to force a new IP address from DHCP? Install a new NIC in the machine and register it? Use wireless? (possibly/probably requires installation as well) -----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