• Status: Solved
  • Priority: High
  • Security: Public
  • Views: 52
  • Last Modified:

dhcp securing and controls

Dear Experts

We have DHCP server in the LAN please suggest on the following
1. would like to reserve few IP's to few users and we allow only those IP's to access the internal application web based server, please suggest the best practice considering the security controls for the dhcp,
2. is there a way that even though the wifi network password is known to the users still there should be one more level of authentication or some controls only if that is accepted then only  the users device gets IP assigned
please suggest, thanks.
  • 2
2 Solutions
nociSoftware EngineerCommented:
1)Security controls over DHCP are an illusion...
DHCP is driven by MAC address. A MAC address is initially equal to Hardware address of a chipset.
a) MAC addresses have duplicates as there are not enough address for all equipment.
b) MAC address are trivialy modified.
c) MAC address cannot be hidden.

2) No Wifi as such has no "extra" method.
You can choose to use IPSEC (L2TP) to connect from sensitive workstations to sensitive systems..
Andy BartkiewiczNetwork AnalystCommented:
I would recommend creating a new DHCP scope for privileged users, not reservations. If a password is known to the users, it's no security at all. I would recommend going to [WPA2][Auth(802.1X)] if you have the ability too. This would authenticate a user against AD, so everyone would have a unique username and password.
D_wathiAuthor Commented:
thanks noci and Andy Bartkiewicz, it is interesting to know  [WPA2][Auth(802.1X)] can you please explain how this works, think the firewall device/dhcp server device to be configured for AD, can you please list what all is needed to enable this, windows AD server please list the requirements in terms of hardware and software and few steps please
Andy BartkiewiczNetwork AnalystCommented:
[WPA2][Auth(802.1X)] uses a radius server to authenticate. There are several different options when it comes to radius servers, we use Network Policy Server, which comes with windows server. There are several methods of authentication, but we use PEAP. When the user authenticates, the radius server sends a certificate to the end user and the end user authenticates with either the user or computer ID/Password. This way both the radius server and the end user are authenticated.  AD can be configured with either a windows server (most common) or a Linux box. Users can be configured on AD, the radius server can either be part of the AD server, or it can be added to AD. So when an end user authenticates to AD the radius server checks AD to validate the credentials. If the credentials match, access is granted.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Cloud Class® Course: MCSA MCSE Windows Server 2012

This course teaches how to install and configure Windows Server 2012 R2.  It is the first step on your path to becoming a Microsoft Certified Solutions Expert (MCSE).

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now