Re: SBS2003 - Terminal Server - RWW too many steps
- From: "Cary Shultz" <cshultz@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 24 May 2008 18:03:38 -0400
Chriss,
Thanks. This is what I thought -BUT- I work mainly with WIN2003 Standard and Enterprise. I am pretty familiar with the basics of SBS2003 and have some very specific knowledge in some areas but wanted to ask to make sure that I offer the best solution for the client -AND- do not make a decision that eventually paints us (and, more importantly, the client) into a corner with respect to what solutions are available.
Cary
"Cris Hanna (SBS-MVP)" <crisnospamhanna@xxxxxxxxxxxxxxxxxxxxx> wrote in message news:eOmJidevIHA.4876@xxxxxxxxxxxxxxxxxxxxxxx
Assuming Cliff is correct that these are coming from the outside.
You can infact redirect 3389 to the TS Server.
3389 is not required for SBS especially since you have other management software.
--
Cris Hanna [SBS-MVP]
-------------------------------------------------
Microsoft MVPs
Independent Experts (MVPs do not work for MS)
Real World Answers
---------------------------------------------------------
Please do not contact me directly regarding issues
"Cary Shultz" <cshultz@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:uZZcgFevIHA.5520@xxxxxxxxxxxxxxxxxxxxxxx
Good afternoon!
Okay, asking a stupid question because we have a client that does not want
to use RWW to connect to the Terminal Server because it "is too many steps
and takes way to long to get there". They want a shortcut on the desktop
that takes them to the Terminal Server. Anything more than that is
unacceptable. I am not sure that I understand why RWW is unacceptable.
They say that it takes too long!
[begin rant] This is one of the major problems with us in the USA. We all
seem to want instant gratification and if something takes 20 seconds to do
then we do not want to do it. [end rant]
Anyway, just a few questions regarding this (not asking if it is a good idea
or not...just how to best do this):
1) thinking that I can just change the listening port on the TS from 3389 to
something else and then create a shortcut on their desktop pointing to "IP
Address:something else".
Now, this will most probably break accessing the TS via RWW. Apparently,
this is not a problem for them. It is for me, but I do not count.
2) redirect RDP traffic on the Firewall from the SBS machine to the Terminal
Server. No one accesses the SBS2003 machine via RDP anyway.
Now, this would remove our ability to access the SBS2003 box via RDP but we
have management software on all machines in the environment so remote
access - per se - is not an issue. Doing this would simply remove the
ability to directly access the SBS2003 box externally via RDP.
Of these two ideas which one is "better"? With "better" meaning fewer
negatives.
I really really really really do not understand how RWW "takes too long".
And, to clarify, I am familiar with the "options" page potentially taking a
long time to load...this is not part of the "problem" for them.
NOTE: the "options" page being where the user - after supplying
credentials - is presented with the "connect to e-mail, connect to my
company's application sharing computer, etc." page.
Thanks,
Cary
- References:
- SBS2003 - Terminal Server - RWW too many steps
- From: Cary Shultz
- Re: SBS2003 - Terminal Server - RWW too many steps
- From: Cris Hanna \(SBS-MVP\)
- SBS2003 - Terminal Server - RWW too many steps
- Prev by Date: Re: SBS2003 - Terminal Server - RWW too many steps
- Next by Date: Re: SBS2003 - Terminal Server - RWW too many steps
- Previous by thread: Re: SBS2003 - Terminal Server - RWW too many steps
- Next by thread: Re: SBS2003 - Terminal Server - RWW too many steps
- Index(es):
Relevant Pages
|
