• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 387
  • Last Modified:

Remote dektop connection

Hi,

when i connect to this server using mstsc this error is coming


Error message:

"The client could not connect to the remote computer.

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

Please try connecting again later. If the problem continues to occur, contact your administrator."
0
Manne
Asked:
Manne
6 Solutions
 
Pratima PharandeCommented:
The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accept new connections. It is also possible that network problems are preventing your connection. Please try your connection again later. If the problem continues to occur, contact your administrator.
Cause:  The remote computer might not be set up to accept remote connections.

Solution:  Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator.

Cause:  The remote computer might already have the maximum number of remote connections it is set up to accept.

Solution:  Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator.

Cause:  Network problems might be preventing the connection.

Solution:  Try connecting to the remote computer at a later time. If you receive the same message, contact the server administrator.


refer

http://technet.microsoft.com/en-us/library/cc780927(WS.10).aspx#BKMK_13
0
 
Premkumar YogeswaranAnalyst II - System AdministratorCommented:
Hi,

Make sure you have administrator access to that server.

Orelse add your name to remote desktop users group in the server.

qwinsta /server:servername

Check this command do anyother logged into the server

Regards,
Prem
0
Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

 
villeahCommented:
Hello,

1. Check that client is resolving server's name by pinging it.
2. Ensure that "Enable Remote Desktop on this computer" is checked on Remote tab under system properties.
0
 
waleedaCommented:
make sure that you enabled the remote desktop on the server by right click on my computer and click on properties click on remote tape and check the check-box allow user to remote desktop to this computer

make sure also that you are member of the remote desktop user on the server and if you wan to administrate the server you should be also member of administrators group

i hope it will help
0
 
rsoly777Commented:
Another thing looks like maybe was not covered is if you have only administrative access for RDP to that machine there are only 2 connections allowed, if those connections are used and the person did not log out those connections will still be in use. You need to log them out to gain a new connection. If you are remoting from a Windows  machine you might gain a third RDP connection by using the mstsc /Admin switch you might also try mstsc /console which mimics that you are logging in from the console.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: IP Lookup

Get more info about an IP address or domain name, such as organization, abuse contacts and geolocation.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now