VPN - Network Novice Questions

[porbarfarms@gmail.com]

At our main office we have a Windows 2003 Server running as a DC and a
Terminal Server - I know not recommended but we have to cut corners on
hardware expenses temporarily. We are setting up a remote office that
will be using Thin-clients with the Windows CE 5.0 OS. Our phone
company is installing a VoIP system at the remote office and will also
be setting up a VPN from the remote office to the main office (they
support the VoIP here too and have their router in place) and they
will supply the router at the remote location. We have a static IP at
each location.

The remote clients will login to the Terminal Server with Active
Directory/Domain credentials.

Here is our current network setup:

Location A: Main Office

Server =Windows 2003 Standard Edition
Clients: all XP Pro
Running DHCP = Yes -- handing out addresses: 192.168.1.xxx to local
clients
# of NICs = 1
LAN IP: 192.168.1.1
Subnet Mask:255.255.255.0
Gateway: 192.168.1.254 -- router IP
DNS Server: 192.168.1.1
Internet Connection: Cable

Location B: Remote Office

Server: None
Clients: Wyse Winterms with Windows CE5.0
Internet Connection: DSL

Here are our questions:

1. Should the router at the remote site run DHCP or do you typically
let the remotes get IP addresses from the Server at the main location?
Or, do we statically assign IPs to the remotes and turn off DHCP on
the router?

2. What IP address range should the remotes use? For example,
192.168.2.xxx?

3. We have read many post where the serve has 2 NICs and ours has one.
Should we add one and how would that affect our setup?

Thanks

 

[Lanwench [MVP - Exchange]]

Re: VPN - Network Novice Questions

porbarfarms@gmail.com wrote:
> At our main office we have a Windows 2003 Server running as a DC and a
> Terminal Server - I know not recommended but we have to cut corners on
> hardware expenses temporarily.

Ouch - yes, this is really a very bad idea, even as a temporary measure! If
it's only a hardware issue, get VMWare or other virtualization software and
install W2003 & TS within *that*.

However, note that as your questions don't pertain to terminal services at
all, you'd be best off posting in
microsoft.public.windows.server.networking.

I also suggest that you try using a news client, such as Forte Agent,
Thunderbird, or even Outlook Express, rather than Google Groups or the MS
web interface to their It's a lot easier to do nearly everything that way.
You can mark messages to be watched, filter the views so you can see replies
to your posts easily, and search.

The Microsoft public news server is msnews.microsoft.com and you can
subscribe to as many groups as you like; no authentication is required.

The following is from a post by MVP Malke ...

-------------------------------------------------------
Here's information on Usenet and using a newsreader:

http://www.elephantboycomputers.com/page3.html#12-09-02 - a brief
explanation of newsgroups
http://michaelstevenstech.com/outlo...ssnewreader.htm
http://rickrogers.org/setupoe.htm
http://support.microsoft.com/defaul...wto/default.asp
- Set Up Newsreader

http://www.dts-l.org/goodpost.htm
http://www.catb.org/~esr/faqs/smart-questions.html
http://aumha.org/nntp.htm - list of MS newsgroups
microsoft.public.test.here - MS group to test if your newsreader is
working properly
http://www.mailmsg.com/SPAM_munging.htm - how to munge email address
http://www.blakjak.demon.co.uk/mul_crss.htm - multiposting vs.
crossposting

Some newsreaders for Windows
http://www.forteinc.com/agent/index.php - for Forte
http://www.mozilla.org (Thunderbird does newsgroups)
http://gravity.tbates.org/

-------------------------------------





> We are setting up a remote office that
> will be using Thin-clients with the Windows CE 5.0 OS. Our phone
> company is installing a VoIP system at the remote office and will also
> be setting up a VPN from the remote office to the main office (they
> support the VoIP here too and have their router in place) and they
> will supply the router at the remote location. We have a static IP at
> each location.
>
> The remote clients will login to the Terminal Server with Active
> Directory/Domain credentials.
>
> Here is our current network setup:
>
> Location A: Main Office
>
> Server =Windows 2003 Standard Edition
> Clients: all XP Pro
> Running DHCP = Yes -- handing out addresses: 192.168.1.xxx to local
> clients
> # of NICs = 1
> LAN IP: 192.168.1.1
> Subnet Mask:255.255.255.0
> Gateway: 192.168.1.254 -- router IP
> DNS Server: 192.168.1.1
> Internet Connection: Cable
>
> Location B: Remote Office
>
> Server: None
> Clients: Wyse Winterms with Windows CE5.0
> Internet Connection: DSL
>
> Here are our questions:
>
> 1. Should the router at the remote site run DHCP or do you typically
> let the remotes get IP addresses from the Server at the main location?
> Or, do we statically assign IPs to the remotes and turn off DHCP on
> the router?
>
> 2. What IP address range should the remotes use? For example,
> 192.168.2.xxx?
>
> 3. We have read many post where the serve has 2 NICs and ours has one.
> Should we add one and how would that affect our setup?
>
> Thanks