"The client could not connect to the remote computer. Remote connections..." - Server 2003

[Maestro]

"The client could not connect to the remote computer. Remote
connections might not be enabled or the computer might be too busy to
accept 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."

I have Windows Server 2003 and am using Session Directory and Load
Balancing Using Terminal Server. Seems like an Administrator can log
on to this "cluster" (i use the term loosely) without issues. but
when a user attempts to, they get the above error message.

In "Network Load Balancing Manager" under Host Properties/Port Rules
tab - i have set the:
Cluster IP address = All
Start = 3389
End = 3389
Protocol = Both
Mode = Multiple
Priority = -- (shows this but is actually set to 1 for the NLBM and 2
for the other server)
Load = Equal
Affinity = None

So I don't think this is the issue

In Users/Groups of the local box i have "Domain Users" in the groups
"Users" and "Remote Desktop Users"

UPDATE
David - one of my programmers can RDP to TS1 without an issue and
cannot to TS2. get's the above error and is an administrator of TS2

Now I'm really stuck - Please Advise

[Maestro]

"Because of a security error, the client could not connect to the
remote computer. Verify that you are logged on to the network, and
then try connecting again." specific error of David

[Maestro]

terminal server. After making sure that you are logged on to the
network, try connecting to the server again.

Cause: If you upgraded a Windows NT domain to Windows 2000 or Windows
Server 2003, then the certificate on the terminal server might be
corrupt. As a result, Windows 2000 Terminal Services clients might be
repeatedly denied access to the terminal server.

Solution: On each terminal server and client, perform the following
steps:

1. On each terminal server, create a backup of the registry.

2. Navigate to the following registry subkey: HKLM\SYSTEM
\CurrentControlSet\Services\TermServices\Parameters.

3. On the Registry menu, click Export Registry File.

4. In the File name box, type exported-parameters, and then click
Save.

If you need to restore this registry subkey in the future, double-
click exported-parameters.reg.

5. Under the Parameters registry subkey, right-click each of the
following values:
-Certificate
-X509 Certificate
-X509 Certificate ID

6. Click Delete, and then click Yes to confirm the deletion.

7. Close Registry Editor, and then restart each terminal server.

8. On the client, create a backup of the MSLicensing registry key and
its subkeys, and then remove the original key and subkeys by doing the
following:
-Navigate to the following registry subkey: HKEY_LOCAL_MACHINE\SOFTWARE
\Microsoft\MSLicensing.
-Click MSLicensing.
-On the Registry menu, click Export Registry File.
-In the File name box, type mslicensingbackup, and then click Save.
-If you need to restore this registry key in the future, double-click
mslicensingbackup.reg.
-On the Edit menu, click Delete, and then click Yes to confirm the
deletion of the MSLicensing registry subkey.
-Close Registry Editor, and then restart the client computer.

Caution

Incorrectly editing the registry may severely damage your system.
Before making changes to the registry, you should back up any valued
data on the computer.

Solution: If the client still cannot connect to the terminal server,
perform the following variation of this procedure:

1. Deactivate the license server.

2. Reactivate the license server by using the Telephone connection
method in the Terminal Server License Server Wizard.
NOTE: When you activate Terminal Server Licensing by using the
Telephone option, Terminal Server Licensing uses a different
certificate.

3. On each terminal server, create a backup of the registry, and then
delete the Certificate, X509 Certificate, and X509 Certificate ID
registry keys, as described in the preceding procedure.

4. Close Registry Editor, and then restart each terminal server.

5. On the client, create a backup of the MSLicensing registry key and
its subkeys on the client, and then remove the original key and
subkeys as described in the preceding procedure.

6. Close Registry Editor, and then restart the computer.

When the client is restarted, the missing registry key is rebuilt.

See also:
Deactivate a Terminal Server license server @
http://technet2.microsoft.com/WindowsServer/en/library/b12a69de-344e-437c-a085-6caec28244b41033.mspx
Reactivate a Terminal Server license server @
http://technet2.microsoft.com/WindowsServer/en/library/e1df9013-5193-411a-8be4-4e5140b006eb1033.mspx

[Maestro]

Still Getting this error - the users getting the error are outside the
lan on the wan we are 154.15.xxx.xxx and they are 154.28.xxx.xxx
joined on a point to point connection (10mb) and 1 AD structure for
both sites DC's in both sites that replicate...

any thoughts?

[Maestro]

"The client could not connect to the remote computer. Remote
connections might not be enabled or the computer might be too busy to
accept 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."

I have Windows Server 2003 and am using Session Directory and Load
Balancing Using Terminal Server. Seems like an Administrator can log
on to this "cluster" (i use the term loosely) without issues. but
when a user attempts to, they get the above error message.

I've checked rights and i'm about to call Microsoft, any thoughts? ?
anyone?

[Maestro]

"The client could not connect to the remote computer. Remote
connections might not be enabled or the computer might be too busy to
accept 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."

I have Windows Server 2003 and am using Session Directory and Load
Balancing Using Terminal Server. Seems like an Administrator can log
on to this "cluster" (i use the term loosely) without issues. but
when a user attempts to, they get the above error message.

I've checked rights and i'm about to call Microsoft, any thoughts? ?
anyone?

[Maestro]

Well i fixed the damn thing! -
We have 2 sites - I only received this error from the other site -
we have 2 cisco routers with one side 172.20.20.1 inside interface and
192.168.1.1 for outside with a private line to the other side
192.168.1.2 outside 172.10.10.1 inside
the 172.20 side was the problem - so is statically arpd the connection
on the 172.10 side (which is the default route for the 172.20 side) i
had to use the mac address that's multicasted by the Load Balancing
Manager on the load balancing server.

I hope this helps some one