NLB with terminal servers using TS Session Broker - Can't log on to the IP on the terminal server

Discussion in 'Clustering' started by Geir Tore Johansen, Apr 7, 2009.

  1. Hi,

    I have configured two terminal servers with Windows 2008 server std. using
    TS Session Broker and NLB. It seems to be working fine, but we are not able
    to connect directly to the terminal server we want to uppgrade with new
    programs. It seems that the TS Session Broker don't care if you use the VIP
    or the DIP when connecting to the terminal servers. When stopping the TS
    Session Broker service we are able to connect directly to the server vi want
    to upgrade.

    Any suggestions on how to avoid this problem? We connect to the servers
    using RDP. We could og course work directly on the servers, but some og the
    software companies have to do remote installations.

    Any help would be most appreciated.

    Regards,

    Geir Tore Johansen
     
    Geir Tore Johansen, Apr 7, 2009
    #1
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.