I also had similar problems. After I installed the service-pack 2 for Windows Server 2003 the windows XP related guests were no longer working well. They booted up but were dramatically slow and won't response to any action. Network access was also no longer possible.
Finally I uninstalled service-pack 2 because of this problems. After I uninstalled it, the problems were no longer there.
1 person found this helpful
Have you tried to uninstall Windows Server 2003 Service Pack 2 on the guest and host?
Uninstalling Windows 2003 Service Pack 2 from the host "solved" the issue. I can even use RDP to connect to the guest OS from the desktop of the host. I tried everything I could short of uninstalling SP2 until you indicated having similar issues. Unfortunately, this "solution" opens the door to the question of whether or not there is an incompatiblilty between Vmware Server and W2K3SP2.
Unfortunately, this "solution" opens the door to the question of whether or not there is an incompatibly between Vmware Server and W2K3SP2.
I don't believe this a VMware issue since the bridged networking works at the layer 2 and services like RDP..etc are higher in the networking stack.
It's possible that SP2 just has some security restrictions that need to be looked at has to why it is interfering with these services.
Anyway, I too would like to know exactly the root cause. I will have to setup a test environment to look at this closer.
it would be great to you give us a feedback if you know more about this issue. I won't hope this is a "strategic feature" from Microsoft to strengthen their own virtualize product, lol... Thanks in advance.
Have there been any further developments on this issue?
I have a Windows 2003 Enterpeise R2 Service Pack 2 VM on an ESX 3.0.1 server and cannot RDP to it from anywhere. This seems like a serious problem as I would like to deploy servers with the latest service packs.
Maybe this helps:
Go to the registry,
Hkey_Local_Machine - system -currentcontrolset - control - terminal services
find the key: fDenyTSConnections and set it to "0"
Do this voor all VM/servers you want to access with RDP
Thanks Bastiaan. I'll give it a try.
I also went ahead and placed a call to VMWare support and was told that Service Pack 2 is not supported under ESX 3.0.1, but is under 3.0.2. It was recommended that I upgrade. I will try your fix and the upgrade and report back on the results.
If you use Windows you have to disable TOE (TCP Offload Engine), go to the network card properties in Device Manager and in 'Advanced' tab set TCP/IP Offload to Off.if you use Lunux- disable TSO (TCP segmentation offload). In terminal as root execute command:
ethtool -K eth0 tx off
(If eth0 is your main interface)
Disabled TOE - Didn't work... Thanks, though.
Sorry for not reporting back sooner.
I tried Bastiaan's suggestion, but it did not help. I upgraded to 3.0.2 per VMware support's suggestion, and this resolved all my problems.
Not sure why there is not more info about this but Windows 2003 Service Pack 2 is only supported under ESX 3.0.2 or higher. Under earlier versions, you can have problems with Windows networking such as file shares and Remote Desktop.
Is-your network card a Intel Pro/1000?
I did experience a lot of problems with Intel network card and virtualization product. I had to disable all TOE over IP UDP and TCP to be able to ping from host to virtual. With TOE enable it just doesn't work. The problem is worst whit VirtualPC. The only way I was able to make it work, so far, is to use a card that is not an Inel. With VMWare. I got slow network response and bad name resolution. Ex: ping computer1 = no resolution. But I am able to ping the IP with slow response.
The NIC is an HP NC373i and not and Intel Pro 1000 Thank you for the "heads up" on the Pro 1000