"The client could not connect to the remote computer..."

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hello,
when I try to use remote connection from computer A to computer B everything
is fine but when I try to connect remotly from computer B to computer A it
says

"The client could not connect to the remote computer. Remote connection
might not be enabled or computer might be too busy to accept new connections.
It is also possible that network problems are preventing your connection."

remote connection are enabled on both computers, windows firewall is turned
off on both computers so are norton anti-virus and windows antispyware...

also, when I try to switch users on computer A it does not work: i click
switch users, click on another user and it does not log on, it brings me back
to the users screen.

thank you!
 
If your running NAV 2005 some folks report that the worm protection blocks
RDP connections... Check the NAV 2005 support web pages or documentation for
help with that...

--

Al Jarvi (MS-MVP Windows Networking)

Please post *ALL* questions and replies to the news group for the mutual
benefit of all of us...
The MS-MVP Program - http://mvp.support.microsoft.com
This posting is provided "AS IS" with no warranties, and confers no
rights...
 
taht does not seem to be the problem, it does the same thing even with
NAV2005 turned off and with the help on windows remote they provide.
 
"The client could not connect to the remote computer"

Hi,

We are also having this problem at our site. We are a Novell site and i'm wondering if that has anything to do with it. The guy who set up our Juniper box has no problem connecting to the Terminal Server but he can't seem to figure out what is causing this problem. If anyone has any ideas, please let me know asap as our director is looking to drop this service if we dont get it running soon. BTW, i have tried disabling "simple file sharing" and it didnt work.
 
If you are using window XP you must know that it can only take 10 simultaneous request at any given time. Ensure that machine B does not manage other network request then try the connection
 
Hi, Thanks for replying. I found the problem. It wasn't with Terminal Server at all. When the Juniper box was setup, the guy specified that the client and server must use port 3389. I simply removed the client port and told it to connect on any available port. This solved the porblem.
 
Back
Top