Event Id | 20166 |
Source | RemoteAccess |
Description | A connection has been established on port: %1 using interface: %2, but the remote side did not obtain an IP address. |
Event Information | According to Microsoft : Cause : This event is logged when a connection has been established on port using interface, but the remote side did not obtain an IP address. Resolution : Check whether DHCP or remote access servers have enough IP addresses to allocate to clients If the remote access server is configured to allocate IP addresses from a DHCP server, make sure that the DHCP server is accessible and has enough IP addresses to allocate. If the remote access server is configured to allocate IP addresses itself with a static IP address pool, confirm that there are enough addresses in the pool. If all of the addresses in the static pool have been allocated to connected remote access clients, then the remote access server cannot allocate an IP address. If the remote access client is configured only to use TCP/IP as a LAN protocol, the connection attempt is denied. To check the static IP address pool for the availability of addresses:
To verify that the remote access server can accept connections, establish a remote access connection from a client computer. To create a VPN connection:
|
Reference Links | Event ID 20166 from RemoteAccess |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.