As a small business owner I have been thrown into the
role of IT. I have a server with about 8 in office
workstations. I would like to set up terminal services
when some employees can not make it in to work. I
currently have a setup as such. Internet
modem>router>switch>to work stations and server. Because
of internet problems my ISP has provided me with a Cicso
modem with a builtin router. I was told by them that if
I want to utilize terminal services that I would want to
give me exchange a seperate static IP addess and I could
set the other info up as it is currently. I'm very green
to this please help. Any tutorials would help
tremediously. Thanks

Re: Static IP, Terminal Server , Exchange by Marina

Marina
Sun Apr 11 20:00:50 CDT 2004

Is this SBS 2000? How many nics in the server? Do you have a static public
IP? How about VPN?

--
Regards,

Marina
Microsoft SBS-MVP

"Jack" <Jack5083@lycos.com> schreef in bericht
news:1b2af01c42028$edf00f90$a401280a@phx.gbl...
> As a small business owner I have been thrown into the
> role of IT. I have a server with about 8 in office
> workstations. I would like to set up terminal services
> when some employees can not make it in to work. I
> currently have a setup as such. Internet
> modem>router>switch>to work stations and server. Because
> of internet problems my ISP has provided me with a Cicso
> modem with a builtin router. I was told by them that if
> I want to utilize terminal services that I would want to
> give me exchange a seperate static IP addess and I could
> set the other info up as it is currently. I'm very green
> to this please help. Any tutorials would help
> tremediously. Thanks



Re: Static IP, Terminal Server , Exchange by Merv

Merv
Sun Apr 11 20:46:41 CDT 2004

I assume you have SBS 2000 now. I also assume you have not yet purchased a
second server to be used as the terminal server. It appears you are only
using the SBS with a single NIC so you are not using ISA as a firewall,
meaning you must be using a hardware firewall (maybe your Cisco router).
What are the OS of your LAN workstations and the remote workstations?

You could set up a Win2K member server with Terminal Services (running in
application mode) next to the SBS 2000 server and allow your users to VPN
into the SBS and then fire up a TS session on the TS box without having to
acquire another public IP address.

With SBS 2000, the SBS CALs cover access to a Windows 2000 member server
(assuming you don't exceed the total number of SBS CALs for the combination
of your LAN and TS sessions; the TS server itself will consume one SBS CAL).
With TS 2000, all Win2K and WinXP Pro computers do not require a TS CAL to
access the TS 2000 component. However, any Win9x or Win XP Home Edition
machine will require a TS 2000 CAL (whether they are LAN based or remote
machines). You would also need an app license (like MS Office, etc) for
each user who accesses these on the TS.

If your LAN workstations are currently WinXP Pro and your LAN workstations
are each dedicated to a single user, SBS 2003 (with USER CALs) may be a
better road for you to take since your users could use RWW (Remote Web
Workplace) from any Internet-connected computer to remotely control there
office workstations. While installing a new operating system on your server
may seem like a daunting challenge, with only 8 workstations (and presumably
8 users), this should be doable as a clean install after you have migrated
or backed up all user folders, company data and Exchange mailboxes (to .pst
files). I'm presuming you're not using SQL 2000 on the SBS server now. If
your Cisco router has a good firewall in it, you could use SBS 2003 Standard
Edition (about $500-600), 2 NICs in your SBS and implement the "basic"
firewall in SBS 2003 (in addition to your hardware firewall). SBS 2003
comes with 5 CALs, so you'd need to buy 5 more (only available in lots of 5)
for about $100 per CAL.

--
Merv Porter [SBS MVP]
===================================

"Jack" <Jack5083@lycos.com> wrote in message
news:1b2af01c42028$edf00f90$a401280a@phx.gbl...
> As a small business owner I have been thrown into the
> role of IT. I have a server with about 8 in office
> workstations. I would like to set up terminal services
> when some employees can not make it in to work. I
> currently have a setup as such. Internet
> modem>router>switch>to work stations and server. Because
> of internet problems my ISP has provided me with a Cicso
> modem with a builtin router. I was told by them that if
> I want to utilize terminal services that I would want to
> give me exchange a seperate static IP addess and I could
> set the other info up as it is currently. I'm very green
> to this please help. Any tutorials would help
> tremediously. Thanks



Re: Static IP, Terminal Server , Exchange by Jack

Jack
Mon Apr 12 07:47:48 CDT 2004

The Server does have 2 NICs a LAN and a WAN. I currently
have 5 static IP addresses. We currently using 1 for
exchange.
>-----Original Message-----
>Is this SBS 2000? How many nics in the server? Do you
have a static public
>IP? How about VPN?
>
>--
>Regards,
>
>Marina
>Microsoft SBS-MVP
>
>"Jack" <Jack5083@lycos.com> schreef in bericht
>news:1b2af01c42028$edf00f90$a401280a@phx.gbl...
>> As a small business owner I have been thrown into the
>> role of IT. I have a server with about 8 in office
>> workstations. I would like to set up terminal services
>> when some employees can not make it in to work. I
>> currently have a setup as such. Internet
>> modem>router>switch>to work stations and server.
Because
>> of internet problems my ISP has provided me with a
Cicso
>> modem with a builtin router. I was told by them that
if
>> I want to utilize terminal services that I would want
to
>> give me exchange a seperate static IP addess and I
could
>> set the other info up as it is currently. I'm very
green
>> to this please help. Any tutorials would help
>> tremediously. Thanks
>
>
>.
>

Re: Static IP, Terminal Server , Exchange by Marina

Marina
Tue Apr 13 11:17:49 CDT 2004

In fact one static IP would be sufficient. If your router is configured
properly for opening the right ports and forwarding to your external nic-IP,
you should be fine. You can use VPN for remote access. In that case make
sure the router handles the GRE-protocol which is needed for VPN (as well as
port 1723).


--
Regards,

Marina
Microsoft SBS-MVP

"Jack" <anonymous@discussions.microsoft.com> schreef in bericht
news:187e401c4208c$5beb3cf0$a601280a@phx.gbl...
> The Server does have 2 NICs a LAN and a WAN. I currently
> have 5 static IP addresses. We currently using 1 for
> exchange.
> >-----Original Message-----
> >Is this SBS 2000? How many nics in the server? Do you
> have a static public
> >IP? How about VPN?
> >
> >--
> >Regards,
> >
> >Marina
> >Microsoft SBS-MVP
> >
> >"Jack" <Jack5083@lycos.com> schreef in bericht
> >news:1b2af01c42028$edf00f90$a401280a@phx.gbl...
> >> As a small business owner I have been thrown into the
> >> role of IT. I have a server with about 8 in office
> >> workstations. I would like to set up terminal services
> >> when some employees can not make it in to work. I
> >> currently have a setup as such. Internet
> >> modem>router>switch>to work stations and server.
> Because
> >> of internet problems my ISP has provided me with a
> Cicso
> >> modem with a builtin router. I was told by them that
> if
> >> I want to utilize terminal services that I would want
> to
> >> give me exchange a seperate static IP addess and I
> could
> >> set the other info up as it is currently. I'm very
> green
> >> to this please help. Any tutorials would help
> >> tremediously. Thanks
> >
> >
> >.
> >