Clients can not connect

=?Utf-8?B?a2F6aQ==?=

Guest

Posts: n/a

30th Apr 2005

Everytime client tires to connect gets error "The client could not connect to
the Terminal server. The server may be too busy. Please try connecting
later". So far I've tried reset RDP connection, checking no: of permitted
sessions, licenses etc.
I've a 2003 domain controller which issues lic: for win2000 TS clients, TS
2000 registry is also set to acquire lic from win2003.
Pls suggest...

« Problem with Non Admin users logon | Suggested remote printers - native W2K Server drivers »

Thread Tools
Show Printable Version Email this Page
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads You may not post replies You may not post attachments You may not edit your posts BB code is On Smilies are On [IMG] code is On HTML code is Off Trackbacks are On Pingbacks are On Refbacks are Off Forum Rules

Similar Threads
Thread	Thread Starter	Forum	Replies	Last Post
clients cannot connect	=?Utf-8?B?V29sZmdhbmcgSG9sZXNjaA==?=	Microsoft Windows 2000 Terminal Server Clients	4	30th Apr 2005 08:11 PM
Some XP Pro clients cannot connect using RDP	=?Utf-8?B?UGF1bCBHcmVlcg==?=	Microsoft Windows 2000 Terminal Server Clients	1	25th Jan 2005 09:24 PM
ICS clients cannot connect	Peter	Windows XP General	7	22nd Jun 2004 02:54 PM
Clients can't connect	=?Utf-8?B?V2VybmVyIFNU?=	Microsoft Windows 2000 Terminal Server Applications	3	31st Mar 2004 09:14 PM
Clients cannot connect	=?Utf-8?B?Q0I=?=	Microsoft Windows 2000 Terminal Server Clients	3	5th Oct 2003 03:19 PM