How do I complete setup?

[John F Kappler]

We have a domain controlled by a SBServer 2003. On that domain we have
a WServer 2003 for TS.

The SBServer has the TS License Manager activated.

The current users of the SBServer are 10 local PCs, plus a copule of
Laptop users who use ConnectComputer or OWA. Usual sort of thing.

At some outlying offices, we have five users who work on local (to
them) PCs, either standalone or locally peer-to-peer networked.

We do NOT want to make these into regular SBServer Users as their
ability to connect would be intermittent.

However, when they have access to the Internet, we would like them to
be able to access and application which has a client installed on the
TS WServer.

So far all we have done is add the WServer to the SBServer domain.
I presume we have to add these users to the SBServer, but I dont
understand how we tell the SBServer that when this person connects
they need to be passed to the WServer?

Additionally, do I have to open any specific ports on the external
router, and, if so, do I route them to the ip address of the SBServer
(as usual) or direct to the WServer?

Sorry for my basic lack of knowledge - I tried revieing previous posts
but found it difficult to search not knowing what topics I might be
looking for! Please feel free to point me at document that might help
(I already have "Deploying Windows Server 2003 Terminal Server to Host
User Desktops in a Windows Small Business Server 2003 Environment")

TIA,

JohnK

 

[Lanwench [MVP - Exchange]]

Re: How do I complete setup?

John F Kappler <john@pceffect.co.uk> wrote:
> We have a domain controlled by a SBServer 2003. On that domain we have
> a WServer 2003 for TS.
>
> The SBServer has the TS License Manager activated.
>
> The current users of the SBServer are 10 local PCs, plus a copule of
> Laptop users who use ConnectComputer or OWA. Usual sort of thing.
>
> At some outlying offices, we have five users who work on local (to
> them) PCs, either standalone or locally peer-to-peer networked.
>
> We do NOT want to make these into regular SBServer Users as their
> ability to connect would be intermittent.

That's wise, I think.
>
> However, when they have access to the Internet, we would like them to
> be able to access and application which has a client installed on the
> TS WServer.

Sure.
>
> So far all we have done is add the WServer to the SBServer domain.

Since you're using SBS, note that it's very wizard-centric. Did you first
create the computer account for the server on SBS as you would a
workstation, and then run /connectcomputer on the TS box? That's the way you
want to do it.


> I presume we have to add these users to the SBServer,

Yes, you have to create user accounts for the remote users, just as though
they were going to connect on your LAN. Use the SBS server management
console, just as you do for your LAN-connected users. (right? ignore these
wizards at your peril).

> but I dont
> understand how we tell the SBServer that when this person connects
> they need to be passed to the WServer?

You don't tell it anything. What you should do is have them go to the Remote
Web Workplace page and select the Terminal Services box ("connect to my
company's application sharing server.")
>
> Additionally, do I have to open any specific ports on the external
> router, and, if so, do I route them to the ip address of the SBServer
> (as usual) or direct to the WServer?

If you already have RWW enabled, you don't need to do anything. If you
don't, you need to port-forward 443 to your SBS box, and also TCP 4125 in
your firewall, and re-run the SBS "connect to the internet" wizard. (see
wizard comments above)
>
> Sorry for my basic lack of knowledge - I tried revieing previous posts
> but found it difficult to search not knowing what topics I might be
> looking for! Please feel free to point me at document that might help
> (I already have "Deploying Windows Server 2003 Terminal Server to Host
> User Desktops in a Windows Small Business Server 2003 Environment")
>

For anything that isn't Terminal Services related (and your questions
aren't, really), you'd be best off posting in
microsoft.public.windows.server.sbs. SBS is its own beast and does things
its own way - you'll get a lot of good help in there.

I think you'll also want to look into group policy stuff so you can lock
down the TS box properly.

> TIA,
>
> JohnK