DSL ROUTER & WINDOWS 2000 ACTIVE DIRECTORY

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

GOOD AFTERNOON,

I'M NEW TO W2K AND I WILL APRECIATE ANY HELP.

1.- WINDOWS 2000 SERVER(192.168.1.111)

2.- SPEEDSTREAM 5200 DSL ROUTER (192.168.1.254)
DHCP DISABLED

3.- WORKSTATIONS: (20)
STATIC IP (192.168.1.1...100)
GATEWAY: POINT TO THE ROUTER(192.168.1.254)
DNS: ISP DNS

WHAT I'M PLANNING TO DO IS THIS:

1.- CONFIGURE WINDOWS 2000 SERVER TO ACT AS A DOMAIN CONTROLLER & FILE SERVER.

2.- CONFIGURE W2K SERVER TO GIVE OR DENY ACCES TO INTERNET, FILES, SHARES,
INTERNET DOWNLOADS, SOFTWARE INSTALLATION, ETC.

MY QUESTIONS ARE:

1.- DO I NEED TO ADD ANOTHER NIC TO THE SERVER, AND THEN USE THAT NIC TO
CONNECT THE ROUTER?

IF I ADD A 2ND NIC, I NEED TO:

CHANGE THE DNS ON THE SERVER TO ISP DNS
CHANGE THE GATEWAY TO ROUTER IP
CHANGE THE WORKSTATIONS TO POINT TO THE W2K SERVER, SINCE THE ROUTER WILL BE
CONNECTED TO THE SECOND NIC ON THE SERVER.

CHANGE THE DNS ON THE WORKSTATION TO POINT TO THE SERVER

2.- HOW CAN I CONFIGURE W2K SERVER TO CONTROL INTERNET ACCESS IF THE ROUTER
WORK SEPARATELY FROM THE SERVER?

CAN YOU TELL ME IF I'M RIGHT OR IF THERE ARE ANOTHER EASY WAY TO DO THIS?

THANKS IN ADVANCE.

ABEL
 
Hi there

No need to write in capitals -- it's considered SHOUTING!

There is nothing in Windows 2000 Server that will enable you to control
access to the Internet at the level you describe. Microsoft ISA Server is a
product that has this capability, but I would definitely not recommend
installing it on a Windows 2000 Server domain controller.

You should look into purchasing Microsoft Small Business Server 2003
Premium. The Premium version contains ISA Server (for controlling Internet
access), Exchange (for e-mail), Sharepoint (for creating an Intranet and for
collaboration with Office 2003, if you have that) and acts as a Windows file
and print server. It's designed in the knowledge that people running IT in
small businesses are often not full-time IT professionals and so has wizards
to help you with common tasks.

For 20 clients, I would definitely look into SBS. If you decide to go this
route, the SBS enthusiasts live in the microsoft.public.windows.server.sbs
newsgroup.

For a regular Windows Active Directory deployment using Windows 2000 Server,
you should not add an extra NIC to the server. Also, in an Active Directory
deployment, you should not have your ISPs DNS address anywhere in a TCP/IP
settings of the server or any workstation. DNS misconfiguration is the
number one cause of Active Directory not running as expected and it pays to
understand DNS.

Run the Microsoft DNS service on your server and point the server to itself
for DNS resolution. Configure a forwarder in DNS to your ISP's DNS server.
That way, the DNS service on the server will forward queries to your ISP as
appropriate.

Once you've used dcpromo to create the new domain, I would switch the domain
to use Active Directory-integrated DNS.

Hope this helps

Oli
 
Back
Top