I have XP mode VPC running on several Win 7 x64 hosts that worked perfectly with integration components working fine until the other day a prompt appeared saying that an update for integration components was available. I updated the integration components and now I have a problem. Two of the applications that we run for work are no longer able to connect to our oracle database and therefore, cannot run. Upon investigating this issue, I found that from my XP VPC, I can no longer ping my local database server by name (only by IP). Prior to the update I was able to ping the server by its hostname just fine. After the update, the server is only pingable via direct IP address ping. I tested this by restoring the VM from a vhd backup I have (which works fine) and then purposely installing the update and I confirmed that installing the VPC integration components update causes this network communication problem. From the Win 7 host, I can ping the server just fine so that's not an issue even after applying the update. However, from the XP Mode, it looks like it can no longer resolve the server name. I have tried disabling the firewall on the XP Mode and on the Win 7 host, but that seems to make no difference. I still have internet connectivity on the XP mode, I just cannot reach the server by its hostname. It looks like this update has blocked some TCP/IP port or enhanced security in some way.
So I have two alternatives: either prevent users from installing this update on VPC, or find out what the update does to the network connectivity so I can undo it.
Does anyone know how to prevent users from installing this update? It pops up every time the XP mode starts after the host is rebooted.
If not, does anyone know what this update does to the network configuration? It looks like it blocks the name-resolving abilities of XP mode. By the way, I am using NAT in Virtual PC since I cannot use the bridge mode due to our enterprise network policy.