The information in this article applies to:
SYMPTOMSWhen you are using Network Load Balancing (NLB) to load-balance a cluster of Layer 2 Tunneling Protocol (L2TP) servers, clients experience broken L2TP sessions when a server is added to the cluster. CAUSE
Microsoft does not support using NLB to load-balance L2TP traffic
because some client sessions are torn down as User Datagram Protocol (UDP) datagrams are rebalanced to the new server when you add a server to the cluster.
STATUSMicrosoft has confirmed this to be a problem in the Microsoft products listed at the beginning of this article. MORE INFORMATIONNLB Behavior with PPTPThis problem does not occur when NLB load-balances Point-to-Point Tunneling (PPTP) traffic because a PPTP session maps perfectly to a TCP connection using TCP port 1723. NLB is able to track TCP connections. NLB watches for TCP "FIN" packets to determine when a connection terminates.When a cluster host is brought back online or a new cluster host is added to a PPTP cluster, NLB waits for TCP connections to end on the existing hosts before transferring some of the load to the new server. NLB Behavior with L2TPWith UDP L2TP traffic, when a server joins the cluster, some of the L2TP sessions on the existing cluster hosts are broken and moved to the new server.NLB Behavior with Both PPTP and L2TPNLB can service virtual private networking (VPN) clients with both PPTP and L2TP when a cluster host goes down. Sessions to the down server are lost but new sessions are directed to the surviving cluster hosts.Additional query words: wlbs
Keywords : kbenv kbnetwork |
Last Reviewed: January 5, 2000 © 2000 Microsoft Corporation. All rights reserved. Terms of Use. |