[heise]

The registry trick is for Win2k3

[imthebrian]

Your netmask needs to be 255.255.255.255 and the gateway should be 37.187.69.254

Thanks for the clarification...made the changes and all was verified working properly. :-)

Quick question though...is it necessary for me to first set the mask @ 255.255.0.0, then go into the registry and change it to 255's? Seems like I could just put it into the GUI of the server while configuring everything else and bypass the regedit step at the end.

-Brian

[Neil]

Setting mask to all 255's resulted in an error msg and server completely dropping network connection, so that's not our fix ;-)

Your netmask needs to be 255.255.255.255 and the gateway should be 37.187.69.254

[imthebrian]

should that not be 255.255.255.255 ???

Setting mask to all 255's resulted in an error msg and server completely dropping network connection, so that's not our fix ;-)

[heise]

MASK: 255.255.255.0

should that not be 255.255.255.255 ???

[imthebrian]

Hello,

I've recently purchased a dedicated infrastructure server (37.187.69.168) which has been installed with ESXi 5.5. I've ordered an additional block of 8 IP's (46.105.249.40/29) to use for management VM's:

*.40 = vCenter Appliance
*.42 = Win2008r2 Server

I've setup the Virtual MAC addresses with OVH and have them manually assigned to the proper VM's along with their corresponding IP's. Yesterday I started receiving the following email messages from OVH.cz:

Hello,

We have detected that your server ns6456440.ip-37-187-69.eu unnecessarily sending
a large number of requests over the network via its IP failover 46.105.249.42
This is due to a misconfiguration.

We asked you in an prior email to kindly reconfigure the IP
failover, noting that the problem persists, we now reiterate
that request.

If the problem is not solved in 24 hours
we will be forced to block your IP.

In this case, it will be possible to unblock it in your manager
once the reconfiguration is done.

THIS IS THE LAST WARNING BEFORE THE BLOCKING OF YOUR IP !!!

You can use the following guide to help you with the reconfiguration:

http://prirucky.ovh.cz/IpAlias/
http://prirucky.ovh.cz/BridgeClient/


You will find below a sample of queries sent by your server:

------- EXTRACT OF REQUESTS -------

Thu Aug 14 16:46:39 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 17:11:30 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 17:36:33 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 18:01:30 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 18:26:46 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 18:51:46 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 19:16:46 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 19:41:31 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 20:06:30 2014 : arp who-has 46.105.249.40 tell 46.105.249.42
Thu Aug 14 20:31:30 2014 : arp who-has 46.105.249.40 tell 46.105.249.42

------- END OF EXTRACT -------



Yours faithfully,

OVH.CZ, s.r.o.

So it looks like there's some ARP traffic between vCenter and one of the Win2008r2 Servers. Here's the configuration for the server that keeps getting nastygrams:

IP: 46.105.249.42
MASK: 255.255.255.0
GW: 46.105.249.254
NS: 213.186.33.99
MAC is manually set in vSphere to match output of Virtual Mac tool that corresponds to correct IP.

Server is working fine as far as I can tell, I just keep getting the above warning emails. Is this configuration correct? I have another Win2008r2 server that's configured the same (with different valid IP and MAC pairs), and I'm not getting any configuration error emails for it.

Thanks,
Brian