Remote Desktop Connection to SBS 2003 with ISA 2004

External Since: Jan 29, 2009 Posts: 1

Hello: Until a week ago, RDC was working properly, connecting to SBS 2003
R2
server desktop. It has now stopped working. I get the Remote Desktop
Disconnected dialog,
saying "This Computer can't connect to the remote computer. Try connecting
again ... etc."

I can see the connection attempts in the ISA 2004 Standard Edition
Monitoring>Logging window. The connect/disconnect info is as follows:

Initiated Connection TESTSBS
1/28/2009 5:18:48 PM
Log type: Firewall service
Status: The operation completed successfully.
Rule: Allow remote management from selected computers using Terminal Server
Source: External ( XX.XX.170.146:2439)
Destination: Local Host ( XX.XX.174.78:3389)
Protocol: RDP (Terminal Services)
User:
Additional information
Number of bytes sent: 0 Number of bytes received: 0
Processing time: 0ms Original Client IP: XX.XX.170.146
Client agent:

Closed Connection TESTSBS 1/28/2009
5:18:48 PM
Log type: Firewall service
Status: A connection was abortively closed after one of the peers sent a RST
segment.
Rule: Allow remote management from selected computers using Terminal Server
Source: External ( XX.XX.170.146:2439)
Destination: Local Host ( XX.XX.174.78:3389)
Protocol: RDP (Terminal Services)
User:
Additional information
Number of bytes sent: 215 Number of bytes received: 187
Processing time: 0ms Original Client IP: XX.XX.170.146
Client agent:

Using Remote Web Workplace, I can connect to the desktop of any client of
SBS 2003, but not the server desktop. If anyone can point me to an
exhaustive checklist
to follow in solving this challenge, it would be appreciated.

External Since: Jan 30, 2009 Posts: 3

Dear Customer,

Thank you for posting in newsgroup.

According to the research, here is a checklist just for your reference.

Checklist:
==================

1. Please check the TCP port 3389 is not blocked by any firewall between
the problematic client and the SBS serve. You may telnet to internal IP of
the SBS server from the problematic client to see if the TCP port 3389 can
be connected.

Telnet IPaddressofSBS 3389

2. Please check if the TCP port 3389 is in the status of LISTENING on the
SBS server.

Netstat -nao

3. Please find another client and logon it with the same credential to see
if you can terminal to the SBS server via RDC.

4. if the issue still exist on the other client, please check that the
registry keys are configured with following on the SBS server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Disabl
eTaskOffload and set it to 1.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Enable
RSS and set it to 0.

5. Please install the utility "devcon" on the problematic windows XP client
from

http://support.microsoft.com/default.aspx?scid=kb;en-us;311272

6. After unzipping the file, reinstalled the Terminal Server Device
Redirector by executing the following command from the CMD Prompt:

devcon -r install %windir%\inf\machine.inf root\rdpdr

7. Please reboot both the SBS server and the problematic client to test if
the issue still exists.

Please tell me the result and hope it helps.

David Shen
Microsoft Online Technical Support