RWW - RDP Client Connection Problems "The client could not connect to the remote computer..."

[mhudacko]

Hello - I have a 2003 SBS
RWW is working in part. I can login to the RWW portal, I can run OWA.
When I run "Connect to Server Desktop" or "Client Desktop" and once I have selected the computer I receive the following message.

"The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to acept new connections. It is also possible that network problems are preventing your connection. Please try connecting again later. If the problem continues to occur, contact your administrator."

More on the overall config.
Hardware firewall, no ISA server.
Ports open, 3389, 4125, 443, 1732

RDP works just fine when making a direct connection to the server from the LAN, VPN client or direct from the WAN.

I am thinking that the problem is an ActiveX not being downloaded from the server to the PC station using RWW.

Any help you could give it greatly appreciated!
Thanks
Marty

mhudacko wrote:
> Hello - I have a 2003 SBS
> RWW is working in part. I can login to the RWW portal, I can run OWA.
> When I run "Connect to Server Desktop" or "Client Desktop" and once I
> have selected the computer I receive the following message.
>
> "The client could not connect to the remote computer. Remote
> connections might not be enabled or the computer might be too busy to
> acept new connections. It is also possible that network problems are
> preventing your connection. Please try connecting again later. If the
> problem continues to occur, contact your administrator."
>
> More on the overall config.
> Hardware firewall, no ISA server.
> Ports open, 3389, 4125, 443, 1732
>
> RDP works just fine when making a direct connection to the server from
> the LAN, VPN client or direct from the WAN.
>
> I am thinking that the problem is an ActiveX not being downloaded from
> the server to the PC station using RWW.
>
> Any help you could give it greatly appreciated!
> Thanks
> Marty
>
>
reregister the dll

see www.fixmyrww.com

Susan Bradley wrote:
> mhudacko wrote:
>> Hello - I have a 2003 SBS
>> RWW is working in part. I can login to the RWW portal, I can run OWA.
>> When I run "Connect to Server Desktop" or "Client Desktop" and once I
>> have selected the computer I receive the following message.
>>
>> "The client could not connect to the remote computer. Remote
>> connections might not be enabled or the computer might be too busy to
>> acept new connections. It is also possible that network problems are
>> preventing your connection. Please try connecting again later. If the
>> problem continues to occur, contact your administrator."
>> More on the overall config.
>> Hardware firewall, no ISA server. Ports open, 3389, 4125, 443, 1732
>>
>> RDP works just fine when making a direct connection to the server from
>> the LAN, VPN client or direct from the WAN.
>>
>> I am thinking that the problem is an ActiveX not being downloaded from
>> the server to the PC station using RWW.
>>
>> Any help you could give it greatly appreciated!
>> Thanks
>> Marty
>>
>>
> reregister the dll
>
> see www.fixmyrww.com
When connecting via Remote Web Workplace to SBS 2008 ..if it fails
perform the following checks:

1. You have installed the self signed cert bundle on the remote machine
(you can get around this one by using the Trusted Cert wizard and buying
(and installing) a third party cert)

2. The ActiveX control is installed and active (not disabled) in IE.

To work around this issue, follow these steps:

1. Start Internet Explorer.
2. Visit the Web site that is causing this problem.
3. If you are using Windows Internet Explorer 7, follow these steps: a.
On the Tools menu, point to Manage Add-ons, and then click Enable or
Disable Add-ons. The Manage Add-ons dialog box appears.
b. In the list of add-ins, search for the Microsoft Terminal Services
Client Control ActiveX control or for the Microsoft RDP client Control
ActiveX control.
c. Click the control, click Enable, and then click OK to close the
Manage Add-ons dialog box.

If you are using Internet Explorer 6, follow these steps: a. On the
Tools menu, click Manage Add-ons. The Manage Add-ons dialog box appears.
b. In the list of add-ins, search for the Microsoft Terminal Services
Client Control ActiveX control or for the Microsoft RDP client Control
ActiveX control.
c. Click the control, click Enable, and then click OK to close the
Manage Add-ons dialog box.

4. Add the site to your Trusted Sites in Internet Explorer.
5. Restart Internet Explorer.
6. Try to connect to the remote computer. Or, try to start the remote
application.


3. Reregistering the ActiveX control -- specifically - To solve this
problem, run the Regsvr32.exe program to reregister the Mstscax.dll
file. To do this, click Start, click Run, type regsvr32
%systemroot%\system32\mstscax.dll, and then click OK. The bat file is
here:
http://www.codeplex.com/sbs/Release/...eleaseId=18496

When connecting via Remote Web Workplace to SBS 2003 ..if it fails
perform the following checks:

1. You have confirmed that the self signed cert has been properly
installed (see here for instructions specifically for Vista -
http://msmvps.com/blogs/bradley/arch...-in-vista.aspx


2. The ActiveX control is installed and active (not disabled) in IE.

To work around this issue, follow these steps:

1. Start Internet Explorer.
2. Visit the Web site that is causing this problem.
3. If you are using Windows Internet Explorer 7, follow these steps: a.
On the Tools menu, point to Manage Add-ons, and then click Enable or
Disable Add-ons. The Manage Add-ons dialog box appears.
b. In the list of add-ins, search for the Microsoft Terminal Services
Client Control ActiveX control or for the Microsoft RDP client Control
ActiveX control.
c. Click the control, click Enable, and then click OK to close the
Manage Add-ons dialog box.

If you are using Internet Explorer 6, follow these steps: a. On the
Tools menu, click Manage Add-ons. The Manage Add-ons dialog box appears.
b. In the list of add-ins, search for the Microsoft Terminal Services
Client Control ActiveX control or for the Microsoft RDP client Control
ActiveX control.
c. Click the control, click Enable, and then click OK to close the
Manage Add-ons dialog box.

4. Add the site to your Trusted Sites in Internet Explorer.
5. Restart Internet Explorer.
6. Try to connect to the remote computer. Or, try to start the remote
application.


3. Reregistering the ActiveX control -- specifically - To solve this
problem, run the Regsvr32.exe program to reregister the Mstscax.dll
file. To do this, click Start, click Run, type regsvr32
%systemroot%\system32\mstscax.dll, and then click OK. The bat file is
here:
http://www.codeplex.com/sbs/Release/...eleaseId=18496



-- 0 --

Review these KB articles:

After you apply a Windows XP service pack, the remote desktop session
fails:
http://support.microsoft.com/kb/928055/en-us


You cannot connect to a remote computer or start a remote application
when you use Terminal Services Web Access or Remote Web Workspace on a
Windows XP SP3-based or Windows Small Business Server 2003 SP1-based
computer:
http://support.microsoft.com/default...b;EN-US;951607

[mhudacko]

OK - So I have applied all of the above suggestions with no success.

In further testing I have tested the ActiveX contrl by logging into a different VPN hardware which can utilize the ActiveX control and it loaded the "Microsoft RDP Client Control (redist)" file mstscax.dll and it functioned correctly - so it is looking like the problem is on the side of the SBS server
Any further suggestions?

Hello,

Thank you for posting here. Also thanks for the great sharing from Susan.

According to your description, I understand that:

You cannot remote desktop (RWW) to the server and client computers in the
SBS domain.

If I have misunderstood the problem, please don't hesitate to let me know.


Agree with Susan that you should first check the Active X on the Internet
Explorer to narrow down the issue. Furthermore, please realize that when
you connect to a computer in the domain in RWW, RWW accept the port 4125 on
the SBS server and redirect to the port 3389 on the destination server. The
port 4125 on the SBS server is only open to be listened when it receive the
RWW remote desktop connection.

However, when you install the MS08-067 security update, random ports will
be used. You may run the netstat -ano |find "4125" before the RWW
connection to verify the essential port has not be occupied. If the port
4125 is used by other programs, try to find out the culprit and assign
another ports for it. If the culprit is the MS08-037, please add the port
4125 in the port exception list in the registry. To do that:

1. Click Start, click Run, type regedit, and then click OK.
2. Locate and then click the following subkey:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters

3. Right-click ReservedPorts, and then click Modify.
4. Type the range of ports that you want to reserve such as 1723-1723. For
a detailed list of the widely used services (ports), you may refer to:


956189 Some services may not start or may not work correctly on a
computer that is running Windows SBS after you install the DNS Server
security update 953230 (MS08-037)
http://support.microsoft.com//kb/956189


More related information for your reference:

886209 Users cannot connect to remote desktops by using the Windows Small
Business Server 2003 Remote Web Workplace
http://support.microsoft.com/default...b;EN-US;886209

Hope it helps. If you have any questions or concerns, please do not
hesitate to let me know.



Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.

[mhudacko]

Hi Miles and Yes! Thanks Susan for the post.
Unfortunately the problem continues...

Thanks Miles for the assistance as well!

As a recap (see my previous post) I checked the ActiveX "Microsoft RDP Client Control (redist) file mstscax.dll" mark enabled.
Equally it functions correctly when connecting to other devises utilizing the MS ActiveX RDP Client...

Just for kicks I tried Susan's suggestion & reregistered regsvr32 %systemroot%\system32\mstscax.dll

Miles - before making any reg changes I checked to see if anything else was trying to use port 4125 has I know that mad.exe will sometimes use that port.
Nope only w3wp.exe is using 4125

While watching w3wp.exe using the lestining port 4125 and on my attempt to connect with RWW-RDP I can see a connection "established" on the RDP port 3389 at this point the message "The client could not connect to the remote computer..." is presented to my computer.

I have tested this from several PC's all with the same result.
So based on what I have read here and elsewhere seems to me that RWW is working and configed correctly.

So as a matter of taking every attempt to correct this problem I made the following changes from your post:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters
Adding 4125

&

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc
3. Right-click Rpc, point to New, and then click Key.
4. In the New Key #1 box, type Internet, and then press ENTER.
5. Create the following three registry entries:
Entry name: Ports
Type: REG_MULTI_SZ
Value data: 4125

Entry name: PortsInternetAvailable
Type: REG_SZ
Value data: N

Entry name: UseInternetPorts
Value type: REG_SZ
Value data: Y

Reboot
Problem persists
I am wondering is there is a licensing issues or perhaps RWW-RDP will not work if the Terminal Server is in Remote Admin Mode?
I have not purposefully turned on Application Server assuming this would be installed during the build. I just checked and it has not been enabled...any thoughts?

Hello,

In the SBS environment, TS Application mode is not recommended to be
installed on the SBS server. You can add the feature on another Windows
Server 2003 server but not on the SBS server. It should be the expected
that TS Application mode is not enabled on the SBS server. All computers in
the domain (SBS server and Clients) should have TS Remote Administration
Mode enabled. The Administration Mode (2 concurrent sessions) is shipped on
the system and no license is needed for Administration Mode.

Form the description, it does seem that the RWW configuration on the SBS
sever is all right. Please have a test described below to narrow down the
issue.

1. In the SBS internal domain, choose 2 client computer such as Com_1and
Com_2.
2. On the SBS server, check whether you can RDP to Com2 properly with MSTSC.
2. On the Com_1, log onto the RWW with a domain administrative account.
3. Then click Connect to client desktop and choose Com_2 to connect.
4. On the SBS server, check whether the connection from the Com_1 on port
4125 is properly established using the following command:

netstat -ano |find "4125"

5. If the RWW remote desktop access is all right from the internal network,
please make sure that port 4125 in open on the firewall. You can verify it
by Telnet from the external network.

6.There is a known issue that a intermediate network device may drops
packets because of the exceeded MTU. To check it out, I suggest you perform
the following command:

Ping <SBS server IP address> -f -l 1472

If the returned result is "Packet needs to be fragmented but DF set", it
indicates the network device is fragmenting packets. we are able to
identify that the largest full packet we could send was 1407B (Ethernet has
a maximum frame size of 1500B). Please try a smaller buffer size such as
1400 to identify the largest full packet you could send (Ethernet has a
maximum frame size of 1500B). After we get the proper MTU for the
intermediate network device, we could modify the following registry value
to specify the acceptable MTU size on the SBS server.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\Tcpip\Parameters\Interf
aces\<ID for Adapter>
Value Name: MTU
Value Type: REG_DWORD
Value date: such as 1300 (decimal)


More information for your reference:
===========================
314825 How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/default...b;EN-US;314825

HOW TO: Change the Default Maximum Transmission Unit (MTU) Size Settings
for PPP Connections or for VPN Connections
http://support.microsoft.com/kb/826159

Recommended TCP/IP settings for WAN links with a MTU size of less than 576
http://support.microsoft.com/kb/900926/en-us
314825 How to Troubleshoot Black Hole Router Issues
http://support.microsoft.com/default...b;EN-US;314825

Hope it helps. If you have any questions or concerns, please do not
hesitate to let me know.




Best regards,
Miles Li

Microsoft Online Partner Support
Microsoft Global Technical Support Center

Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.