General discussion

Locked

Lock client to a specific DHCP Server

By noelamo ·
I would like to lock down all the clients to a specific DHCP server. I know there is a registry entry for DHCPnameserverlist. I want to lock this list down.

Any Help and guidance will be of Help

This conversation is currently closed to new comments.

1 total post (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Registry Entry

by BFilmFan In reply to Lock client to a specific ...

The entry you are speaking of in your message is for WINS. It stores a list of IP addresses of Windows Internet Name Service (WINS) servers, as provided by the Dynamic Host Configuration Protocol (DHCP) service.

The whole entry is HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\Interfaces\interface-name.

Windows NT 4.0 had the entry DHCPnameserver and DHCPNameServerbackup. These no longer exist in Windows 2003.

You can read more about it here:
http://www.microsoft.com/resources/documentation/WindowsServ/2003/all/deployguide/en-us/Default.asp?url=/resources/documentation/WindowsServ/2003/all/deployguide/en-us/242708.asp

If you want all the clients to get addresses from a single DHCP server, then configure the scopes only on that DHCP server. This isn't a recommended best practice as in the event that DHCP fails, clients will not recieve addreses.

With Active Directory, if your DHCP servers are all Microsoft based systems, then they will have to be authorized. This will prevent anyone from accidentally setting up their own Microsoft DHCP server. It won't prevent some other OS or hardware device from handing out DHCP addresses.

What issue are you experiencing that is causing you to seek the locking down of clients to a specific DHCP server?

Back to IT Employment Forum
1 total post (Page 1 of 1)  

Related Discussions

Related Forums