General discussion


Network Design Problem

By monsi ·
Hi, here is the scenario

We are a small UK company (20 users all with win 2000 pro) using Windows 2000 SBS for email (exchange), file & print and database (sql) services, connected to the internet behind an adsl modem/router and linux (IPcop) firewall.

We are opening two new offices another in the UK and one in the US
The UK site will just be a single user site (probably dial up VPN)
The US site will be similar size to the main UK site

What does any one recommend in the way of network design and suggested hardware? I?ve got a few ideas but I?ve not have to design this size network before

What is the best way of setting up W2K Server and AD? Can I use a second copy of SBS for the US site and connect this to the main UK site?

Thanks in advance


This conversation is currently closed to new comments.

Thread display: Collapse - | Expand +

All Comments

Collapse -

by CG IT In reply to Network Design Problem

ah hate to break the bad news to you but Small Business Server won't establish trusts between domains. built in limitation. So no you can't use a second copy of SBS and connect it to your other SBS site. The other limitation is # of computers that connect. SBS2000 is 50 SBS2003 is 75. This is also a built in limitation. This limitation applies to ALL computers be they servers or workstations.

you can try to do subdomains within your domain namespace, use scopes and replicate AD between the sites using AD sites and services. Since subdomains within the root domain implicitly trust all within the domain, you might be able to replicate AD on a DC in a remote site. Then have local users authenticate to their local DC. the Site link will require you to have an active connection to the other sites either with a dedicated link or a VPN tunnel [use VPN endpoint routers which establish and maintain the tunnel between themselves clients just use the tunnel].

Collapse -

by CG IT In reply to

another word of caution on the # of computers allowed to connect. You'll need CALS for each computer on the network on your primary site which runs SBS. NOT by site. The site that runs SBS {PDC} handles the CALS for all within the domain. Even if local users use a local DC to authenticate with. The SBS PDC counts em as a connection.

Collapse -

by CG IT In reply to

last word of caution: AD will handle everyone within the domain including remote sites. SO that means a remote site isn't autonomous. You can delegate some Ad control to a site but remember setting up OU's and GP will be propogated to ALL including remote sites. [that's the trust relationship between domains limitation. What you do at the UK site will effect the US site and vice versa.

Collapse -

by CG IT In reply to

last comment [ha ha] Exchange server. Configuring Exchange [which uses AD] running on SBS can be a real pain. If you have an exchange expert or know of one, consult em about your plans and how you want exchange mail service to work. You might not be able to do what you want to do using SBS simply because of Exchange 2000 [which uses AD] and how it will handle mail at each site.

Collapse -

by CG IT In reply to

IMO if you think you might possibly grow in size again at any point in time, dump SBS and go with W2K or W2003 [non SBS]. Setting up the network structure now with growth in mind and switching to W2K or W2003 will solve a TON of headaches further down the line. Might cost a chunk more $$ in stand alone copies of Exchange, W2K/W2003 licenses for each site's copy and CALS but the flexibility they provide will outweigh the anguish, frustration,hairpulling, you'll experience trying to switch from SBS to a W2003/W2K [non SBS]in the future.

Collapse -

by monsi In reply to

Poster rated this answer.

Collapse -

by monsi In reply to Network Design Problem

This question was closed by the author

Related Discussions

Related Forums