Posted 21 January 2013 - 17:21
I am currently in the middle of a data centre migration, moving from physical boxes to virtual but as part of it I am also separating systems that don't seem to play nice together. So the setup is like this;
3 sites, Site A, B and C. all connected via and MPLS circuit to our new ISP who then routes traffic to the new vDC (virtual data centre). The internet breakout for the users is also at the ISP but all web/public facing servers in the vDC breakout from the vDC. This way if the link between ISP and vDC went down we would still be functional albeit at a reduced capacity.
This means the servers in the vDC that are not public facing have a gateway ending in 200.254 so all traffic is routed back to the MPLS network. The servers that are public facing have a gateway ending in 200.1 which is the gateway at the vDC but persistent routes forwarding all MPLS traffic to the 200.254 GW.
I am based in Site A and this works perfectly for me. I can access all the servers and all the web facing ones are still routing traffic to the public domain when requested. Site C is the same. Site B however where the team who need to test the new servers is based can ping some but not all of the servers. To confuse the matter a little more, some users are able to ping more servers than others and one isn't able to ping any.
So this is what I have done.
Removed the static route and added it again.
Cleared the TCP/IP stack and reset the winsock catalogue re-adding the static routes again.
Reset the server between each step of the above and have done the same on the servers and client PC.
Tried using Wireless and cabled connections as the client is on a laptop.
The servers that the client is unable to connect to is Server 2003 R2 and 2008 R2, the client is on Win 7 x64.
I suspect that there is something obvious that I am missing but looking at this problem for a couple of days and I cant see it.