DHCP: Port 68 (DHCP Client port for IPv4) should not be used by any other process while rogue detection is enabled

Updated: February 15, 2010

Applies To: Windows Server 2008 R2, Windows Server 2012

This topic is intended to address a specific issue identified by a Best Practices Analyzer scan. You should apply the information in this topic only to computers that have had the Dynamic Host Configuration Protocol Best Practices Analyzer run against them and are experiencing the issue addressed by this topic. For more information about best practices and scans, see Best Practices Analyzer (http://go.microsoft.com/fwlink/?LinkId=122786).

 

Operating System

Windows Server 2008 R2, Windows Server 2012

Product/Feature

Dynamic Host Configuration Protocol (DHCP)

Severity

Error

Category

Prerequisite

Port 68 is in use another by process

If port 68 is in use by another process, DHCP server cannot perform rogue DHCP server detection in IPv4.

Stop the process that is using port 68 or configure this process to use a port other than 68.

DHCP uses UDP ports 67 and 68 to initiate communication between the client and server. If either of these ports is in use by another application, or the ports are otherwise reserved, DHCP will not function. You can use Windows Firewall with Advanced Security (WFAS) with the following procedure to reassign ports so that DHCP can use port 68.

To perform this procedure, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

  1. Click Start, click Administrative tools, and then click Windows Firewall with Advanced Security.

  2. Click Inbound rules.

  3. In the Local Port column, right-click 68 and then click Properties.

  4. Click Protocols and Port, specify a port other than 68 in Local Port, and then click OK.

  5. Click Action, click New Rule…, and then click Predefined.

  6. Click DHCP Server, check all of the DHCP rules, click Next and then click Finish.

For updated detailed IT pro information about DHCP, see the Windows Server 2008 R2 documentation on the Microsoft TechNet Web site.

Community Additions

ADD
Show: