What's the best way to share an internet connection across anetwork??

Currently we have our network set up as follows:-

- Domain Controller (Windows 2000 Server)
- Exchange Server (Windows 2000 - member server)
- Web Server (Windows 2000 - NAT via Routing and Remote Access plugged
into broadband router)

This setup has served us well for almost 9 years but we're planning on
replacing our servers with new ones and I know we obviously need the
DC and the Exchange server but in terms of the Web Server am I right
in saying that the domain controller can just as easily become the web
server (or the exchange server instead?)??

I don't want the web server separate unless it's absolutely vital - I
don't see any problems with the exchange server taking on the role of
the web server also.

thanks in advance for your input

On Nov 27, 3:27 pm, eggedd2k <chrisnrac...@aol.com> wrote:
> Currently we have our network set up as follows:-
>
> - Domain Controller (Windows 2000 Server)
> - Exchange Server (Windows 2000 - member server)
> - Web Server (Windows 2000 - NAT via Routing and Remote Access plugged
> into broadband router)
>
> This setup has served us well for almost 9 years but we're planning on
> replacing our servers with new ones and I know we obviously need the
> DC and the Exchange server but in terms of the Web Server am I right
> in saying that the domain controller can just as easily become the web
> server (or the exchange server instead?)??
>
> I don't want the web server separate unless it's absolutely vital - I
> don't see any problems with the exchange server taking on the role of
> the web server also.
>
> thanks in advance for your input

Purely my opinion, but I would not put a publicly accessible web
server on a DC, that's asking for trouble.
I would also be wary of putting it on the Exchange server, as this
still contains Active Directory.

The Exchange server can sit on the DC no problem.

So I would team up Exchange and Domain controller, and keep the Web
server completely separate - and not even joined to the domain!

Alister

In this case, you may want to try SBS 2008. These links may help

Windows SBS 2008 How to
http://www.howtonetworking.com/sbs/2008sbs.htm

Windows SBSWindows Small Business Server. Can I install Terminal Services in
Windows SBS 2003? Can we change SBS 2003 name · Can we rename the SBS 2003
domain ...
www.howtonetworking.com/sbs/sbs.htm


--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"eggedd2k" <(E-Mail Removed)> wrote in message
news:d04f6dbf-c072-497d-9fb9-(E-Mail Removed)...
> Currently we have our network set up as follows:-
>
> - Domain Controller (Windows 2000 Server)
> - Exchange Server (Windows 2000 - member server)
> - Web Server (Windows 2000 - NAT via Routing and Remote Access plugged
> into broadband router)
>
> This setup has served us well for almost 9 years but we're planning on
> replacing our servers with new ones and I know we obviously need the
> DC and the Exchange server but in terms of the Web Server am I right
> in saying that the domain controller can just as easily become the web
> server (or the exchange server instead?)??
>
> I don't want the web server separate unless it's absolutely vital - I
> don't see any problems with the exchange server taking on the role of
> the web server also.
>
> thanks in advance for your input

Hello eggedd2k,

If you have not more then 75 users i would agree with Robert, to use SBS.
For up to 300 you can use EBS version.

Either Exchange or Web services should run on a DC, performance and security
reasons.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> Currently we have our network set up as follows:-
>
> - Domain Controller (Windows 2000 Server)
> - Exchange Server (Windows 2000 - member server)
> - Web Server (Windows 2000 - NAT via Routing and Remote Access plugged
> into broadband router)
> This setup has served us well for almost 9 years but we're planning on
> replacing our servers with new ones and I know we obviously need the
> DC and the Exchange server but in terms of the Web Server am I right
> in saying that the domain controller can just as easily become the web
> server (or the exchange server instead?)??
>
> I don't want the web server separate unless it's absolutely vital - I
> don't see any problems with the exchange server taking on the role of
> the web server also.
>
> thanks in advance for your input
>

cheers for your replies chaps.

We have 45 employees at present - will SBS 2003 be best? This goes
up to 65 users doesn't it??

I was under the impression Exchange should really run on it's own
server??

Hello eggedd2k,

As said before 75 users max on SBS. Exchange except on SBS should run on
it's own machine , also some other apps. Basically a DC should be DC/DNS/GC
and DHCP.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> cheers for your replies chaps.
>
> We have 45 employees at present - will SBS 2003 be best? This goes
> up to 65 users doesn't it??
>
> I was under the impression Exchange should really run on it's own
> server??
>