WYSE C10LE and TS Farm

  • This topic is empty.
Viewing 3 posts - 1 through 3 (of 3 total)
  • Author
    Posts
  • #7180
    Avatarrobbie99
    Member
    • Total Post: 2
    • Newbie

    Hello

    I have a Terminal server farm consisting of 2 session servers and one server that acts as connection broker and session redirector. The farm name (farm.domain.com) is set up in DNS.

    From the Wyse terminal I can connect to the sesion redirectorbroker server and this establishes a session on one of the 2 terminal servrers fine (connecting by IP address) However if I try to connect via the farm name (farm.domain.com) I get an error – server not found in Kerberos Database – Error code 7. (The farm name resolves to the session brokerredirector IP address in DNS)

    What what I can make out the WYSE terminal is trying to authenticate against the farm name, and obviosly this isnt known to kerberos. Is ther a way setting this so the Wyse terminal knows this is a farm name, or do I need to use the IP address?

    How do people set this up with MS NLB Farms or do they use the IP address?

    #21992
    Avatarorange10mm
    Member
    • Total Post: 2
    • Newbie

    You actually don’t want the farm name to resolve to the session broker IP. The proper way to set this up is to configure round robin DNS for farm.domain.com that resolves to the IPs of all servers in the farm. Example:

    Server 1 IP = 10.0.0.1
    Server 2 IP = 10.0.0.2

    farm.domain.com resolves to (via two A records):
    10.0.0.1, 10.0.0.2 (both IPs)

    The TS servers will actually forward the requests back to the session broker and the session will land on the proper server. We have 4 TS farms configured with about 200-300 users and this has been working smoothly for us for almost 3 years now. If you read the Microsoft white papers, this is actually the intended configuration of the farm name in DNS.

    Hopefully this helps…I actually just registered on this forum to ask a question myself but couldn’t pass up answering this one….paying it forward 🙂

    #22018
    Avatarrobbie99
    Member
    • Total Post: 2
    • Newbie

    Because some of the clients don’t use the same DNS we were unable to use round robin dns. Terefore we have set up a dedicated session redirector (I agree round robin dns would have been the prefered solution). So all sessions point to a dedicated IP address (the session redirector), this server denies any new connections, so passes the request off tpo the session broker (the same server) which then redirects the request to one of the other servers in the farm – documented in the 2nd half of this article (http://technet.microsoft.com/en-us/library/cc772418(v=ws.10).aspx)

    This all work fine from windows clients – we have a dns name set up which resolves to the redirector. However if the Wyse terminals point to the DNS name I get the authentication errors. If I use the IP address it works fine. So it looks like it is trying to authenticate against the dns name..

Viewing 3 posts - 1 through 3 (of 3 total)
  • You must be logged in to reply to this topic.