Kurt - In device manager is an option to "show hidden devices". Enable that, both on the "new" server there and the "old" server there and see if you have a "ghost" NIC. I bet you will. And that ghost NIC probably has the problem IP address.
Remove the ghost NIC and you'll remove the problem. Regards, Michael B. Smith Consultant and Exchange MVP http://TheEssentialExchange.com ________________________________________ From: Ralph Smith [[email protected]] Sent: Saturday, October 30, 2010 12:22 PM To: NT System Admin Issues Subject: RE: A real puzzler... Do you have an AV application on the server? The reason I ask is I had some servers that exibited the exact symptoms you are describing after installing VIPRE Premium on them. Removing VIPRE solved the problem. -----Original Message----- From: Kurt Buff [mailto:[email protected]] Sent: Saturday, October 30, 2010 1:49 AM 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 Confidentiality Notice: ---------------------------------- This communication, including any attachments, may contain confidential information and is intended only for the individual or entity to whom it is addressed. Any review, dissemination, or copying of this communication by anyone other than the intended recipient is strictly prohibited. If you are not the intended recipient, please contact the sender by reply email, delete and destroy all copies of the original message. ~ 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
