• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Windows 2000 Server and Net access...

Diabolus

Banned
Okay, here's the deal and maybe somebody can help me...

I'm working on a project for my uncle (he owns a day spa with his wife) and I'm working on setting up his network. Right now he has wires run but a terribly slow P2P network using only simple shares on different nodes to get files back/forth from one place to another. It's slow and inefficient.

Anyhow, I'm going to upgrade him to Windows 2000 server to run his network. There's a program that needs to be served to clients and that's no big deal.. I can set that up. However, the manager of his shop wants to get internet access for the office, except he wants to limit that access to only certain staff.

So first question... I'm going to use one computer as a domain controller for the network and the internet proxy. They will not be serving any outside visitors so the server will not be a webserver. I would need a second NIC to get the internet served to the network, correct? And will it be a difficult operation to get up and running after adding a second NIC (will it conflict with the first NIC, any special software, etc...)?

Next question is the proxy server. I was going to use Microsoft ISA Server but I've read that it is VERY complicated and inefficient. I *do* need to let only specific users have access to the internet, namely the managers and a few employees as well as the owners (my aunt/uncle). Is ISA server a good application to do this? And how hard is it to do it using ISA server?

I hope I made my questions pretty clear..

Let me know 🙂
 
The easiest solution would be to get a Cable/DSL router for about $50 and then deny net access through the router.

Unless this Day spa has a lot of computers and an on call tech, I see no reason to setup a DC. I know I didn't really answer any of your questions, but Win2k servers can be a pain in the ass. You'll spend hours configuring the damn things and then hours fixing them when they break (which, thank god isn't too often).

 
Win2K Server + ISA Server is going to be extremly expensive, I don't know if it's worth it for a handfull of people. And AD is going to be a lot of work to get right, also probably overkill since all the benefits of it apply to large corporations.

Personally I would use a box running Linux, it would be simple to allow/deny access to the Internet via IP or hostname and if you really want a caching proxy squid is free and works great. Samba can handle the file sharing easily, and only be listening on one NIC unlike MS' SMB server which always listens on all interfaces.

If you're really intent on using Win2K+ISA Server, check out isaserver.org.
 
Back
Top