Sign in
Microsoft.com
 
Windows Server TechCenter
 
 
 
Windows Server TechCenter > Windows Server Forums > Clustering > NLB with Terminal Services - Doesn't Work??
Ask a questionAsk a question
Search Forums:
 

QuestionNLB with Terminal Services - Doesn't Work??

  • Thursday, April 10, 2008 8:51 PMSTDFJoshua Users MedalsUsers MedalsUsers MedalsUsers MedalsUsers Medals
     
    Sign In to Vote
    0
    Sign In to Vote

    Dear MSFT Team & Fellow Posters:

     

    I'm having a problem setting up a NLB Cluster with Terminal Servers in Windows 2008 Standard Edition.  Here are the steps I took to setup the enviroment:

     

    1. I have two identical hardware servers with Windows 2008 Standard (Full) installed on them with the latest updates.

    2. I then setup the NICs in each server (1 each) with a static IP address (10.51.1.83 and 10.51.1.85).

    3. I disabled all of the firewall services.

    4. I joined the servers to the domain and moved them to a NO POLICY OU and renamed them.

    5. I installed Terminal Services via the Add Roles feature.

    6. Reboot.

    7. Compeleted installation of Terminal Services (success).

    8. I'm able to login to both terminal servers indidually with domain users (not as admin) just fine.

    9. I installed NLB via the Add Features tool.

    10. Reboot for good measure.

    11. I then login to a 3rd Windows 2008 box and use NLB Manager to create the cluster on the other two servers.  The settings I put in are as follows:

     

    Mode:  Multicast (because I only have one nic in each server)

    Virtual IP:  10.51.1.84 (255.255.255.0 same subnet as the two servers)

    Port Rules:  Only one rule that states the virtual IP is 10.51.1.84 (instead of checking the ALL box) for port 3389-3389 and I again select Multicast with Single Affinity here.

     

    12. Both servers converge just fine.  I'm still able to logon to the console remotely via the direct IP or hostname of each server.

    13. I open a command prompt on my machine (10.51.1.184) and I can ping 10.51.1.84 just fine.

    14. I create a DNS entry of STDFTS (A) pointing to 10.51.1.84.

    15. I can ping STDFTS just fine from my workstation.

    16. I open RDP on my workstation and put in STDFTS and click LOGIN and I get an error stating that it could not connect to the server.  (No firewall on my machine and other RDP's work fine).

    17. I put in the IP address of 10.51.1.84 in RDP and try to connect with the same error.

    18. I ensured that the remote desktop on both servers is set to ALLOW ANYONE (instead of just secure network clients).

    19. I ensured that Domain Users were setup in the Remote Desktop group.

    20. I logged into each server, right-clicked the connection properties, and found that TS is listening on ALL AVAILABLE IP ADDRESSES.

    21. On the servers I typed:  netstat -an and I can see 0.0.0.0 listening on port 3389 just fine.  I can also see 10.51.1.83 listening on 3389 showing me logged in remotely.

     

    Honestly, I cannot figure out why this is working.  They are freshly installed, all updated, and what seems like setup properly.  Does anyone have any ideas of what might be happening or am I missing something really obvious!?  Any help is MUCH appreciated. 

     

     

All Replies