Being able to logon once is typical for a licensing problem. The
first connection is always made on a temporary license, on the
second connection, a permananet license must be downloaded to the
client and stored thre.
If the user on the client doesn't have to necessary permissions on
the folder which stores the license, then it can't be saved and
thus the connection is refused.
Check the EventLog on the terminal Server to confirm that this is
indeed your problem. It should have a warning that the server
cannot issue a license to the client.
You need at least write permissions on this folder:
/Users/Shared/Microsoft/RDC Crucial Server Information/RDC GLOBAL
DATA.
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting:
http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
Brian <> wrote on 18 feb 2008 in microsoft.public.mac.rdc:
> I am also getting the same error. I have checked all of the Help
> offerings for a solution and have come away with nothing. I am
> using RDC 1.0.3 and we use it on multiple machines across our
> LAN and WAN. I only have problems with one computer. I tried to
> see if it was user specific and the result I got were strange.
> When I created a new user to run RDC on, it started up fine the
> first time. When I logged off of the system and then tried to
> log back in, it gave me the error message that hpblair got. Is
> this a common error? I have enough licenses; the user name and
> password work from other machines. I am out of ideas. Any help
> would be appreciated. >> Stay informed about: Client could not connect to remote computer 
FAQ
Search
Profile
Private Messages
Log in/Register/Password
