![]() This hotfix might receive additional testing. Apply this hotfix only to systems that are experiencing the problem described in this article. However, this hotfix is intended to correct only the problem that is described in this article. Resolution Hotfix informationĪ supported hotfix is available from Microsoft. Therefore, the server cannot respond to the client's request. Because some routers are designed or configured not to reply to packets with this mix of unicast and multicast, the server cannot discover the address of the default gateway. #Mediaportal client cannot connect to server mac#In multicast mode, this ARP request contains a combination of the unicast Virtual IP of the cluster and the multicast MAC address of the interface. When you try to respond to a client on a different subnet, the server must first send an ARP request for its default gateway. Outbound connection attempts from any NLB server nodes that use a node-specific IP are also successful. Attempts to connect to the node-specific IP are successful. In this scenario, clients may experience intermittent connectivity failures when they try to communicate with a server that is part of this NLB cluster. The NLB cluster nodes have not recently communicated with any device on the client's subnet. There is a router between the NLB cluster nodes and the client devices. NLB is configured to run in multicast mode. The Network Load Balancing (NLB) feature is enabled on a Windows Server 2008-based computer. Windows Server 2008 Datacenter Windows Server 2008 Enterprise Windows Server 2008 Standard Windows Server 2008 Datacenter without Hyper-V Windows Server 2008 Enterprise without Hyper-V Windows Server 2008 Standard without Hyper-V Windows Server 2008 for Itanium-Based Systems More. ![]()
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |