Share via

Event ID 20169 — RRAS IPCP Negotiation

  • Article

Applies To: Windows Server 2008 R2

The virtual private networking (VPN) server must have IP addresses available to assign them to the VPN server's virtual interface and to VPN clients during the IP Control Protocol (IPCP) negotiation phase of the connection process. The IP address assigned to the VPN client is assigned to the virtual interface of the VPN client. Routing and Remote Access can be configured to use a DHCP server to obtain IP addresses or it can use a static pool of IP addresses to assign to remote access and demand-dial connections.

Event Details

Product: Windows Operating System
ID: 20169
Source: RemoteAccess
Version: 6.1
Symbolic Name: ROUTERLOG_AUTONET_ADDRESS
Message: Unable to contact a DHCP server. The Automatic Private IP Address (APIPA): %1 will be assigned to dial-in clients. Clients may be unable to access resources on the network.

Resolve

Check the DHCP server configuration

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Follow the procedures in the order in which they appear until the problem is resolved.

Check the adapter for the DHCP server

To check the adapter for the DHCP server:

  1. Open Routing and Remote Access. Click Start, click Run, type rrasmgmt.msc, and then press ENTER.
  2. In the console tree, right-click the server name, and then click Properties.
  3. On the IPv4 tab, check that the adapter selected is the correct one to receive IP addresses from the DHCP server.

Check the static address pool

To check the static address pool:

  1. Open Routing and Remote Access. Click Start, click Run, type rrasmgmt.msc, and then press ENTER.
  2. Right-click the server name for which you want to create a static IP address pool, and then click Properties.
  3. On the IPv4 tab, select an address pool, and then click Edit.
  4. Check the range of IP addresses.

Note:   If the static IP address pool consists of ranges of IP addresses that are for a separate subnet, then you must either enable an IP routing protocol on the remote access server computer or add static IP routes consisting of the {IP Address, Mask} of each range to the routers of the intranet. If the routes are not added, then remote access clients cannot receive traffic from resources on the intranet.

Verify

To verify that the remote access server can accept connections, establish a remote access connection from a client computer.

To create a VPN connection:

  1. Click Start, and then click Control Panel.
  2. Click Network and Internet, click Network and Sharing Center, and then click Set up a connection or network.
  3. Click Connect to a workplace, and then click Next.
  4. Complete the steps in the Connect to a Workplace wizard.

To connect to a remote access server:

  1. In Network and Sharing Center, click Manage network connections.
  2. Double-click the VPN connection, and then click Connect.
  3. Verify that the connection was established successfully.

 

RRAS IPCP Negotiation

Routing and Remote Access Service Infrastructure