Problem setting up Brokered load balancing

  • Thread starter Thread starter Casey
  • Start date Start date
C

Casey

Guest
I currently have 2 terminal servers, and a seperate server acting as the
session broker. I followed microsoft's step-by-step guide on setting up the
session broker, however I'm having problems.

When I bring up the Web Access interface on a terminal server
(http://ts1/ts) I see my list of available apps. However, after I click on
an icon (ie: wordpad), I get an error stating "Unable to connect to terminal
server. The terminal server farm ts1 that you are trying to connect to is
redirecting you to the server ts2. Remote Desktop cannot verify that this
server belongs to the same server farm. This can occur if there is a server
on your network with the same name as the server farm"

2 things are odd about that error:
1) the farm isn't "ts1", the terminal server is. The farm is called
"ts_farm". I have verified that ts1 and ts2 are bother referencing the
session broker farm of ts_farm.

2) to my knowledge, I never named a farm "ts1". there should be no chance
of a farm and server sharing the same name.

Any ideas? Any help would be greately appreciated.
 
Re: Problem setting up Brokered load balancing

You seem to be connecting using "TS1" as the name and the server
authentication is failing when redirection is happening. You probably need
to specify the farm name as well when connecting.

Regards
Anubhav K

PS. This posting is provided "AS IS" with no warranties, and confers no
rights

"Casey" <Casey@discussions.microsoft.com> wrote in message
news:6594D162-0AD6-43D9-AC1B-6FCE6898B6EE@microsoft.com...
>I currently have 2 terminal servers, and a seperate server acting as the
> session broker. I followed microsoft's step-by-step guide on setting up
> the
> session broker, however I'm having problems.
>
> When I bring up the Web Access interface on a terminal server
> (http://ts1/ts) I see my list of available apps. However, after I click
> on
> an icon (ie: wordpad), I get an error stating "Unable to connect to
> terminal
> server. The terminal server farm ts1 that you are trying to connect to is
> redirecting you to the server ts2. Remote Desktop cannot verify that this
> server belongs to the same server farm. This can occur if there is a
> server
> on your network with the same name as the server farm"
>
> 2 things are odd about that error:
> 1) the farm isn't "ts1", the terminal server is. The farm is called
> "ts_farm". I have verified that ts1 and ts2 are bother referencing the
> session broker farm of ts_farm.
>
> 2) to my knowledge, I never named a farm "ts1". there should be no chance
> of a farm and server sharing the same name.
>
> Any ideas? Any help would be greately appreciated.
>
>
 
Re: Problem setting up Brokered load balancing

Possible. I set 2 DNS entries up for 'ts_farm'. One entry points to ts1's
IP, the other to ts2's IP. So, even though I type in "http://ts_farm/ts"
into my browser, it's still techinically going to ts1 or ts2 directly.
Should I be typing a different URL into my browser? I thought this was
exactly what the docs told me to do, I could be wrong.



"Anubhav Kushwaha [MSFT]" wrote:

> You seem to be connecting using "TS1" as the name and the server
> authentication is failing when redirection is happening. You probably need
> to specify the farm name as well when connecting.
>
> Regards
> Anubhav K
>
> PS. This posting is provided "AS IS" with no warranties, and confers no
> rights
>
> "Casey" <Casey@discussions.microsoft.com> wrote in message
> news:6594D162-0AD6-43D9-AC1B-6FCE6898B6EE@microsoft.com...
> >I currently have 2 terminal servers, and a seperate server acting as the
> > session broker. I followed microsoft's step-by-step guide on setting up
> > the
> > session broker, however I'm having problems.
> >
> > When I bring up the Web Access interface on a terminal server
> > (http://ts1/ts) I see my list of available apps. However, after I click
> > on
> > an icon (ie: wordpad), I get an error stating "Unable to connect to
> > terminal
> > server. The terminal server farm ts1 that you are trying to connect to is
> > redirecting you to the server ts2. Remote Desktop cannot verify that this
> > server belongs to the same server farm. This can occur if there is a
> > server
> > on your network with the same name as the server farm"
> >
> > 2 things are odd about that error:
> > 1) the farm isn't "ts1", the terminal server is. The farm is called
> > "ts_farm". I have verified that ts1 and ts2 are bother referencing the
> > session broker farm of ts_farm.
> >
> > 2) to my knowledge, I never named a farm "ts1". there should be no chance
> > of a farm and server sharing the same name.
> >
> > Any ideas? Any help would be greately appreciated.
> >
> >
>
>
>
 
Back
Top