oh yes we do.
4 specialist did work on this problem several days and no working result. After endless tests we are sure it is a problem with ESX and Windows 2008 R2 Server.
Enable Promiscuous Mode within the portgroup or vswitch
Thank you for the reply. We tried this also and had no success.
Have you tried the setting with success?
sure it works fine. the same principle applies to CARP/VRRP.
If you have changes the security settings next thing to check is the load balancing method.
There is no loadbalancing configured at the moment. We have tried it again and can't see a dhcp request on our dhcp server coming from the windows 2008 R2 server and no virtual ip is assigned to the remote session.
Whould you be so kind and give us some more information?
- which adapter you use for the vm
- which security settings you talking about?
- we have no failover for the adapter configured, but if, which settings are important?
thank you for your help
There are two settings that need to be changed for WNLB to be used.
1) Within the Port Group or vswitch change "forged mac" to "accept"
2) Within the vswitch change "notify switches" to NO
Go here for more info:
Or you can just use "multicast mode"
Sorry for the delay, the problem is also present.
We have information from vmware that it is working with vmware V3.5U5 and can be reproduced at vmware 4.
It should be fixed at U3. The Vmware Bug Numbr is 547341.
So i'm not shure if you have an identical configuration running.
Is this problem solved? I have the same problem on ESXi4.0. If theres a solution it would be nice to know.
Try uninstalling VMware Tools, reboot guest and then make a custom VMware Tools installation where you choose not to install the VMCI driver.
Message was edited by: datahalland
deinstalled the vmci driver but doesn't change anything. even without vmware tools it doesnt change. i've done all the things mentioned above but virtual ip doesn't work. :-(((
Ive done a native fresh install of W2K8 Server R2 on a Proliant Server. DHCP Server is configured on the same machine. The Virtual IP Feature works if the normal Network Adapter is chosen.
When configuring DHCP and RDP to use a Network on the "Local Loopback Adapter" it doesn't work anymore. Seems to me that MS has general problems with virtual adapters.
Hi, we make a production probes and we found that when we unistall the vmware tools, work fine with two network adapters.
Even redirecting a physical Network Card with PassThrough dosen`t solve the Problem. But as soon as i uninstall VMware Tools everything is working fine.
Removing the VMXNET3 adapter and driver and installing a E1000 network adapter solves my problem. (a VMXNET2 Enhanced adapter did not work completely, no RDP connection possible)
The problem is with the VMXNET3 driver. I hope there will be a fix soon, because I now have to work with the slowest network adapter available on this virtual machine.