TS server in SBS2003 environment newbie question

  • Thread starter Thread starter Andrew Kennard
  • Start date Start date
A

Andrew Kennard

Guest
Hi all

I've been googling for info on TS and the general concensus seems to be that
if you want one on a network that has a SBS2003 server then you should
install it on a separate box as the built in one is only designed for
administration

My question is if I do this an connect the new TS box to the local network.
How am I going to be able to access it from the outside world as it is not
directly connected ie it has a private IP addres ?

I assume I need to do something on the SBS server to get the packet to it
but where should I start

Thanks in advance for your help

Andrew
 
Re: TS server in SBS2003 environment newbie question

You can configure your firewall to forward all incoming traffic on
port 3389 (the default port for rdp traffic) to the Terminal
Server.
If you also need to rdp to your SBS server from the outside, then
you could use a different port for the TS.

Note that you might get more help in the SBS newsgroup:
microsoft.public.windows.server.sbs

_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
microsoft.public.windows.terminal_services:

> Hi all
>
> I've been googling for info on TS and the general concensus
> seems to be that if you want one on a network that has a SBS2003
> server then you should install it on a separate box as the built
> in one is only designed for administration
>
> My question is if I do this an connect the new TS box to the
> local network. How am I going to be able to access it from the
> outside world as it is not directly connected ie it has a
> private IP addres ?
>
> I assume I need to do something on the SBS server to get the
> packet to it but where should I start
>
> Thanks in advance for your help
>
> Andrew
 
Re: TS server in SBS2003 environment newbie question

Vera thanks for the reply I shal post this on the SBS group

Hi all

What do I need to do on a 2 NIC SBS server to get the packets to the TS
server ?

Cheers


"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AACDEB716526veranoesthemutforsse@207.46.248.16...
> You can configure your firewall to forward all incoming traffic on
> port 3389 (the default port for rdp traffic) to the Terminal
> Server.
> If you also need to rdp to your SBS server from the outside, then
> you could use a different port for the TS.
>
> Note that you might get more help in the SBS newsgroup:
> microsoft.public.windows.server.sbs
>
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
> microsoft.public.windows.terminal_services:
>
>> Hi all
>>
>> I've been googling for info on TS and the general concensus
>> seems to be that if you want one on a network that has a SBS2003
>> server then you should install it on a separate box as the built
>> in one is only designed for administration
>>
>> My question is if I do this an connect the new TS box to the
>> local network. How am I going to be able to access it from the
>> outside world as it is not directly connected ie it has a
>> private IP addres ?
>>
>> I assume I need to do something on the SBS server to get the
>> packet to it but where should I start
>>
>> Thanks in advance for your help
>>
>> Andrew
 
Re: TS server in SBS2003 environment newbie question

When you run through the Connect to the Internet wizard from Server
Management everything is set. You then connect to the application
sharing server from http://mail.realworlddomain.com/remote or whatever
record you set up. Thsi is called Remote Web Workplace or RWW. This
also lets you connect to user desktops attached to your SBS network.

On Thu, 29 May 2008 09:22:43 +0100, "Andrew Kennard" <b@a.com> wrote:

>Vera thanks for the reply I shal post this on the SBS group
>
>Hi all
>
>What do I need to do on a 2 NIC SBS server to get the packets to the TS
>server ?
>
>Cheers
>
>
>"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
>news:Xns9AACDEB716526veranoesthemutforsse@207.46.248.16...
>> You can configure your firewall to forward all incoming traffic on
>> port 3389 (the default port for rdp traffic) to the Terminal
>> Server.
>> If you also need to rdp to your SBS server from the outside, then
>> you could use a different port for the TS.
>>
>> Note that you might get more help in the SBS newsgroup:
>> microsoft.public.windows.server.sbs
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi all
>>>
>>> I've been googling for info on TS and the general concensus
>>> seems to be that if you want one on a network that has a SBS2003
>>> server then you should install it on a separate box as the built
>>> in one is only designed for administration
>>>
>>> My question is if I do this an connect the new TS box to the
>>> local network. How am I going to be able to access it from the
>>> outside world as it is not directly connected ie it has a
>>> private IP addres ?
>>>
>>> I assume I need to do something on the SBS server to get the
>>> packet to it but where should I start
>>>
>>> Thanks in advance for your help
>>>
>>> Andrew
>
See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx
 
Re: TS server in SBS2003 environment newbie question

Andrew,

Howdy. Vera is absolutely correct (when is she not?). However, please
understand that SBS is a completely different animal.

Here is what I would suggest:

Take a look at RWW (Remote Web Workplace). In the SBS world, RWW is a very
cool thing. There are a lot of things that you can do with it, like access
OWA or your internal SharePoint from the outside world or, since you are
asking about TS, access your "company's application sharing server".

Here - in a nutshell - is how things work:

You enter https://mail.mydomain.com/remote (yes, /remote.....).
You log in with user name and password (and, user name would *NOT* be
mydomain\cshultz, it is just 'cshultz')
The next page presents the logged in user with potentially several options
Assuming you select Terminal Servers (in RWW world, the 'application sharing
server')
The next screen presents you with all of the 'application sharing servers'
Select it and you are taken to the TS - log in and you are there.


Now, how does this work? The SBS box is a 'proxy' in that the incoming
connection is over Port 4125 (so, you need to create this 'service' on your
Firewall and then point it to the internal IP Address of the SBS box).
Once you provide credentials and make a selection (from that list I
mentioned) the SBS box 'forwards' the user to the proper place. Since we
are talking about TS it would forward the user to the TS box on Port 3389.

I would not necessarily change any ports - generically speaking - because
this might break some things in RWW (which can probably be changed).

Now - as Vera stated - you can probably change the rule on your Firewall so
that RDP traffic is sent directly to your TS box. I have this set up as
such for one client because they want everything to be an icon on the
desktop and accessible via a double-click (RWW and its five steps or so is
toooooo slooooow). Kinda retarded to me....but what do I know?

Anyway, it works very well -AND- you do not break anything in RWW (which
also, for example, affords you the ability to connect to your computer in
the office!).

HTH,

Cary


"Andrew Kennard" <b@a.com> wrote in message
news:O8hAiJOwIHA.4848@TK2MSFTNGP05.phx.gbl...
> Hi all
>
> I've been googling for info on TS and the general concensus seems to be
> that if you want one on a network that has a SBS2003 server then you
> should install it on a separate box as the built in one is only designed
> for administration
>
> My question is if I do this an connect the new TS box to the local
> network. How am I going to be able to access it from the outside world as
> it is not directly connected ie it has a private IP addres ?
>
> I assume I need to do something on the SBS server to get the packet to it
> but where should I start
>
> Thanks in advance for your help
>
> Andrew
>
 
Re: TS server in SBS2003 environment newbie question

Thanks for this excellent explanation, Cary! I knew there was more
help to get in the SBS group!
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___

"Cary Shultz" <cshultz@nospam.outsourceitcorp.com> wrote on 29 maj
2008 in microsoft.public.windows.terminal_services:

> Andrew,
>
> Howdy. Vera is absolutely correct (when is she not?). However,
> please understand that SBS is a completely different animal.
>
> Here is what I would suggest:
>
> Take a look at RWW (Remote Web Workplace). In the SBS world,
> RWW is a very cool thing. There are a lot of things that you
> can do with it, like access OWA or your internal SharePoint from
> the outside world or, since you are asking about TS, access your
> "company's application sharing server".
>
> Here - in a nutshell - is how things work:
>
> You enter https://mail.mydomain.com/remote (yes, /remote.....).
> You log in with user name and password (and, user name would
> *NOT* be mydomain\cshultz, it is just 'cshultz')
> The next page presents the logged in user with potentially
> several options Assuming you select Terminal Servers (in RWW
> world, the 'application sharing server')
> The next screen presents you with all of the 'application
> sharing servers' Select it and you are taken to the TS - log in
> and you are there.
>
>
> Now, how does this work? The SBS box is a 'proxy' in that the
> incoming connection is over Port 4125 (so, you need to create
> this 'service' on your Firewall and then point it to the
> internal IP Address of the SBS box). Once you provide
> credentials and make a selection (from that list I mentioned)
> the SBS box 'forwards' the user to the proper place. Since we
> are talking about TS it would forward the user to the TS box on
> Port 3389.
>
> I would not necessarily change any ports - generically speaking
> - because this might break some things in RWW (which can
> probably be changed).
>
> Now - as Vera stated - you can probably change the rule on your
> Firewall so that RDP traffic is sent directly to your TS box. I
> have this set up as such for one client because they want
> everything to be an icon on the desktop and accessible via a
> double-click (RWW and its five steps or so is toooooo slooooow).
> Kinda retarded to me....but what do I know?
>
> Anyway, it works very well -AND- you do not break anything in
> RWW (which also, for example, affords you the ability to connect
> to your computer in the office!).
>
> HTH,
>
> Cary
>
>
> "Andrew Kennard" <b@a.com> wrote in message
> news:O8hAiJOwIHA.4848@TK2MSFTNGP05.phx.gbl...
>> Hi all
>>
>> I've been googling for info on TS and the general concensus
>> seems to be that if you want one on a network that has a
>> SBS2003 server then you should install it on a separate box as
>> the built in one is only designed for administration
>>
>> My question is if I do this an connect the new TS box to the
>> local network. How am I going to be able to access it from the
>> outside world as it is not directly connected ie it has a
>> private IP addres ?
>>
>> I assume I need to do something on the SBS server to get the
>> packet to it but where should I start
>>
>> Thanks in advance for your help
>>
>> Andrew
 
Re: TS server in SBS2003 environment newbie question

Andrew Kennard wrote:
> Vera thanks for the reply I shal post this on the SBS group
>
> Hi all
>
> What do I need to do on a 2 NIC SBS server to get the packets to the TS
> server ?
>
> Cheers
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
> news:Xns9AACDEB716526veranoesthemutforsse@207.46.248.16...
>> You can configure your firewall to forward all incoming traffic on
>> port 3389 (the default port for rdp traffic) to the Terminal
>> Server.
>> If you also need to rdp to your SBS server from the outside, then
>> you could use a different port for the TS.
>>
>> Note that you might get more help in the SBS newsgroup:
>> microsoft.public.windows.server.sbs
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi all
>>>
>>> I've been googling for info on TS and the general concensus
>>> seems to be that if you want one on a network that has a SBS2003
>>> server then you should install it on a separate box as the built
>>> in one is only designed for administration
>>>
>>> My question is if I do this an connect the new TS box to the
>>> local network. How am I going to be able to access it from the
>>> outside world as it is not directly connected ie it has a
>>> private IP addres ?
>>>
>>> I assume I need to do something on the SBS server to get the
>>> packet to it but where should I start
>>>
>>> Thanks in advance for your help
>>>
>>> Andrew
>
>
I connect to it using Remote Web Workplace and do not go straight 3389
to that TS box inside my SBS Land
 
Re: TS server in SBS2003 environment newbie question

Andrew Kennard wrote:
> Vera thanks for the reply I shal post this on the SBS group
>
> Hi all
>
> What do I need to do on a 2 NIC SBS server to get the packets to the TS
> server ?
>
> Cheers
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
> news:Xns9AACDEB716526veranoesthemutforsse@207.46.248.16...
>> You can configure your firewall to forward all incoming traffic on
>> port 3389 (the default port for rdp traffic) to the Terminal
>> Server.
>> If you also need to rdp to your SBS server from the outside, then
>> you could use a different port for the TS.
>>
>> Note that you might get more help in the SBS newsgroup:
>> microsoft.public.windows.server.sbs
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi all
>>>
>>> I've been googling for info on TS and the general concensus
>>> seems to be that if you want one on a network that has a SBS2003
>>> server then you should install it on a separate box as the built
>>> in one is only designed for administration
>>>
>>> My question is if I do this an connect the new TS box to the
>>> local network. How am I going to be able to access it from the
>>> outside world as it is not directly connected ie it has a
>>> private IP addres ?
>>>
>>> I assume I need to do something on the SBS server to get the
>>> packet to it but where should I start
>>>
>>> Thanks in advance for your help
>>>
>>> Andrew
>
>
I connect to it using Remote Web Workplace and do not go straight 3389
to that TS box inside my SBS Land
 
Re: TS server in SBS2003 environment newbie question

Andrew Kennard wrote:
> Vera thanks for the reply I shal post this on the SBS group
>
> Hi all
>
> What do I need to do on a 2 NIC SBS server to get the packets to the TS
> server ?
>
> Cheers
>
>
> "Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
> news:Xns9AACDEB716526veranoesthemutforsse@207.46.248.16...
>> You can configure your firewall to forward all incoming traffic on
>> port 3389 (the default port for rdp traffic) to the Terminal
>> Server.
>> If you also need to rdp to your SBS server from the outside, then
>> you could use a different port for the TS.
>>
>> Note that you might get more help in the SBS newsgroup:
>> microsoft.public.windows.server.sbs
>>
>> _________________________________________________________
>> Vera Noest
>> MCSE, CCEA, Microsoft MVP - Terminal Server
>> TS troubleshooting: http://ts.veranoest.net
>> ___ please respond in newsgroup, NOT by private email ___
>>
>> "Andrew Kennard" <b@a.com> wrote on 28 maj 2008 in
>> microsoft.public.windows.terminal_services:
>>
>>> Hi all
>>>
>>> I've been googling for info on TS and the general concensus
>>> seems to be that if you want one on a network that has a SBS2003
>>> server then you should install it on a separate box as the built
>>> in one is only designed for administration
>>>
>>> My question is if I do this an connect the new TS box to the
>>> local network. How am I going to be able to access it from the
>>> outside world as it is not directly connected ie it has a
>>> private IP addres ?
>>>
>>> I assume I need to do something on the SBS server to get the
>>> packet to it but where should I start
>>>
>>> Thanks in advance for your help
>>>
>>> Andrew
>
>
I connect to it using Remote Web Workplace and do not go straight 3389
to that TS box inside my SBS Land
 
Re: TS server in SBS2003 environment newbie question

Vera, you are welcome. I guess that maybe I have listened to a few people
over the years! Glad to help where I can.

Cary

"Vera Noest [MVP]" <vera.noest@remove-this.hem.utfors.se> wrote in message
news:Xns9AADE78B541BEveranoesthemutforsse@207.46.248.16...
> Thanks for this excellent explanation, Cary! I knew there was more
> help to get in the SBS group!
> _________________________________________________________
> Vera Noest
> MCSE, CCEA, Microsoft MVP - Terminal Server
> TS troubleshooting: http://ts.veranoest.net
> ___ please respond in newsgroup, NOT by private email ___
>
> "Cary Shultz" <cshultz@nospam.outsourceitcorp.com> wrote on 29 maj
> 2008 in microsoft.public.windows.terminal_services:
>
>> Andrew,
>>
>> Howdy. Vera is absolutely correct (when is she not?). However,
>> please understand that SBS is a completely different animal.
>>
>> Here is what I would suggest:
>>
>> Take a look at RWW (Remote Web Workplace). In the SBS world,
>> RWW is a very cool thing. There are a lot of things that you
>> can do with it, like access OWA or your internal SharePoint from
>> the outside world or, since you are asking about TS, access your
>> "company's application sharing server".
>>
>> Here - in a nutshell - is how things work:
>>
>> You enter https://mail.mydomain.com/remote (yes, /remote.....).
>> You log in with user name and password (and, user name would
>> *NOT* be mydomain\cshultz, it is just 'cshultz')
>> The next page presents the logged in user with potentially
>> several options Assuming you select Terminal Servers (in RWW
>> world, the 'application sharing server')
>> The next screen presents you with all of the 'application
>> sharing servers' Select it and you are taken to the TS - log in
>> and you are there.
>>
>>
>> Now, how does this work? The SBS box is a 'proxy' in that the
>> incoming connection is over Port 4125 (so, you need to create
>> this 'service' on your Firewall and then point it to the
>> internal IP Address of the SBS box). Once you provide
>> credentials and make a selection (from that list I mentioned)
>> the SBS box 'forwards' the user to the proper place. Since we
>> are talking about TS it would forward the user to the TS box on
>> Port 3389.
>>
>> I would not necessarily change any ports - generically speaking
>> - because this might break some things in RWW (which can
>> probably be changed).
>>
>> Now - as Vera stated - you can probably change the rule on your
>> Firewall so that RDP traffic is sent directly to your TS box. I
>> have this set up as such for one client because they want
>> everything to be an icon on the desktop and accessible via a
>> double-click (RWW and its five steps or so is toooooo slooooow).
>> Kinda retarded to me....but what do I know?
>>
>> Anyway, it works very well -AND- you do not break anything in
>> RWW (which also, for example, affords you the ability to connect
>> to your computer in the office!).
>>
>> HTH,
>>
>> Cary
>>
>>
>> "Andrew Kennard" <b@a.com> wrote in message
>> news:O8hAiJOwIHA.4848@TK2MSFTNGP05.phx.gbl...
>>> Hi all
>>>
>>> I've been googling for info on TS and the general concensus
>>> seems to be that if you want one on a network that has a
>>> SBS2003 server then you should install it on a separate box as
>>> the built in one is only designed for administration
>>>
>>> My question is if I do this an connect the new TS box to the
>>> local network. How am I going to be able to access it from the
>>> outside world as it is not directly connected ie it has a
>>> private IP addres ?
>>>
>>> I assume I need to do something on the SBS server to get the
>>> packet to it but where should I start
>>>
>>> Thanks in advance for your help
>>>
>>> Andrew
 
Re: TS server in SBS2003 environment newbie question

Thanks for the responses !

I shall get back to you when I get into this fully

Thanks again

Cheers

Andrew

"Cary Shultz" <cshultz@nospam.outsourceitcorp.com> wrote in message
news:OhhrJvXwIHA.1936@TK2MSFTNGP04.phx.gbl...
> Andrew,
>
> Howdy. Vera is absolutely correct (when is she not?). However, please
> understand that SBS is a completely different animal.
>
> Here is what I would suggest:
>
> Take a look at RWW (Remote Web Workplace). In the SBS world, RWW is a
> very cool thing. There are a lot of things that you can do with it, like
> access OWA or your internal SharePoint from the outside world or, since
> you are asking about TS, access your "company's application sharing
> server".
>
> Here - in a nutshell - is how things work:
>
> You enter https://mail.mydomain.com/remote (yes, /remote.....).
> You log in with user name and password (and, user name would *NOT* be
> mydomain\cshultz, it is just 'cshultz')
> The next page presents the logged in user with potentially several options
> Assuming you select Terminal Servers (in RWW world, the 'application
> sharing server')
> The next screen presents you with all of the 'application sharing servers'
> Select it and you are taken to the TS - log in and you are there.
>
>
> Now, how does this work? The SBS box is a 'proxy' in that the incoming
> connection is over Port 4125 (so, you need to create this 'service' on
> your Firewall and then point it to the internal IP Address of the SBS
> box).
> Once you provide credentials and make a selection (from that list I
> mentioned) the SBS box 'forwards' the user to the proper place. Since we
> are talking about TS it would forward the user to the TS box on Port 3389.
>
> I would not necessarily change any ports - generically speaking - because
> this might break some things in RWW (which can probably be changed).
>
> Now - as Vera stated - you can probably change the rule on your Firewall
> so that RDP traffic is sent directly to your TS box. I have this set up
> as such for one client because they want everything to be an icon on the
> desktop and accessible via a double-click (RWW and its five steps or so is
> toooooo slooooow). Kinda retarded to me....but what do I know?
>
> Anyway, it works very well -AND- you do not break anything in RWW (which
> also, for example, affords you the ability to connect to your computer in
> the office!).
>
> HTH,
>
> Cary
>
>
> "Andrew Kennard" <b@a.com> wrote in message
> news:O8hAiJOwIHA.4848@TK2MSFTNGP05.phx.gbl...
>> Hi all
>>
>> I've been googling for info on TS and the general concensus seems to be
>> that if you want one on a network that has a SBS2003 server then you
>> should install it on a separate box as the built in one is only designed
>> for administration
>>
>> My question is if I do this an connect the new TS box to the local
>> network. How am I going to be able to access it from the outside world as
>> it is not directly connected ie it has a private IP addres ?
>>
>> I assume I need to do something on the SBS server to get the packet to it
>> but where should I start
>>
>> Thanks in advance for your help
>>
>> Andrew
>>
>
>
 
Back
Top