RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

[SPC]

RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Has anyone else experienced the following problem with a Remote Desktop
Connection to a Windows Server 2003 SE SP2 with all current High Priority
and Optional updates applied? Any suggestions?

The following is displayed in a critical error pop-up dialog box:

Remote Desktop Disconnected

This computer can't connect to the remote computer.

The connection was lost due to a network error. Try connecting again.
If the problem continues, contact your network administrator or technical
support.

The error occurs regardless if the connection is attempted remotely from a
Windows XP/Vista workstation or even locally through the loopback
interface.

The checkbox for "Enable Remote Desktop on this computer" has been selected
in the System Properties, Remote tab.

Netstat -anb indicates the following:

TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 2944

tasklist /FI "PID eq 2944" indicates the following:

Image Name PID Session
Name Session# Mem Usage
========================= ======== ================ ===========
============
svchost.exe 2944 Console
0 4,468 K

Windows Defender, Software Explorer tool indicates the following:

Microsoft Generic Host Process for Win32 Services
File Name: svchost.exe
Display Name: Microsoft Generic Host Process for Win32 Services
Description: Generic Host Process for Win32 Services
Publisher: Microsoft Corporation
Digitally Signed By: Microsoft Windows Verification Intermediate PCA
File Type: Application
Auto Start: No
File Path: C:\WINDOWS\System32\svchost.exe
File Size: 14848
File Version: 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
Date Installed: 2/17/2007 10:04:01 AM
Process ID: 2944
User Name: NT AUTHORITY\SYSTEM
Services: Terminal Services
Classification: Permitted
Ships with Operating System: Yes

The Terminal Services service is executed as follows:

C:\WINDOWS\System32\svchost.exe -k termsvcs

The Terminal Services Manager displays "The protocol is currently enabled"
for the RDP-Tcp (listener).

A TCP connection with Telnet to port 3389 succeeds. An RDP session back to
the XP/Vista workstation succeeds. No Event Viewer messages are logged.

TIA

 

[Jeff Loo]

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Ensure that you have a terminal services license server online and
configured with available and matching User or Device CAL's in Terminal
Services Configuration. Configure the terminal server to point to the same
TS licensing server if automatic doesn't find it or if it is on a different
subnet.


"SPC" <sig52@hotmail.com> wrote in message
news:OOI5NBmJJHA.1160@TK2MSFTNGP04.phx.gbl...
> Has anyone else experienced the following problem with a Remote Desktop
> Connection to a Windows Server 2003 SE SP2 with all current High Priority
> and Optional updates applied? Any suggestions?
>
> The following is displayed in a critical error pop-up dialog box:
>
> Remote Desktop Disconnected
>
> This computer can't connect to the remote computer.
>
> The connection was lost due to a network error. Try connecting again.
> If the problem continues, contact your network administrator or
> technical support.
>
> The error occurs regardless if the connection is attempted remotely from a
> Windows XP/Vista workstation or even locally through the loopback
> interface.
>
> The checkbox for "Enable Remote Desktop on this computer" has been
> selected in the System Properties, Remote tab.
>
> Netstat -anb indicates the following:
>
> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING
> 2944
>
> tasklist /FI "PID eq 2944" indicates the following:
>
> Image Name PID Session
> Name Session# Mem Usage
> ========================= ======== ================ ===========
> ============
> svchost.exe 2944
> Console 0 4,468 K
>
> Windows Defender, Software Explorer tool indicates the following:
>
> Microsoft Generic Host Process for Win32 Services
> File Name: svchost.exe
> Display Name: Microsoft Generic Host Process for Win32 Services
> Description: Generic Host Process for Win32 Services
> Publisher: Microsoft Corporation
> Digitally Signed By: Microsoft Windows Verification Intermediate PCA
> File Type: Application
> Auto Start: No
> File Path: C:\WINDOWS\System32\svchost.exe
> File Size: 14848
> File Version: 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
> Date Installed: 2/17/2007 10:04:01 AM
> Process ID: 2944
> User Name: NT AUTHORITY\SYSTEM
> Services: Terminal Services
> Classification: Permitted
> Ships with Operating System: Yes
>
> The Terminal Services service is executed as follows:
>
> C:\WINDOWS\System32\svchost.exe -k termsvcs
>
> The Terminal Services Manager displays "The protocol is currently enabled"
> for the RDP-Tcp (listener).
>
> A TCP connection with Telnet to port 3389 succeeds. An RDP session back
> to the XP/Vista workstation succeeds. No Event Viewer messages are
> logged.
>
> TIA
>
>

 

[SPC]

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Thanks Jeff for the feedback, but ...

The Server Settings, Licensing parameter is configured for the default
Remote Desktop for Administration and did not require a TS Licensing Server
when it was functioning. The Connections, RDP-tcp parameter is Type:
Microsoft RDP 5.2 but even with the 5.2 RDP client the same error occurs.
(Default Server 2003 SE SP2 installation with no other Terminal Services
configured.)

A network trace indicates 41 frames split accross two connections of 8
frames and 33 frames respectively, occuring in consecutively in what seems
to be session negotiation. In the first dialog, only 19 bytes are sent to
the server in frame 4 and 19 bytes are returned to the client in frame 5.
Frame 8 resets the TCP connection.

In the second dialog, 428 bytes are sent in frame 19 and includes the client
NETBIOS name. In frame 20, 337 bytes are returned with what appears to be
encryption algorithm negotiation. Frame 40 contains 48 bytes returned to
the client and the connection is reset in frame 41. Frame 40 is listed
below - data starts at offset 36.

TCP: Data: Number of data bytes remaining = 48 (0x0030)

00000: 00 0F 1F 49 B2 E6 00 0F 1F 49 A7 BA 08 00 45 00
....I²æ...I§º..E.
00010: 00 58 74 5E 40 00 80 06 01 5B C0 A8 01 C9 C0 A8
..Xt^@.€..[À¨.ÉÀ¨
00020: 01 CD 0D 3D 04 35 DF 5C 30 AF 1C 33 EA 09 50 18
..Í.=.5ß\0¯.3ê.P.
00030: FB F9 BB 79 00 00 03 00 00 30 02 F0 80 68 00 01
ûù»y.....0.ð€h..
00040: 03 EB 30 22 08 00 02 03 CD 0C 3E 6A 21 CE C5 0A
..ë0"....Í.>j!ÎÅ.
00050: B5 51 05 72 24 81 59 85 29 3B 1E 06 D0 8A 90 DC
µQ.r$�Y…);..Њ�Ü
00060: 2B 53 BC 70 CB 66 +S¼pËf

Regardless of the message displayed, this does not appear to be a network
connectivity issue. Any help is most appreciated.

"Jeff Loo" <jeffloo@comcast.net> wrote in message
news:4F0B45CF-FC52-4F72-A844-68C18CFFEFA7@microsoft.com...
> Ensure that you have a terminal services license server online and
> configured with available and matching User or Device CAL's in Terminal
> Services Configuration. Configure the terminal server to point to the same
> TS licensing server if automatic doesn't find it or if it is on a
> different subnet.
>
>
> "SPC" <sig52@hotmail.com> wrote in message
> news:OOI5NBmJJHA.1160@TK2MSFTNGP04.phx.gbl...
>> Has anyone else experienced the following problem with a Remote Desktop
>> Connection to a Windows Server 2003 SE SP2 with all current High Priority
>> and Optional updates applied? Any suggestions?
>>
>> The following is displayed in a critical error pop-up dialog box:
>>
>> Remote Desktop Disconnected
>>
>> This computer can't connect to the remote computer.
>>
>> The connection was lost due to a network error. Try connecting again.
>> If the problem continues, contact your network administrator or
>> technical support.
>>
>> The error occurs regardless if the connection is attempted remotely from
>> a Windows XP/Vista workstation or even locally through the loopback
>> interface.
>>
>> The checkbox for "Enable Remote Desktop on this computer" has been
>> selected in the System Properties, Remote tab.
>>
>> Netstat -anb indicates the following:
>>
>> TCP 0.0.0.0:3389 0.0.0.0:0 LISTENING 2944
>>
>> tasklist /FI "PID eq 2944" indicates the following:
>>
>> Image Name PID Session
>> Name Session# Mem Usage
>> ========================= ======== ================ ===========
>> ============
>> svchost.exe 2944
>> Console 0 4,468 K
>>
>> Windows Defender, Software Explorer tool indicates the following:
>>
>> Microsoft Generic Host Process for Win32 Services
>> File Name: svchost.exe
>> Display Name: Microsoft Generic Host Process for Win32 Services
>> Description: Generic Host Process for Win32 Services
>> Publisher: Microsoft Corporation
>> Digitally Signed By: Microsoft Windows Verification Intermediate PCA
>> File Type: Application
>> Auto Start: No
>> File Path: C:\WINDOWS\System32\svchost.exe
>> File Size: 14848
>> File Version: 5.2.3790.3959 (srv03_sp2_rtm.070216-1710)
>> Date Installed: 2/17/2007 10:04:01 AM
>> Process ID: 2944
>> User Name: NT AUTHORITY\SYSTEM
>> Services: Terminal Services
>> Classification: Permitted
>> Ships with Operating System: Yes
>>
>> The Terminal Services service is executed as follows:
>>
>> C:\WINDOWS\System32\svchost.exe -k termsvcs
>>
>> The Terminal Services Manager displays "The protocol is currently
>> enabled" for the RDP-Tcp (listener).
>>
>> A TCP connection with Telnet to port 3389 succeeds. An RDP session back
>> to the XP/Vista workstation succeeds. No Event Viewer messages are
>> logged.
>>
>> TIA
>>
>>
>

 

[SPC]

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

Re: RDP fails with "This computer can't connect to the remote computer" with no Terminal Services error indication

I was able to resolve the problem by deleting the connection from the
Terminal Services Configuration Management Console and re-creating the
connection with the default parameters. I don't know if a reboot is
required or not. I rebooted anyway but it may not matter. I do know for
certain that you can correct the problem without backing out MS updates. I
would expect if you are able to resove the problem by backing out updates
that when you re-apply patches, you may see the problem manifest itself
again.

It would seem as if more than a few admins may be having the same problem
based on their private responses so sorry for not posting any further
updates but it appeared to me as if the thread was dead.