New Network Setup 1

[bookser]

I am setting up a small office network. There are currently 10 local machines, 9 running windows XP and 1 running windows me. There is also one server running Windows 2000 Server. The office was using a dynamic DSL connection to access the Internet. The connection was recently upgraded to a DSL connection with 5 useable static IP addresses. The new DSL router has been installed and has an additional static IP address. What is the best way to configure the server so all of the systems in the office will be able to file share and be set up for the internet through the static DSL account. Thanks

Brad

 

[Seaspray0]

You don't have enough public ip addresses for all the clients, nor do you really need that many. Your DSL router should have NAT capability along with DHCP services to go along with it. With NAT, you can use private addresses (typically 192.168.0.x subnet 255.255.255.0) for your clients and your router will do the address translation to get you on the internet through a single public address (Similar to internet connection sharing). Check out the capabilities of your router. You may be able to pool the public ip addresses through NAT, redirect a public address to a private address, accept VPN connections, etc. You should be able to drop some of those public addresses.

If the router doesn't do these things, the SERVER WILL. Remote routing and access is very good on 2000 server.

 

[bookser]

Will this allow me to setup a Local Domain for file and print sharing?

 

[june1980]

Well, For such a small network, unless you're planning on expansion, I wouldn't setup your network as a domain because your server will then need to be the primary domain controller. You'll need to setup DNS and Active Directory, promote the server to PDC status..... things can get hard at this point. I would setup your server as a workgroup server without AD or DNS.

But to answer your question, it will allow for a local domain, but you'll have to assign a static IP to your domain controler. Don't worry, the static IP can be a private address in the same range as your DHCP scope. FYI - be sure that you take the domain controller's IP out of the DHCP scope. Duplicate IPs cause problems.