Security

Ask something
Discussion Locked

auditing DHCP

0 helpful
2 replies

by lindamabry

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
We are a fairly open university campus, and would like to implement DHCP on a more universal basis. The issue we are having trouble with is being able to identify machines and their locations in the event of a problem. Like any higher ed facility,we get students trying to go where they don't belong, and occasionally an outsider slipping in with a handy laptop. We need to secure against the latter, and be able to trace the former. Does anyone have any experience with this? Ideas? Thanks!

2 replies

by tomsal

Since obviously you can trace through IP numbers in a DHCP setting, because the numbers aren't static - I'd suggest going the route of a standardized naming convention to be used with the NETBIOS name of the machine, then lock out the GUI so users can't change/delete/modify the NETBIOS name of the workstation.

There are tools that do this, you can do this also if you are good with registry editing, otherwise look at system policies (NT environment) or tools like TWEAKUI to not allow users tochange the Netbios or TCP/IP settings.

This is a suggestion however, since I use a more involved way of tracking my clients - I track by NETBIOS, STATIC IP ADDRESSES, MAC ADDRESS AND S/N of the software the machines run. This info is stored in a self updating inventory control program that audits the machine at boot up (with the help of an NT login script). The system works well for my needs.

by ntr9217

In our school one has to use his/her school username and password in order to register a machine with the school's DHCP server. This has to be done at the beginning of each academic year.

Depending on the subnet the machine is on, you can locate it. I don't know how they implement this, but I thought you might be interested to know.

This discussion is closed to new replies.