Environment: Windows NT 4.0 SP 6a
Running DHCP on a very limited scale: using static addresses for critical systems that require monitoring and/or remote control.
I’ve recently been presented with the task of completely redesigning our network of 13 locations scattered across two states. All the machines are currently assigned static IP addresses (mainly due to remote monitoring and support needs).
Is there a way to use DHCP to assign addresses from a table? For example, I want to assign the PC ‘Branch1President’ to 10.0.0.100, the PC ‘SysAdmin’ to 10.0.0.68, the machine ‘RouterA’ 10.0.0.1, and all the other machines in the network in a similiar fashion. For security reasons, I also want to specify that if a machine attempts to get a DHCP request that ISN’T identified in this table I’ve created, it is denied an address (basically for security reasons — A rogue janitor plugging in a laptop wouldn’t be given an IP address that would allow connections). I’d also like to log these entries so when a machine logs in and gets an address, the MAC, username and the date/time of login/logout).
Am I asking too much? I really hate to drive all over the states reassigning the network addresses if I can get around it.
Also, we are evertually going to a Windows 2000 advanced server environment, so tips on doing it in that OS would be very helpful.
Can DHCP requests pass through my Cisco 1720, or can I enable the DHCP on both sides to do what I’m attempting?
Becauseof the scope of these questions, I’ve assigned a very high point value to this question (IMHO).
Thank you in advance for your responses.