Windows networking

[BigDaddy]

Have Win2k3 S1 Server Eddition installed on the server machine which is also connected to ADSL. I also have 3 client PCs WinXP SP2 connected to this machine thru a switch.

How do I set up Internet and filesharing and I would also like to have DHCP so I don't have to type all the IP address on client machines.

And cos picture tells more than a 1000 words:

ps. Am asking this cos B4 I was using Kerio WINROUTE PRO but now I would like to give Windows' networking a try

[InTheWayBoy]

There are many ways to go at this...you would probably want to install at least DHCP on the server, but you might want to look into making it a Domain Controller, which can include DHCP, DNS, and much more. It's also more effort, so be prepaired.

If you go the easy route, then DHCP is all you'll really need. You'll need two NIC's in the server if you want to setup to work...one for DSL, the other for your LAN. You can use the built-in Internet Connection Sharing that Server provides to handle the NAT portion, with the DHCP you installed doing it's job. File sharing is usually as simple as right-clicking on the folder you want to share and edit the sharing properties. You'll have to watch out for permissions here, and that changes depending on how you have everything setup.

You'll need to figure out how you want to handle things...many people take the easy route and just give "Everyone" full control, but that is a very bad move. So if you want security you'll need to look at either using Active Directory or pre-configuring all the WinXP machines to have similar security settings. The Active Directory path is much harder, but worth it if you plan on doing a lot of reloads of your client machines.

[Ahmed-26]

Hello,

You can setup and configure DHCP server in the W2k3 server that is connected to the ADSL router and add 003 scope option in the DHCP to be the ip address of the ADSL router. Configure your client machines TCP/IP properties to obtain ip addresses automatically. Also, in the TCP/IP properties of the W2k3 server in the default gateway field write the ip address of the ADSL router and its recommended to use a static ip address for the server not from DHCP range to avoid ip conflicts.

But, about the DNS information in order to resolve internet names you have to write the ip addresses that the service provider gave you. Add an additional 006 scope option in DHCP and write the ISP DNS addresses. Configure your client machines to obtain DNS automatically.

About file sharing , simply install "File and printer sharing for Microsoft Networks" which is by default installed and just share the folders by right-clicking .

I have to ask you first , is this W2k3 server got two network cards? if so, then you will benefit from NATing for more security but the NAT is not the topic here i think and the topic is just to connect your clients to the internet and gain access to file sharing.

I wish this can help your issue.

Edited September 23, 2005 by Ahmed-26

[InTheWayBoy]

Also...is this just a DSL Modem, or a DSL Modem hooked up to a Router? In either case you'll want to make sure that you don't have conflicting services running...meaning, if your Modem/Router has a built-in DHCP server, you'll want to disable that before you install DHCP on the Server.

[BigDaddy]

Woav. Tanx, really appreciate the help! Will start working on it at once.

To clarify some questoins:

It's only aDSL modem hooked directly to NIC #1

The rest of LAN is connected to to onboard NIC.

First I'm goona try the easy route INTHEWAYROUTE. IF it works alright I am gonna switch 2 Domain Controller. But have little to no knowledge about it. Guess am gonna have to google it 2 find some good tutorial about it.And also what is ACTIVE DIRECTORY?

After I set this up I would also like to have FW. I was thinking about installing OUTPOST FW. Reccommendations??

I would also like to learn more about Nating. Have some basic knowledge about it. Learned it when setting up Winroute PRO

Edited September 24, 2005 by BigDaddy

[InTheWayBoy]

Active Directory is M$ term for their security/networking subsystem...some just call it AD. It's basically a big database that holds all the security and configurations for a whole network...or a domain as they call it. So you have one central 'thing' that controls most aspects of your network...this is good and bad. It good cause it's very effective and actually pretty easy to maintain. But it's bad because it's a whole new thing you'll need to learn, and when it breaks it's a pain to troubleshoot.