I just virtualized a Windows 2003 Server SP2 x32. The server contained our help desk server (Spiceworks) and our anti virus management server (ESET RAC). The host computer actually contained the virtualized server originally; I created the vhd and then I wiped this system clean and installed Windows 2008 R2 x64 Datacenter and added the virtualized 2003 onto the Hyper-V 2008 R2 Server.
I got the server running fine except for... certain ip ranges. Local clients can get updates from the AV server from my 192.168.180.xxx & 192.168.181.xxx BUT NOT from any 192.168.182.xxx, 192.168.183.xxx, 192.168.184.xxx etc... I can not ping the server from any clients except for the 180. & 181. ranges.
Now I created 2 other virtualized servers (win2008 & a win7 pro) and they exist on the same virtual host as the 2003 server. And at first I could not ping those until I went to the "\Network and Sharing Center\Advanced sharing settings" and Turned On File and Print Sharing. Then I could ping and access those virtualized guests.
Win2003 server isn't quite the same.
EDIT!! Changed Image and added more info...
The ping test is from a host in the 192.168.187.x
192.168.181.200 is the server (Spiceworks/AV)
hostname is cea-spiceworks (originally ois-imaging)
- First ping cea-spiceworks = Request Timed out.
- Second ping: 192.168.181.200 = Request Timed out.
- Third ping test to cea-hyperv = Successful cea-hyperv is Windows 2008 R2 Datacenter x64 which holds the cea-spiceworks vhd virtual server.
- Fourth ping is to a nas fileserver (192.168.181.30), which is on the same ip range as cea-spiceworks. And that ping was successful.
I can ping all other guests running on cea-hyperv, just not the 2003 Spiceworks Server. Which makes me believe it is the cea-spiceworks 2003 server and not dns.
btw, I did rename that 2003 Server (Spiceworks/AV) hostname. And I tried a CNAME. But I do not think that is the problem. EDIT: OR because this server existed on this hardware/computer before becoming virtualized?