[Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1774
  • Last Modified:

Unable to connect through remote desktop connection

I am facing this problem while connecting to a remote server through RDC...

Server is accessed through WAN.
I am able to ping it but unable to connect.

The error message received is as follows

The client could not establish a connection to remote computer
0
rujs
Asked:
rujs
  • 3
  • 3
  • 3
  • +5
2 Solutions
 
Phadke_hemantCommented:
is the server behind firewall? is the RDP port is changed on the server?
which os the server is having? is it win server 2003 or 2000?
0
 
Phadke_hemantCommented:
if you are behind the firewall, you need to open RDP port or allow the remote desktop connection service. also check whether RDC is enabled on the remote server and you have the rights to log on through terminal services
0
 
marine7275Commented:
Phadke is right

Open port 3389 (RDP) on your firewall
Make sure you have checked allow remote connections in my computer/properties/remote tab
male sure routing and remote connections service is on in service
0
What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

 
TrilotechCommented:
While all of the suggestions are good and will probbaly fix your problem you have a bigger one. I would NOT open an RDC port to the internet...

I would suggest re-thinking how you want to do this.

On my clients networks I establish a VPN FIRST then remote through that VPN to the machine I want access to.
0
 
darrenakinCommented:
Please also forward port 4125 and 3389
0
 
tellawiCommented:
All what you need to do is to setup web based remote desktop connection and then you can customize the port number you need to use for remote connection. a very nice artical and all what you need to how to set it up as follows:

http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx


regards


0
 
rujsAuthor Commented:
I am able to connect to other servers from the same terminal but not to this particular server.
I am getting this message now
"The connection was ended because of network error. Please try connecting to the remote computer again."
Thanks and regards,
rujs.
0
 
Phadke_hemantCommented:
are you able to resove the ip address of that server using hostname?
to to connect using the ip address
you may add that server to your hosts file e.g. add ip_addr athen press tab then type the servername like-

111.222.333.444      servername

add this entry to your hosts file which is located in C:\WINDOWS\system32\drivers\etc folder, if you are using windows 2000, you will find 'WINNT' instead of 'WINDOWS'
0
 
tellawiCommented:
If you are getting the following error: "Unable to log you on because of an account restriction." the you probably using an user account with an empty password.

you can resolve this issue through global policies. check the following article from Microsoft:

http://support.microsoft.com/default.aspx?scid=kb;EN-US;q303846

Regards
0
 
tellawiCommented:
this is another article can help you in troubleshooting remote desktop issues:

http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html

0
 
amontyhCommented:
Ruis,

Are there any errors in the logs of the server you are trying to connect to?  Perhaps anything related to MS Licensing?

Cheers.
0
 
amontyhCommented:
I think the initial track on checking port availability was the best first step.  However, we were never able to determine whether or not the client and server could communicate on port 3389.

Additionally, we did not determine if clients local to the server could connect (possibly pointing to a problem with Terminal Services on the server itself).  This would have been crucial in pinpointing the source of the problem (network or server).

Hope that helps.


0
 
rujsAuthor Commented:
Sorry Guys,
Sorry for not updating you people, but I could not wait for the resolution of the problem for so long as work had to be continued on that PC. My colleague formatted the PC and now I am able to use RDC to the required Server. I leave it to the Experts to decide what they want to do with the question.
Rujs.
0
 
rujsAuthor Commented:
If there are regular comments made by any member other than you, then you'll have to ask to have your question deleted by one of the Moderators; This is what I saw in the help.
Rindi, Could you please delete this question or please can you suggest what is to be done.
0
 
rcom_infraopsCommented:
Helloo Guys,

Unable to Take RDP on Windows 2003 Servr- SP2

I am not able to take RPD on server, but we are able to ping & telnet port 3389.
No events error found for same,
0

Featured Post

Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 3
  • 3
  • 3
  • +5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now