DHCP and VLANs

I'm currently in college and we are setting up a network to experiment with.
I was wondering if there was a way to set DHCP on our server so that it
either corrosponds with a port number on the switch or the VLAN number. So I
have the 10.3.x.x /16 network and I want to make all the clients on VLAN 2 to
use 10.3.2.x scope, clients on VLAN 3 to use 10.3.3.x scope and so on. I have
all my scopes setup and now I'm to the point where I either have to go in and
figure out how to set the switch up to handle this or set up Server 2003 to
handle this. The problem is I'm not real sure on how to accomplish this. I'm
going to graduate this spring and I've had Cisco classes 1-6 and a Microsoft
Server 2003 class. Sadly my Server 2003 class had a teacher that really
didn't know much other then the basic set up users, the AD, and basic DHCP,
DNS. I've read some other posts that people are trying to do similar things
but it's just not the same.

I'm sure I have the resources to accomplish this I just need a push in the
right direction. I'm want to do it like this way so that when we setup ACLs
and put up the firewall, that it will be easier to monitor and restrict
access.

Also if anyone out there has just some basic tips on security (I'm in the
middle of my security class now and haven't learned all that much) I'd
appreciate it.

Thank you for your time!!!!

Josh

Phillip
Thu Jan 27 09:55:18 CST 2005

It doesn't matter where the DHCP is as long as you have functioning
connectivity to it. It is the responsibility of the Router between the
networks to forward the DHCP Queries to the DHCP Server so only the Router
needs to "know" where the DHCP Server is.

On the DHCP Server it is extremely simple,...you just create a separate
independent Scope for each subnet used,..that's it,...you're done with the
DHCP config. (No superscopes!!, forget it, don't even ask)

The fact that you use VLANs does not matter, it all works the same way no
matter if it is VLANs or regular "LANs".

The Router is the key to everything and you never even mentioned having one.
Switches can divide up thier ports into different VLANs, but they can *not*
make a VLAN work. Only the Router can do that. The Router is the "heart" of
the whole thing,..including the DHCP setup.

Don't worry about Firewalls until you have a properly fuctioning system to
put one on. Firewalls are "edge" devices that connect it to the Internet and
should not have any effect on the actual functionality of the LAN itself.
--

Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com


"Josh" <Josh@discussions.microsoft.com> wrote in message
news:527085E2-AAFA-4248-9837-D4F16314A135@microsoft.com...
> I'm currently in college and we are setting up a network to experiment
with.
> I was wondering if there was a way to set DHCP on our server so that it
> either corrosponds with a port number on the switch or the VLAN number. So
I
> have the 10.3.x.x /16 network and I want to make all the clients on VLAN 2
to
> use 10.3.2.x scope, clients on VLAN 3 to use 10.3.3.x scope and so on. I
have
> all my scopes setup and now I'm to the point where I either have to go in
and
> figure out how to set the switch up to handle this or set up Server 2003
to
> handle this. The problem is I'm not real sure on how to accomplish this.
I'm
> going to graduate this spring and I've had Cisco classes 1-6 and a
Microsoft
> Server 2003 class. Sadly my Server 2003 class had a teacher that really
> didn't know much other then the basic set up users, the AD, and basic
DHCP,
> DNS. I've read some other posts that people are trying to do similar
things
> but it's just not the same.
>
> I'm sure I have the resources to accomplish this I just need a push in the
> right direction. I'm want to do it like this way so that when we setup
ACLs
> and put up the firewall, that it will be easier to monitor and restrict
> access.
>
> Also if anyone out there has just some basic tips on security (I'm in the
> middle of my security class now and haven't learned all that much) I'd
> appreciate it.
>
> Thank you for your time!!!!
>
> Josh