Event ID 1000 — RemoteApp and Desktop Connection Configuration
Applies To: Windows Server 2008 R2
RemoteApp and Desktop Connection is configured by using the Control Panel.
|Product:||Windows Operating System|
|Source:||Microsoft-Windows-RemoteApp and Desktop Connections|
|Message:||An error occurred. Contact your workplace administrator for assistance.
Connection name: %1
Connection URL: %2
Error code: %3, %4
Identify and fix configuration issues with Remote Desktop Web Access
To resolve this issue, do the following things:
- If you are using an RD Connection Broker server, you must ensure that the RD Connection Broker server is available on the network.
- If you are using one or more RemoteApp sources, you should ensure that the RemoteApp source name is correct.
To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.
Ensure that the RD Connection Broker server is available on the network
The following are some troubleshooting steps that you can perform to help identify the root cause of the problem:
- Ping other computers on the network to help determine the extent of the network connectivity issue.
- If you can ping other servers but not the domain controller, try to ping the RemoteApp source server from another computer. If you cannot ping the RD Connection Broker server from any computer, first ensure that the RD Connection Broker server is running. If the RD Connection Broker server is running, check the network settings on the RD Connection Broker server.
- Check the TCP/IP settings on the local computer by doing the following:
- Click Start, click Run, type cmd, and then click OK.
- At the command prompt, type ipconfig /all, and then press ENTER. Make sure that the information listed is correct.
- Type ping localhost to verify that TCP/IP is installed and correctly configured on the local computer. If the ping is unsuccessful, this may indicate a corrupt TCP/IP stack or a problem with your network adapter.
- Type ping *IP_address, where *IP_address is the IP address assigned to the computer. If you can ping the localhost address but not the local address, there may be an issue with the routing table or with the network adapter driver.
- Type ping *DNS_server, where *DNS_server is the IP address assigned to the DNS server. If there is more than one DNS server on your network, you should ping each one. If you cannot ping the DNS servers, this indicates a potential problem with the DNS servers, or with the network between the computer and the DNS servers.
- If the RD Connection Broker server is on a different subnet, try to ping the default gateway. If you cannot ping the default gateway, this might indicate a problem with the network adapter, the router or gateway device, cabling, or other connectivity hardware.
- In Device Manager, check the status of the network adapter. To open Device Manager, click Start, click Run, type devmgmt.msc, and then click OK.
- Check network connectivity indicator lights on the computer and at the hub or router. Check network cabling.
- Check firewall settings by using the Windows Firewall with Advanced Security snap-in.
- Check IPsec settings by using the IP Security Policy Management snap-in.
Ensure that the RemoteApp source name is correct
You can ensure that the RemoteApp source name is correct by using Remote Desktop Web Access Configuration.
To ensure that the RemoteApp source name is correct:
- On the RD Web Access server, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Configuration.
- Enter the appropriate user name and password.
- Click Configuration.
- In the Source name box, ensure that the RemoteApp source name represents a NETBIOS name or fully qualified domain name of the RemoteApp source. If you are using more than one RemoteApp source, ensure that each source name is separated with a semicolon.
To verify that RemoteApp and Desktop Connection is configured correctly, you should start a RemoteApp program that is published by using RemoteApp and Desktop Connection.
To start a RemoteApp program that is published by using RemoteApp and Desktop Connection:
- On a client computer, click Start, point to All Programs, point to RemoteApp and Desktop Connections, point to Enterprise Remote Access, and then click a RemoteApp program.
- Verify that the RemoteApp program opens successfully.