Việc xác minh thu hồi các thiết lập của các máy chủ liên bang, cấu hình trên nút Chính sách Trust của AD FS snap-in, được sử dụng bởi các máy chủ liên bang và bởi bất kỳ đại lý AD Web FS bị ràng buộc để các máy chủ liên bang để xác định làm thế nào thu hồi | 282 Introducing Windows Server 2008 NLB cluster stop all other hosts and then the one being tested . If you can isolate the host try to reproduce the problem without NLB bound. 2. Next start Network Load Balancing Manager from a client host that has access to all the hosts in the cluster. If Network Load Balancing Manager gives you any errors try to fix them. The errors shown by Network Load Balancing Manager can be fixed most of the time by reapplying the last known configuration on the host one connects. This can be done by right-clicking on the cluster name in Network Load Balancing Manager selecting cluster properties and clicking OK. 3. Make sure next that all the port rules you want are correct by re-verifying your port rules. To do this right-click the cluster select cluster properties and take a look at the Port Rules tab. Many times rules are incorrectly defined so make sure you read the description about how various port rules behave and be sure you understand the difference between single affinity no affinity diabled rules rules with different weight default host rules and so on. 4. The next step in troubleshooting would be to check whether the information shown by Network Load Balancing Manager is consistent with the output of command-line utilities like the nlb params and nlb display commands. 5. The next step in triaging would be to make sure each host in the cluster is seeing all the incoming traffic. This can be done by sending ICMP ping commands to the cluster from a few clients. If ping works then also make sure you can connect to other services RPC WMI and so on on each host. This can be done by starting Network Monitor on each host. Network Monitor can be downloaded from http downloads FamilyID AA8BE06D-4A6A-4B69-B861-2043B665CB53 displaylang en. You should see client traffic received on each host. In your network capture you should also see NLB heartbeats an Ethernet broadcast packet with the bytes 0x886f after .
