| Event Information | According to Microsoft :
Cause :
This event is logged when no programs were detected.
Resolution :
Ensure that the server is configured as a terminal server and that the server is available on the network
To resolve this issue, do the following:- Determine the terminal server that the TS Web Access server is configured to use.
- Ensure that the server specified is configured as a terminal server.
Identify and fix any network connectivity problems between the TS Web Access server and the terminal server.
To perform these tasks, refer to the following sections.
Determine the terminal server that the TS Web Access server is configured to use
To perform this procedure, you must be logged on with the local Administrator account or have membership in the local TS Web Access Administrators group on the TS Web Access server.
To determine the terminal server that TS Web Access is configured to use:- Connect to the TS Web Access Web site. To do this, use either of the following methods:
- On the TS Web Access server, click Start, point to Administrative Tools, point to Terminal Services, and then click TS Web Access Administration.
- Use Internet Explorer to connect to the TS Web Access Web site. By default, the Web site is located at http://server_name/ts, where server_name is the name of the TS Web Access server.
- Log on to the site by using either the local Administrator account, or an account that is a member of the local TS Web Access Administrators group. If you are already logged on to the computer as one of these accounts, you are not prompted for credentials.
- On the title bar, click the Configuration tab.
Note : If you access the TS Web Access Web site by using the TS Web Access Administration option, the page automatically opens to the Configuration tab. - In the Editor Zone area, in the Terminal server name box, the name of the terminal server that TS Web Access is configured to use as the data source is listed.
Ensure that the server specified is configured as a terminal server
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To check that the server is configured as a terminal server:- On the server, open Server Manager. To open Server Manager, click Start, point to Administrative Tools, and then click Server Manager.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the left pane, expand Roles. If listed, click Terminal Services. If Terminal Services is not listed, the server is not configured as a terminal server.
- Under Role Services, the status of Terminal Server should be listed as Installed. If the status is listed as Not installed, the server is not configured as a terminal server.
- If the server is not configured as a terminal server, do either of the following:
- Add (install) the Terminal Server role service onto the server.
- Configure TS Web Access to use another server that is already configured as a terminal server. To configure TS Web Acesss to use a different terminal server, navigate to the Configuration tab of the TS Web Access Web site. In the Editor Zone area, in the Terminal server name box, type the name of the terminal server, and then click Apply.
Identify and fix any network connectivity problems
To identify and fix any network connectivity problems between the TS Web Access server and the terminal server, do the following:- Determine if there is a network connectivity problem by using the ping command.
- Perform additional troubleshooting steps, if necessary, to help identify the cause of the problem.
To perform these tasks, refer to the following sections.
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 TS Web Access server and the terminal server:- On the TS Web Access server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type ping server_FQDN, where server_FQDN is the fully qualified domain name (FQDN) of the terminal server, 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 - At the command prompt, type ping IP_address, where IP_address is the IP address of the terminal server, and then press ENTER.
If you can successfully ping the terminal server by IP address, but not by FQDN, this indicates a possible issue with DNS host name resolution.
If you cannot successfully ping the terminal server by IP address, this indicates a possible issue with network connectivity, firewall configuration, or IPsec configuration.
Perform additional troubleshooting steps
The following are some additional 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 terminal server, try to ping the terminal server from another computer. If you cannot ping the terminal server from any computer, first ensure that the terminal server is running. If the terminal server is running, check the network settings on the terminal 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 terminal 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.
|