That's worth a shot. On Sat, Oct 30, 2010 at 00:36, Blackman, Woody <[email protected]> wrote: > If the error is on the VM Guest, it could be a ghosted NIC from the P2V > > To work around this behavior and display phantom devices when you use the > Show hidden devices command: > > Click Start, click Run, type cmd.exe, and then press ENTER. > Type set devmgr_show_nonpresent_devices=1, and then press ENTER. > Type Start DEVMGMT.MSC, and then press ENTER. > Click View, and then click Show Hidden Devices. > Expand the Network Adapters tree. > Right-click the dimmed network adapter, and then click Uninstall. > > -----Original Message----- > From: Kurt Buff [mailto:[email protected]] > Sent: Friday, October 29, 2010 10:49 PM > To: NT System Admin Issues > Subject: A real puzzler... > > All, > > I'm in the US, and have a problem in our AU office that I'm having difficulty > wrapping my brain around. I have a theory, but it is still a strange > situation, and any feedback anyone can provide would be appreciated. > > The AU office has a server, which I've just recently stood up, using an > address assigned by DHCP. This is not ideal, obviously, but the thing refuses > to take the static IP address that it's slated to get > (192.168.61.30.) It's a VM on a new ESXi server. > > When I try to assign it the static address, it keeps getting an error message > that another machine has the address. > > However, when I ping the IP address that the machine refuses to use, I get no > answer. > > When I use netmon on the VM in the AU office to capture ARP traffic, I get a > MAC address that's for the DC. However, the DC has never had > 192.168.61.30 - it's been 192.168.61.31 all its life in the AU office. > > I've even fired up regedit on the DC to search for the IP address, and all > I'm showing is the one it's supposed to have - 192.168.61.31 > > I'm more than a little baffled by this one. > > One thing I should note, just because: The DC in the AU office is a machine > that had been used in the US office about two years ago. We did a P2V on it, > and the VM from that still lives on in the US office. > They do share a MAC address (I don't know why, as I would have expected the > the MAC to change when it got the virtual NIC), but AFAICT this shouldn't > make a difference, since they are in different subnets entirely, with > different addresses. > > Anyone have thoughts on this? > > Kurt > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ > <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > > --- > To manage subscriptions click here: > http://lyris.sunbelt-software.com/read/my_forums/ > or send an email to [email protected] > with the body: unsubscribe ntsysadmin
~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
