Terminal Server Session brokering and publishing via ISA 2006

I'm in the process of setting up 3 Terminal servers for use by externally located individuals. I'm hoping to set them up with a Terminal Server Session Broker, but have a few questions before I finalize the plan.

The 3 Terminal Servers will be published externally via 3 ISA 2006 Standard servers. Each ISA server is on a different internet connection. For ease of use by end users, I'd like to only publish 1 TS per ISA server (since I'd have to set the second and 3rd to use non-standard ports to publish them).

The round robin-DNS would obviously be different internally than externally.

So, what I need to know, is when the Broker returns the Terminal Server to connect to back to the client, what will it return? With IP address redirection turned on, I kind of assume that the Session Broker will return the server's internal IP, since neither it, nor the terminal server itself, are aware that it's also associated with an external IP. I'm also assuming that this will prevent the client on the outside from being able to connect.

If I leave IP address redirection turned off, and stick with token redirection, will this work any better, or are the token's still based on IP?

Short of round-robin DNS, is there any way to effectively load-balance, or at least provide Session re-connection to clients outside the WAN?

LVL 1
tilbardAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Keith AlabasterEnterprise ArchitectCommented:
Great question - shame I don't know the answer. I have not used a TS Broker before.

Your comment about various port number requirements is valid if you only have one public ip address on each of your internet connections. the restriction is one protocol/port per IP address instance, not per connection instance.

Round-robin is never a great solution really as a node down will give you a one in three hit failure - yes, most can live with it but it is still a bit 'iffy.

If the broker is inside then it will return the internal ip address - not much you can do about that as far as I know. Personally we publish (securely) the TSweb portal so that authorised users select the connection to use AFTER they have connected initially - this removes the issue with the NAT of internal/external Ip addresses. Doesn't really help for published apps though.

Sorry that this is little help - ISA is my area but TS is a bit of a dark art to me.

Keith
ISA MVP
0
Keith AlabasterEnterprise ArchitectCommented:
No point PAQ'ing it as, although it is fact, you cannot tell if it resolved the issue therefore it is of no value to the database. It cannot be accepted for the same reason. A delete - no refund would be my suggestion.
0
ee_autoCommented:
Question PAQ'd, 500 points not refunded, and stored in the solution database.
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft Server OS

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.