Jump to content

Windows Server 2003 with domain controller and NAT


Recommended Posts

Hello all,

I am using Windows Server 2003 as a server with domain controller, DNS server and NAT. Also I do have 7 clients in the network with different OS's and set there connection to obtain an ip address and DNS server automatically. The problem is when clients connect to the network they get the right ip address and default gateway but I have to enter the dns server manually. What I need is when any client connect to my network cannot access unless they are a member in the domain or dial to the VPN and ever all IP's obtain automatically including the DNS server.

Any help would be much appreciated.

Link to comment
Share on other sites


This really isnt how DHCP works. Machines not connecting to the network unless they are authenticated is beyond the scope of DHCP and domain controllers. To accomplish this I believe you would have to set up 802.x authentication.

The DNS problem is easy you just have to set that option in the DHCP scope.

Link to comment
Share on other sites

Thank you for the responded; I am really sorry I was not clear enough. I attached Drawing of how the Network is setup

Yabeelaa_Network_Drawing.gif

What I need is when any client connects to the network automatically get the ip address, default gateway and the DNS server, no need for me to enter any thing. However, if the client is not a member in the domain controller they would not be able to use the network resources and when they try to use the browser and type any address they would be forward to an address in my IIS. And if the client is a member in the domain controller they would be able to use all network resources like internet and folders share in the server.

Link to comment
Share on other sites

DHCP Scope Classes should do what you want. Just setup one scope class with basic info and your IIS server as the gateway, and one class with the correct complete domain information. Assign all the domain machines to the domain scope class and you're there.

...DHCP Scope classes are usually used for braking up subnets...but there is no reason you can't use it for "Other Stuff"... :)

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...