Windows Server 2008 r2 supports a virtual IP in terminal server sessions.
The virtual IP can either be attached to individual sessions or applications.
Together with the MS support we saw, that under identical configurations this feature does not work in the ESX, but works on real hardware and Hyper-v as well. Now MS denies any further support in this case.
We already configured a different type of network adapter - without success.
Please se the attachement for the details about the eventlog (just one message, which indicates the problem).
Did sombody of you make the same experience?
Some ideas how to get arround that?
Thanks a lot,
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.
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.
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.
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.
I resolved this by disabling the "VMware VMCI Bus Device" in Device Manager (under System devices) and uninstalling the VMCI driver by modifying the VMware Tools installation, disabling IPv6 by unchecking the box in the Local Area Connection properties and setting the DisabledComponents DWORD value to 0xFFFFFFFF under HKLM\CurrentControlSet\services\TCPIP6\Parameters in the registry, and adding the server's IPv4 info to its hosts file, i.e.:
I also made sure any IPv6 references in the hosts file, such as ::1, were commented out.
I am using the VMXNET3 driver and did not make any config changes to the vSwitches and my RDS servers are successfully assigning virtual IPs from DHCP to each session.
tried everything, but it doesnt work for my environment.
I have an ESX4.0 Host:
Ip-Virt. activated on E1000 connected to the same VSwitch as the DHCP Server, VMware Tools are deinstalled, IPv6 disabled
I was helped by the following:
1. add VMXNET3 adapter and remove E1000
2. uninstalling the VMCI driver by modifying the VMware Tools installation
3. disabling IPv6 by unchecking the box in the Local Area Connection properties
4. setting the DisabledComponents DWORD value to 0xFFFFFFFF under HKLM\CurrentControlSet\services\TCPIP6\Parameters in the registry