Re: NLB & separate RDP connections for network adapters

From: Jim Olsen (jabuol_at_hotmail.com)
Date: 05/10/04


Date: Mon, 10 May 2004 12:55:47 -0500

I found this: http://support.microsoft.com/default.aspx?scid=kb;[LN];280805

Can anyone either confirm or deny that 2003 has the same problem?
--Jim

Jim Olsen wrote:

> We have two terminal servers configured as members of a NLB cluster.
> They each have two NICs, one for management and one bound to NLB. We
> would like to force our TS users to connect to our terminal servers by
> using NLB, but allow our admins to connect directly to the management
> interface. The users should not be allowed to login via the management
> NIC.
>
> My attempt at accomplishing this was to use permissions on multiple TS
> connections. I modified the original RDP-Tcp connection so that it is
> "bound" only to the NLB NIC (it defaults to all adapters, 0.0.0.0) and
> created a second RDP-Tcp-Mgmt connection that is bound only to the
> management NIC. The problem is that the RDP-Tcp connection listens only
> on the dedicated IP address (I suppose because it's listed first for the
> interface) and not on the cluster IP address. Consequently, users
> cannot connect to the TS servers via the cluster IP address.
>
> Also, given that our NLB cluster is in unicast mode, I expected a
> connection to the dedicated IP address to still be load balanced (since
> an arp reply for the dedicated IP address would contain the MAC address
> of the cluster). Based on a few small experiments, it doesn't seem to
> behave that way. If that is true, that behavior would also undermine
> our goal of forcing users to use NLB. (The experiments were done using
> Virtual PC 2004 running two TS servers with network adapters on the
> "real" network. The host OS was the TS client. We don't have layer 3
> switches on the network, and I doubt Virtual PC gets involved at layer
> 3, but it's possible.)
>
> Can Windows Server 2003 support our desired goal, and if so, how do I
> configure it?
>
> Thanks for your help.
> --Jim



Relevant Pages

  • Re: Load Balanced TS Servers and Unicast Flooding
    ... Remove each on of your tse servers from the cluster, ... Start adding them back to the NLB Cluster. ... > NICs. ...
    (microsoft.public.windows.terminal_services)
  • RE: NLB heartbeat clarification please.
    ... Today I have an Oracle/Domino back-end cluster based on Win2k3 EE. ... question is how many public IP-addresses will I need (two servers - two NICs) ... > adapter is referred to as the Dedicated NIC. ...
    (microsoft.public.windows.server.clustering)
  • Re: Load Balanced TS Servers and Unicast Flooding
    ... Remove each on of your tse servers from the cluster, ... > Use the other network card for cluster communication. ... >> NICs. ...
    (microsoft.public.windows.terminal_services)
  • Re: NLB & separate RDP connection for network adapters
    ... > They each have two NICs, one for management and one bound to NLB. ... I modified the original RDP-Tcp connection so that it is ... > cannot connect to the TS servers via the cluster IP address. ...
    (microsoft.public.windows.server.clustering)
  • Re: NLB Cluster - Ping fails or long time to reply from outside local subnet - SOLVED
    ... Windows Server 2008 Readiness Team ... cluster on a separate DLink card in multicast mode. ... I thought that the litmus test was that the router functions fine ... member of the NLB cluster, setup NLB on it, plug the NICs ...
    (microsoft.public.windows.server.clustering)

Loading