Event ID 105 — Remote Desktop IP Virtualization IP Address Assignment

Published: January 8, 2010

Applies To: Windows Server 2008 R2

red

Remote Desktop IP Virtualization allows you to assign a unique IP address to a user session or on a per program basis. You must have a DHCP scope configured with enough IP addresses for all sessions or programs on an RD Session Host server.

Event Details

Product: Windows Operating System
ID: 105
Source: Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP
Version: 6.1
Symbolic Name: EVENT_ERROR_LEASESESSIONVIP
Message: Remote Desktop IP Virtualization could not acquire an IP address for session ID %1. Error code: %2

Resolve

Check connectivity to the DHCP server and ensure enough IP addresses are available

To resolve this issue, identify and fix any issues with your DHCP server by doing the following:

  • Determine if there is a network connectivity problem by using the ping command.
  • Ensure that enough IP addresses are available within the DHCP scope.
  • Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.

To perform these tasks, refer to the following sections.

Note:  The following procedures include steps for using the ping command to perform troubleshooting. Therefore, before performing these steps, check whether the firewall or Internet Protocol security (IPsec) settings on your network allow Internet Control Message Protocol (ICMP) traffic. ICMP is the TCP/IP protocol that is used by the ping command.

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

Determine if there is a network connectivity problem

To determine if there is a network connectivity problem between the RD Session Host server and the DHCP server:

  1. On the RD Session Host server, click Start, click Run, type cmd, and then click OK.
  2. At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the DHCP server (for example, server1.contoso.com), and then press ENTER.

    If the ping was successful, you will receive a reply similar to the following:

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=20ms TTL=59

    Reply from IP_address: bytes=32 time=3ms TTL=59

    Reply from IP_address: bytes=32 time=6ms TTL=59

  3. At the command prompt, type ping IP_address, where IP_address is the IP address of the DHCP server, and then press ENTER.

If you can successfully ping the DHCP server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.

If you cannot successfully ping the DHCP server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.

Ensure that enough IP addresses are available within the DHCP scope

To ensure that enough IP addresses are available within the DHCP scope:

  1. On the DHCP server, click Start, point to Administrative Tools, and then click DHCP.
  2. Expand the DHCP server, expand IPv4, and then click Address Leases.
  3. Ensure that the amount of DHCP leases does not exceed the amount of IP addresses available within the DHCP scope.

Perform additional troubleshooting steps

The following are some additional troubleshooting steps that you can perform to help identify the root cause of the problem:

  • Ensure that the DHCP server and the RD Session Host server are located on the same subnet.

Verify

To verify that an IP address has been assigned to a session or a specified program, you must use Event Viewer and confirm that Event 103 in the Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP event source was written to the System event log.

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To confirm that Event 103 was written to the System event log:

  1. On the RD Session Host server, open Event Viewer. To open Event Viewer, click Start, point to Administrative Tools, and then click Event Viewer.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Yes.
  3. In the left pane, expand Windows Logs, and then click System.
  4. Look for an event with a Source of Microsoft-Windows-TerminalServices-TSAppSrv-TSVIP and an Event ID of 103. This event indicates that an IP address was assigned to either a session or program.

Related Management Information

Remote Desktop IP Virtualization IP Address Assignment

Remote Desktop Services

Community Additions

ADD
Show: