Announcement

Collapse
No announcement yet.

Unicast Terminal Server network configuration

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • Unicast Terminal Server network configuration

    Hi All,

    Can anyone let me know what is needed in order to build active/active Terminal Server with Windows NLB manager ?

    I am confused and need your assistance in what IP address to use and what Networking Configuration to use.

    Thanks.

  • #2
    Re: Unicast Terminal Server network configuration

    Albert,

    Microsoft NLB on unicast mode should be placed into a separate VLAN. If not, you will flood the network with traffic.

    Although this document is quite "old" it still applies. ISA for example uses Microsoft NLB as well when putting multiple ISA servers into a cluster
    http://www.isaserver.org/tutorials/basicnlbpart1.html
    http://www.isaserver.org/articles/basicnlbpart2.html
    http://www.isaserver.org/tutorials/nlbpart3.html

    Anyhow, to respond to your question, I would set them in a separate VLAN. Then give both hosts there own IP addres in that VLAN for example 10.10.10.1 and 10.10.10.2. The NLB address will be from the same range. So for example the NLB address would be 10.10.10.10.
    Clients should then connect to the 10.10.10.10 address.
    Last edited by Dumber; 21st May 2012, 10:24.
    Marcel
    Technical Consultant
    Netherlands
    http://www.phetios.com
    http://blog.nessus.nl

    MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
    "No matter how secure, there is always the human factor."

    "Enjoy life today, tomorrow may never come."
    "If you're going through hell, keep going. ~Winston Churchill"

    Comment


    • #3
      Re: Unicast Terminal Server network configuration

      Originally posted by Dumber View Post
      Albert,

      ........

      Anyhow, to respond to your question, I would set them in a separate VLAN. Then give both hosts there own IP addres in that VLAN for example 10.10.10.1 and 10.10.10.2. The NLB address will be from the same range. So for example the NLB address would be 10.10.10.10.
      Clients should then connect to the 10.10.10.10 address.
      Thanks for the reply Dumber, soin this case I shall use just one vNIC per server not two ?

      because I was under the impression that I must use 2x vNIC with one for heartbeat.

      Comment


      • #4
        Re: Unicast Terminal Server network configuration

        You don't have an heartbeat with NLB. So you need to have just one nic per system.

        However, I notice that you are using a virtual environment due to the vNIC naming convention? Note that some vendors might not support NLB on unicast in a virtual environment and therefor you might need to use Multicast instead.
        Marcel
        Technical Consultant
        Netherlands
        http://www.phetios.com
        http://blog.nessus.nl

        MCITP(EA, SA), MCSA/E 2003:Security, CCNA, SNAF, DCUCI, CCSA/E/E+ (R60), VCP4/5, NCDA, NCIE - SAN, NCIE - BR, EMCPE
        "No matter how secure, there is always the human factor."

        "Enjoy life today, tomorrow may never come."
        "If you're going through hell, keep going. ~Winston Churchill"

        Comment

        Working...
        X