| Event Information | According to Microsoft :
Cause :
This event is logged when terminal Server listener stack was down.
Resolution :
Restart the listener or increase available system resources
To resolve this issue, attempt to restart the listener on the terminal server. If restarting the listener is not successful, attempt to increase available system resources, such as memory, on the terminal server.
To perform these tasks, refer to the following sections.
Restart the listener
To restart the listener, use either of the following methods on the terminal server.
To perform these procedures, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Method one
To stop and start the Terminal Services service:- On the terminal server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the Services pane, right-click Terminal Services, and then click Restart.
- If you are prompted about restarting other services, click Yes.
- Confirm that the Status column for the Terminal Services service displays Started.
Method two
To disable and enable Remote Connections:- On the terminal server, start the System tool. To start the System tool, click Start, click Run, type control system and then click OK.
- Under Tasks, click Remote settings.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- In the System Properties dialog box, on the Remote tab, select the Don't allow connections to this computer option, and then click Apply.
- In the System Properties dialog box, select either of the following, depending on your environment:
- Allow connections from computers running any version of Remote Desktop (less secure)
- Allow connections only from computers running Remote Desktop with Network Level Authentication (more secure)
- Click OK to close the System Properties dialog box.
Increase available system resources
One way to increase the amount of available memory is to determine if there are any programs or processes running on the terminal server that can be closed. Use Task Manager to determine which processes are using the most memory, and to end those processes.
To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
To free up memory on the terminal server by using Task Manager:- On the terminal server, right-click an empty area of the taskbar, and then click Task Manager.
- Click the Processes tab.
- Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, on the View menu, click Select Columns, select the User Name and the Memory (Private Working Set) check boxes, and then click OK.
- At the bottom of the tab, select the Show processes from all users check box.
- If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
- To sort the processes by memory usage, click the Memory (Private Working Set) column header.
- Determine if you can end any of the memory-intensive processes.
- To end a process, click the process name, and then click End Process.
- Click End Process to confirm that you want to end the process.
If you cannot free memory by using Task Manager, or if this issue still occurs after you try to free up memory, restart the terminal server.
Verify :
To verify that the listener on the terminal server is working properly, use any of the following methods.
Note : RDP-TCP is the default connection name and 3389 is the default RDP port. Use the connection name and port number specific to your terminal server configuration.
Method one : Use an RDP client, such as Remote Desktop Connection, to establish a remote connection to the terminal server.
Method two :To use the qwinsta tool to view the listener status on the terminal server:- On the terminal server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type qwinsta and then press ENTER.
- The RDP-TCP session state should be Listen.
Method three :To use the netstat tool to view the listener status on the terminal server:- On the terminal server, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type netstat -a and then press ENTER.
- The entry for TCP port 3389 should be Listening.
Method four :To use the telnet tool to connect to the RDP port on the terminal server:- From another computer, click Start, click Run, type cmd, and then click OK.
- At the command prompt, type telnet servername 3389, where servername is the name of the terminal server, and then press ENTER.
If telnet is successful, you will receive the telnet screen and a cursor.
If telnet is not successful, you will receive this error:
Connecting To servername...Could not open connection to the host, on port 3389: Connect failed
The qwinsta, netstat, and telnet tools are also included in Windows XP and Windows Server 2003. You can also download and use other troubleshooting tools, such as Portqry. |