Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows Server 2003Windows 2000Windows NTSmall Business ServerVirtual ServerExchange ServerIISHost Integration ServerISA ServerSMSWSUSMOMWindows Media ServerSecurityCertification
Related Topics
SQL ServerMS WindowsMS OfficePC HardwareMore Topics ...

Windows Server Forum / Windows 2000 / Terminal Services / November 2004

Tip: Looking for answers? Try searching our database.

client could not connect to terminal server

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
A~L~R~F~E - 28 Nov 2004 12:49 GMT
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 - 28 Nov 2004 19:37 GMT
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
> Iam working in a small domain and I have three different types of
> servers,all
[quoted text clipped - 12 lines]
> Best Regards:-
> Ahmed
A~L~R~F~E - 29 Nov 2004 13:09 GMT
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.

> 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.
[quoted text clipped - 15 lines]
> > Best Regards:-
> > Ahmed
Vera Noest [MVP] - 29 Nov 2004 19:57 GMT
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

--
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?QX5MflJ+Rn5F?= <ALRFE@discussions.microsoft.com> wrote
on 29 nov 2004 in microsoft.public.win2000.termserv.clients:

> I found this event recorded
> " Replication of license information failed because the License
[quoted text clipped - 27 lines]
>> > Best Regards:-
>> > Ahmed
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2009 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.