The DHCP allocator component of Network Address Translation (NAT) protocol encountered an error.
The most common reasons for this error are:
The DHCP allocator has failed to check whether the IP address is in use on the network. The most common reason for this failure is the allocator failed to get the address resolution for the IP address on the network.
There was a socket operation failure.
The DHCP allocator has detected a DHCP server on the network.
The DHCP allocator has encountered a network error while attempting to reply to a client's request.
The DHCP allocator has detected Network Address Translation (NAT) enabled on the interface.
The DHCP allocator has disabled itself as its IP address is outside the scope from which addresses are being allocated to DHCP clients.
Sample Event#1: The DHCP allocator was unable to check whether the IP address %1is in use on the network for local IP address %2.This error may indicate lack of support for address-resolution on thenetwork, or an error condition on the local machine.The data is the error code.
Sample Event#2: The DHCP allocator was unable to bind to the IP address %1.This error may indicate a problem with TCP/IP networking.The data is the error code.
Sample Event#3: The DHCP allocator has detected a DHCP server with IP address %1on the same network as the interface with IP address %2.The allocator has disabled itself on the interface in order to avoidconfusing DHCP clients.
Sample Event#4: The DHCP allocator encountered a network error while attempting to replyon IP address %1 to a request from a client.The data is the error code.
Sample Event#5: The DHCP allocator detected network address translation (NAT) enabledon the interface with index ''%1''.The allocator has disabled itself on the interface in order to avoidconfusing DHCP clients.
Sample Event#6: The DHCP allocator has disabled itself on IP address %1,since the IP address is outside the %2/%3 scopefrom which addresses are being allocated to DHCP clients.To enable the DHCP allocator on this IP address,please change the scope to include the IP address,or change the IP address to fall within the scope.
If the server is low on memory, take appropriate action to increase the available memory. See Help and Support Center for information on low memory.
Verify the network connectivity between the client and the NAT server.
Reconfigure the scope from which the addresses are being allocated to DHCP clients to include the IP address of NAT server.
Stop and restart the Routing and Remote Access service.
If the problem persists, restart the server.
Microsoft Corporation, all rights reserved
Target | Microsoft.Windows.RemoteAccess.VPNServer.Class |
Category | EventCollection |
Enabled | False |
Alert Generate | False |
Remotable | True |
Event Log | System |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
DS | DataSource | Microsoft.Windows.EventProvider | Default |
WriteToDB | WriteAction | Microsoft.SystemCenter.CollectEvent | Default |