2 Common Issues With Microsoft Terminal Services

Many WAN connections can vary in quality and latency, and often times these two characteristics will manifest themselves in disconnected terminal services sessions. By doing two relatively easy registry hacks, you can reduce these disconnects and improve the overall experience of your users.

 

Keep Alives:

In the registry at HKLM\SYSTEM\CurrentControlSet\Control\Terminal Server, create or edit the DWORD value of KeepAliveEnable and set it to 1. This will turn Keep Alives on. This will serve to stabilize the connection by sending ‘heartbeat’ packets to the client every so often. This will cause an idle connection to be probed every so often just to be sure that the connection is still alive and that the client is still listening on the other side. This will also help prevent disconnects by preventing network devices from killing off sockets that it assumes to be idle.  By turning on Keep Alives, the connection will not appear idle, and therefore the network device will not attempt to terminate the socket.

Two other registry entries to look at are at HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveInterval and HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\KeepAliveTime.  KeepAliveInterval determines the interval separating keep alive retransmissions until a response is received. If a response is received, the delay until the next keep alive transmission is again controlled by the value of KeepAliveTime. KeepAliveTime controls how often TCP attempts to verify that an idle connection is still intact by sending a keep alive packet. If the remote system is still reachable and functioning, it will acknowledge the keep alive transmission.

 

TcpMaxDataRetransmissions:

In the registry at HKLM\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters, create or edit the DWORD value of TcpMaxDataRetransmissions. By default it is set to 5, but I would recommend doubling that value, to 10.  The value of TcpMaxDataRetransmissions is the number of times TCP retransmits an unacknowledged data segment on an existing connection. TCP retransmits data segments until they are acknowledged or until this value expires.

 

Enjoy..

[Solved]-Remote Web Workplace will not connect to my computer.

You have a user that has a  Home  (Windows 7 Home) or Work (Windows 7 Pro) Computer

When using remote web workplace they selects connect to my computer, picks their computer from the list and then it never makes it past this point. There is a error icon displayed in the lower progress bar area of the browser.

Running IE as a administrator they are able to use RWW just fine.

The user is an administrator on the computer. IE9 has been removed and replaced with IE8 same results.

Windows firewall is off,  We have tried with the firewall on and off, makes no difference.  We have added RWW site to the trusted site and relaxed all the active security settings for the trusted site, same result. The browser add-ons show the Microsoft rdp active control is installed when in IE both as an admin and just launching it normally so what could be hanging us up?

Well you will find that your UAC is on and one of the results of this being active is that Active X functions are suppressed. Just turn off UAC and the problem will go away.

Go to your start button and in the search window type “UAC”. It will launch the UAC Control and allow you to change the settings

Enjoy

Cubert.