Forget DHCP. If Client require a specific IP# then statically assign them
and forget it.
The right way to do this would be to use a product like ISA Server that
controls access by *who* the user is rather than by what IP# they have.
If you have to do this with a Firewall Product that can only function based
on IP# then forget DHCP and statically assign the addresses. You could
create Reservations in DHCP but that is debatably as much or more work than
just staticaly assigning the addresses to begin with.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Microsoft Internet Security & Acceleration Server: Guidance
http://www.microsoft.com/isaserver/t...dance/2004.asp
http://www.microsoft.com/isaserver/t...dance/2000.asp
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Deployment Guidelines for ISA Server 2004 Enterprise Edition
http://www.microsoft.com/technet/pro...isaserver.mspx
-----------------------------------------------------
"B3NGL" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> I am trying to network 22 users, with some having email and internet
> access, some with email only acess and the rest with none of these....i
> was wondering how i can go about doin this?.....
> i was thinkin if i set 3 diferent DHCP Scope, with exclusion zone set
> to it...i can control (block certain ports)....but how do i control
> which computer gets which IP address...Mac address, but what happens
> when the user chnages computer.....can anyone help me with this
> issue....thank you
>
Similar Threads
Linear Mode
