Event ID 30015 — RRAS DHCP Relay Agent Enabling
Applies To: Windows Server 2008 R2
.jpg)
The DHCP Relay Agent is a Bootstrap Protocol (BOOTP) relay agent that relays Dynamic Host Configuration Protocol (DHCP) messages between DHCP clients and DHCP servers on different IP networks. For each IP network segment that contains DHCP clients, either a DHCP server or a computer acting as a DHCP Relay Agent must be enabled.
Event Details
| Product: | Windows Operating System |
| ID: | 30015 |
| Source: | Microsoft-Windows-RasIpBootp |
| Version: | 6.1 |
| Symbolic Name: | IPBOOTPLOG_EVENTSELECT_FAILED |
| Message: | IPBOOTP was unable to request notification of events on the socket for the local interface with IP address: %1. The data is the error code. |
Diagnose
This error might be caused by one of the following conditions:
- IPBOOTP failed. Check IPBOOTP while requesting notification of events on the socket.
- The DHCP relay router interface is not receiving packets. Use event logging to determine which interface and address failed.
You can use event logging to record remote access server errors, warnings, and other detailed information in the system event log.
To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
To configure event logging:
- Open Routing and Remote Access. Click Start, click Run, type rrasmgmt.msc, and then press ENTER.
- Right-click the server name for which you want to view properties, and then click Properties.
- Click the Logging tab, and then click Log all events.
- Retry the connection and then check the system event log for events logged during the connection process.
- See the sections titled "Check for low memory" and "Check the log files" for possible resolutions.
Resolve
To resolve this issue, use the resolution that corresponds to the cause you identified in the Diagnose section. After performing the resolution, see the Verify section to confirm that the feature is operating properly
Cause |
Resolution |
|---|---|
Various issues can affect DHCP Relay Agent |
Check memory status, restart Routing and Remote Access service, or restart computer |
Local interface parameters |
Check the log files |
Check memory status, restart Routing and Remote Access service, or restart computer
Possible resolutions:
- This computer might be low on memory. For more information, see the "Check memory usage on the server" section.
- Stop and restart the Routing and Remote Access service. For more information, see the "Restart the remote access service" section.
- Restart the computer.
To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.
Check memory usage on the server
To check memory usage on the remote access server:
- On the remote access server, click Start, click Run, type taskmgr, and then click OK.
- In the Windows Task Manager dialog box, click the Performance tab.
- Under Physical Memory, check the remote access server's memory usage.
- If necessary, free up available memory by ending non-essential applications or processes.
Restart the remote access service
To restart the remote access service:
- Open Routing and Remote Access. Click Start, click Run, type rrasmgmt.msc, and then press ENTER.
- By default, the local computer is listed as a server. To add another server, in the console tree, right-click Server Status, and then click Add Server. In the Add Server dialog box, click the appropriate option, and then click OK.
- In the console tree, right-click the server you want to restart, click All Tasks, and then click Restart.
Check the log files
Possible resolution:
- The logs might provide the reason for the failure. Review the Routing and Remote Access logs under \Windows\System32\LogFiles.
Verify
To verify that the DHCP Relay Agent is working:
From the router with the DHCP Relay Agent enabled, use the ping command to ping each of the DHCP servers that are configured in the DHCP Relay Agent dialog box on the remote access server.