Discussion:
Some XP Pro clients cannot connect using RDP
(too old to reply)
Paul Greer
2005-01-25 12:39:04 UTC
Permalink
We've got 2 servers at the one site, the first on is SBS 2000 and the second
Windows 2000, with VPN setup so that the remote users (all on XP Pro) can
access both servers by picking the correct internal IP address.
Some remote users can RDP to the second server but 2 users get the following
error:
"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."
The same users have no problem connecting to the first server. The main SBS
server also gets the same error when trying to RDP to the Windows 2000 server.
The License logging service is not running on the SBS server but is on the
windows 2000 server.
I've tried removing the MSLicensing registry keys as per article:
http://support.microsoft.com/kb/323597
but there's no change.
Any ideas?
Vera Noest [MVP]
2005-01-25 21:24:32 UTC
Permalink
This should help:

329896 - Error Message: Because of a Security Error, the Client
Could Not Connect to the Terminal Server
http://support.microsoft.com/?kbid=329896

--
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
http://hem.fyristorg.com/vera/IT
--- please respond in newsgroup, NOT by private email ---

"=?Utf-8?B?UGF1bCBHcmVlcg==?="
Post by Paul Greer
We've got 2 servers at the one site, the first on is SBS 2000
and the second Windows 2000, with VPN setup so that the remote
users (all on XP Pro) can access both servers by picking the
correct internal IP address. Some remote users can RDP to the
"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."
The same users have no problem connecting to the first server.
The main SBS server also gets the same error when trying to RDP
to the Windows 2000 server. The License logging service is not
running on the SBS server but is on the windows 2000 server.
I've tried removing the MSLicensing registry keys as per
article: http://support.microsoft.com/kb/323597
but there's no change.
Any ideas?
Loading...