client can not connect

kazi

Guest

Posts: n/a

30th Apr 2005

I get the following msg from client pc each time
"The client could not connect to the Terminal server. The server may be
too busy. Please try connecting later."
Already tried recreate RDP connection,allow no: of terminal
connections,port fwding from router etc. we've win2003 domain server,
win2000 TS is member server. Lic server is 2003 and TS2000 Registry is
pointed to that server for lic issue. even i can not connect from TS 2000
itself via remote desktop utility. with "netstat" commands i even can not
see port 3389 open on win2000 TS server list..
pls suggest..

« Moving users to new server? | Terminal Services License Server Not found »

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
client /server VPN is fine, but client cannot connect internet anymore	duzhidian@gmail.com	Windows XP Networking	1	21st May 2007 05:04 PM
Unable to connect to shared directory, shared files from XP Pro client to XP Home Client on simple LAN	Ted Levy	Windows XP General	1	23rd Nov 2004 02:31 AM
Client could not connect	Sammy	Windows XP Work Remotely	0	19th Sep 2004 01:12 PM
Cannot Connect using TS Client	M P	Microsoft Windows 2000 Networking	1	14th Apr 2004 09:49 PM
Cannot Browser nor Connect Client to Client in a Home Domain	Terence Ifan Bland	Windows XP Networking	0	12th Aug 2003 06:15 AM