Re: remote connections might not be enabled or the computer might be to busy
- From: "Vera Noest [MVP]" <vera.noest@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Tue, 27 Jun 2006 05:47:43 -0700
Have you checked with the command "netstat -an" on those clients if
they are listening on port 3389?
Is there anything in the EventLog on the clients?
Are they running SP2? Have you checked the firewall settings?
_________________________________________________________
Vera Noest
MCSE, CCEA, Microsoft MVP - Terminal Server
TS troubleshooting: http://ts.veranoest.net
___ please respond in newsgroup, NOT by private email ___
cdoc <cdoc@xxxxxxxxx> wrote on 27 jun 2006 in
microsoft.public.win2000.termserv.clients:
I hope this is the correct newsgroup for this question. I setup.
pcs (xp pro) with remote desktop everyday and usually with no
problem. I have had two machines recently at different
locations that were setup correctly (double checked) that I
cannot access. I get the following error...
"The client could not connect....remote connections might not be
enabled or the computer might be to busy"
Has anyone had this issue that can shine some light on
troubleshooting this for me.
Thanks in advance
- References:
- Prev by Date: remote connections might not be enabled or the computer might be to busy
- Next by Date: How can I create a single logon with the RDP client for users on Windows 2K and XP?
- Previous by thread: remote connections might not be enabled or the computer might be to busy
- Next by thread: How can I create a single logon with the RDP client for users on Windows 2K and XP?
- Index(es):
Relevant Pages
|
Loading
