client could not connect to terminal server

[Guest]

Iam working in a small domain and I have three different types of servers,all
of them have the terminal services installed on each of them.I have used the
terminal services to access each one of the servers ,but suddenly I
discovered that one server of them gives me this message " the client could
not connect to the terminal server the server may be too busy please try
connecting later" then I went to the server it self and opened the terminal
service manager (hoping that I could solve the problem with reseting the
rdp-tcp listener) but unfortunately the rdp-tcp listener was not appeared

please help I donot know what Should I Do
Best Regards:-
Ahmed

 

[MikeD]

Check the Application and System Log of the problem server and look for Term
Serv erros to help u solve the problem. Sounds like license issue.
Mike D

 

[Guest]

I found this event recorded
" Replication of license information failed because the License Logging
Service on server fpisrv.FPIEGY could not be contacted. "


Please Help

Replication of license information failed because the License Logging
Service on server fpisrv.FPIEGY could not be contacted.

 

[Vera Noest [MVP]]

That's EventID 213 from Source: LicenseServices, correct?

Your problem has nothing to do with Terminal Server licenses, you
have a problem with normal server CALs.
Check this error on EventID.net, there are several causes and
troubleshooting tips for this problem:

http://www.eventid.net/display.asp?eventid=213&eventno=52
&source=LicenseService&phase=1