H
HeyMcFly
Environment: Vmware ESXi 6.0 latest version, Server 2016 Standard all updates installed.
We are working on deploying Windows Server 2016 Remote Desktop Services but having an issue with NLB. We have setup Microsoft NLB to load balance user connections to the farm. When we make a change to the load weight in NLB the server will drop 3-4 pings. If you have a command prompt window open with a continuous ping running it will report a PING Transmit error right after the NLB cluster starts converging.
I have found if I disable the DHCP Client Service then I am able to adjust the NLB load weight and the server does not drop its connection. I have been unable to determine what part of the DHCP service is causing this issue. We are using static IPs on the server so do not require DHCP but I would prefer to keep the service running.
I was able to replicate the issue on a VMware workstation VM but I was unable to replicate the issue on a Virtual box VM. We have tried changing a number of settings related to the network card and driver all to no affect.
We are aware there are other options for load balancing Remote Desktop services (i.e using Connection Broker) but we are not interested in other methods at this time.
Anyone else seen this issue on Server 2016 and Vmware?
Continue reading...
We are working on deploying Windows Server 2016 Remote Desktop Services but having an issue with NLB. We have setup Microsoft NLB to load balance user connections to the farm. When we make a change to the load weight in NLB the server will drop 3-4 pings. If you have a command prompt window open with a continuous ping running it will report a PING Transmit error right after the NLB cluster starts converging.
I have found if I disable the DHCP Client Service then I am able to adjust the NLB load weight and the server does not drop its connection. I have been unable to determine what part of the DHCP service is causing this issue. We are using static IPs on the server so do not require DHCP but I would prefer to keep the service running.
I was able to replicate the issue on a VMware workstation VM but I was unable to replicate the issue on a Virtual box VM. We have tried changing a number of settings related to the network card and driver all to no affect.
We are aware there are other options for load balancing Remote Desktop services (i.e using Connection Broker) but we are not interested in other methods at this time.
Anyone else seen this issue on Server 2016 and Vmware?
Continue reading...