Frustrated with Remote Desktop!! HELP!!!

0 pts.
Tags:
DataCenter
Microsoft Windows
Networking
I desperately need help with my Remote Desktop Web Connection? I have spent many hours trying to get the Remote Desktop Web Connection to work. It will work on my home LAN, but not over the internet. I appreciate any help in getting this to work. Below are some notes on what happens, what I have tried, and what I have set up. - I have downloaded and run tswebsetup.exe from MS. It set up TSWeb in wwwroot. Terminal Services Web Client now appears in my add/remove programs contol panel. - I have Windows Firewall turned off. - I am not running any kind of third-party firewall software on my PC. - I have ports 80 and 3389 forwarded in my D-Link DI-624 router to the static ip of my host PC. - I have also tried putting my host PC in the DMZ. - I am using dyndns.com to get to my home PC over the internet. - I can view both htm and asp pages on my home PC, from any PC on the internet, without any problems. - I can view the /tsweb/default.htm over the internet just fine. However, when I enter into the "server" field and press enter then one of two things happen. A) If I enter the "name" of the host then I immediately receive the "VBScript: Remote Desktop Disconnected" dialog saying, "The specified remote computer could not be found. Verify that you have typed the correct computer name or IP address, and then try connecting again." B) If I enter the "IP Address" of the host then it "thinks" for about 30 seconds and then I receive the ""VBScript: Remote Desktop Disconnected" dialog saying, "The client could not connect to the remote computer. Remote connections might not be enabled or the computer might be too busy to accpet 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." - I have used canyouseeme.org to check my ports 80 and 3389. Both are visible. - I have used PortQry.exe and the 3389 is enabled. - I have looked at netstat -a in the cmd screen and the host name is "listening" on 3389. I'm stumped. Any ideas on where I can go from here? Thanks in advance!!
ASKED: December 11, 2006  11:03 PM
UPDATED: March 11, 2008  4:10 PM

Answer Wiki

Thanks. We'll let you know when a new response is added.

I’m presuming that you are using something other than windows xp. I would recommend that you download RDCLI.EXE from microsoft’s website and use it. Here’s a link:

http://www.microsoft.com/windowsxp/downloads/tools/rdclientdl.mspx

Your d-link router must be pointed to the computer on your internal network, that port 3389 is opened for.

In other words, you cannot open port 3389 without specifying the ip address of the “internal network” destination.

Also ensure, by viewing the target computer’s power options, that hibernate is not enabled, as this will allow the computer to shut itself down and consequently will not be available for a network connection.

Good Luck.

Discuss This Question: 20  Replies

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when members answer or reply to this question.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy
  • Vdinenna
    Try this link. Do you have web services running on your PC? http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx Why don't you use Remote Desktop that comes with XP? It works off of port 3389. Are you using something other than XP outside on the net? Vince
    60 pointsBadges:
    report
  • Dhagar
    It is possible that this is a NAT'd environment and using PAT. In which case your request coming in to the server is on port 3389 but the answer may come across any port number assigned thereby not responding on port 3389. You could put a sniffer on your PC you are trying to remote from and capture packets when you try to make the connection. Look for responses from your source IP but on a different port.
    0 pointsBadges:
    report
  • Petroleumman
    Hello, Based on your errors a couple things come to mind; 1) do you have IIS properly configured and running on your computer? 2) Is DNS able to resolve your computer name? If not, you need to set up an A record to make this happen. 3) Have you properly set up RDP on your host computer? You want to make sure you have added your user account to the Remote Desktop security group on your host computer. 4) have you confirmed your network firewall is allowing RDP traffic into your network? Here is a link to a very good document on setting up RDP web services on XP. Maybe this will help you out. http://www.microsoft.com/windowsxp/using/networking/expert/northrup_03may16.mspx Good luck!
    0 pointsBadges:
    report
  • JohnTWT
    Any reason why you can't use VPN and then just use the RDP client to administer the server over it? Or is this PC to PC?
    0 pointsBadges:
    report
  • Tbitner
    I would also suggest using Remote Desktop built-in to XP. Make sure it's enabled by going to properties of My Computer and click on "remote" tab. Logging or sniffing would is also a good idea to make sure PAT isn't the culprit. Can you enable logging on the D-Link? Also turn on Windows Firewall but enable logging in the Advanced tab. I've used this quite a few times to diagnose pc connectivity problems.
    510 pointsBadges:
    report
  • Enterprisephil
    1) Can you try using the router ip address instead for the TSweb connectivity over the internet? 2) In the hosts file of all the systems add the router IP address and type a userfriendly name to all that to resolve the name to IP address. 127.0.0.1 localhost 192.168.0.25 Theater Where the ...0.25 is your local network-assigned internal IPaddress. Your ISP however has assigned a different IP address. Use that instead....(163.12.145.1 Theater) If your router has been given that address then use that to resolve your system name and thereby the internet access.
    0 pointsBadges:
    report
  • Revjebjr10
    If all you need to do is control a remote PC I suggest giving up on WRD and use logmein.com. I use the free version regularly for remote access and even support. It was a breeze to setup and I can access PCs from any internet enabled PC. I've even done it from my Treo in an emergency.
    0 pointsBadges:
    report
  • Redwings3030
    Hello All and thank you for your help!! Okay, I thought I was thorough in my description, but it appears I left a couple of important things out. - I am running WinXP SP2 on the host machine (I am running the same on all my PCs on the network, but the only one I'm using Remote Desktop on is my main PC.) - I am using the built-in Remote Desktop that is packaged with XP. I'm not using any VNC based services, although I have tried those and have encountered similar problems, but that's another story. - Remote Desktop is ONLY setup on my main PC. I do not have it running on any other PCs in the network. -I do have port 3389 and port 80 forwarded to the IP address of the PC on the internal network. Now to answer some of the questions you've asked: - I do have web services running on the main PC and only the main PC. I have not had a chance to try all of the suggestions, but I will review the page that petroleumman sent and have modified my hosts file as well as my lmhosts.sam file to include the suggested dns entries. To revjebjr10, thanks for the suggestion of logmein.com I was using that until my company denied access to that website. Ugh, they're just making it harder and harder on us. And to JohnTWT, I'm not sure how I would use VPN since my router does not have VPN capabilites. Forgive my ignorance, but I'm not sure if it is PC to PC. I'm connecting from my work PC inside the company network to my PC at home inside my home network behind the router. Thanks again to all of you who have responded and please keep the suggestions coming. I will keep you all posted on how they all work out.
    0 pointsBadges:
    report
  • Mbdata
    Check Firmware and Revision on D-Link DI-624. Change firmware in this router to newest. For example firmware 4.02 in revision D is realy shit and doesn't work propertly.
    0 pointsBadges:
    report
  • Enterprisephil
    1) Can you try using the DLINK router ip address instead of the PC IPaddress for the TSweb connectivity over the internet? 2) In the hosts file of the PC you are trying to access and the remote PC and add the router IP address and type a userfriendly name to all that to resolve the name to IP address. Like so: 127.0.0.1 localhost 192.168.0.25 Theater.....instead use the following 163.28.112.34 Theater...where 163.28.112.34 is the router IP address. pls can you let us know if this works ?
    0 pointsBadges:
    report
  • Stevesz
    Have you done any testing internally--inside your router on your network? Can you reach the designated machine from another machine on your network? If I wa having this sort of problem, I'd try this first. It would indicate where the problem may lay--with the machine setup or with the router and other gear you may have between your outside connection and the machine you are trying to reach.
    2,015 pointsBadges:
    report
  • Dhagar
    You can take a look here... http://theillustratednetwork.mvps.org/RemoteDesktop/RemoteDesktopSetupandTroubleshooting.html
    0 pointsBadges:
    report
  • Stevesz
    redwings3030 wrote me privately to say that he is able to connect from a computer on the local network. Now that it is known that a connection is possible we need to take a look at the path the data travels. It enters your network by going through a router/firewall. Test the connection from the outside by trying to connect. Look at the incoming logs to see if the connection is being accepted or rejected by the router (you may need to change your logging options so you can see the acceptance of the data. If the data is being rejected, determine why, and fix it. If it is being accepted, make sure it is pointed to the correct machine. While I am not familiar with how D-Link handles port opening, most routers require you to forward a port in one section (port forwarding) and then open the path in another section (firewall rules). Remove any rule you may have in the firewall portion, and make sure the port is forwarded properly--right port, right machine address--and try to connect again. Look at the logs again for failure or acceptance. If you do make the connection, you are good to go, problem solved. If you still are getting blocked, add the rule for access to your firewall. This should allow you to get through.
    2,015 pointsBadges:
    report
  • Dwiebesick
    You say your company denied you access to logmein. How did they do that? Can you verify that your router is connected to the internet and not your internal network? Are you in a larger network were you placed your router between your computer and the outside world? I am just trying to get a better understanding of your overall infrastructure. Good luck dmw
    2,235 pointsBadges:
    report
  • Redwings3030
    Well folks, I tried modifying the hosts file and still no joy. I checked D-Link's website and there is an FAQ about setting up the router specifically for Windows XP Remote Desktop. I set the router back to default factory settings and tried to set it up exactly the way they had in the post and it still didn't work. I'm about ready to throw the router out the window. I'm not sure what else it can be. I had an old non-wireless router sitting around that I used to use Remote Desktop through a while back and I decided to give that one a try. Since it was old, I figured I'd probably better perform a firmware upgrade on it and when I did, the firmware upgrade failed on it and now that one is a dead stick. I'm considering the purchase of one of the new Buffalo routers that have remote desktop connectivity built-in to the router and see if that works. It's $129 but I figure if it saves me the headaches, then it'll be well worth it. Unfortunately I'm still not sure the router is the problem. I've scanned the logs on the router, but D-Link has a really crappy logging interface. It's not at all user friendly and doesn't provide any useful info at all. Unfortunately, I'm still not convinced that the problem lies with the router. I'm thinking it's something with Windows Remote Desktop, but I can't confirm that. Like I've said before, I'm still getting to the Windows Remote Desktop Web Connection page but when I enter the computer name or IP address of the machine I want to connect to, I still get the same errors I mentioned before. Thanks to all of you for any help and/or info that you can provide. Brian
    0 pointsBadges:
    report
  • Redwings3030
    Okay, news flash folks!!! I brought a laptop in that's just running a standard WinXP build (our company runs a modified version with all the goodies stripped out). I went to start > all programs > accessories > communications > remote desktop connection and was able to successfully connect that way!! HOWEVER, since my company's PCs don't have the remote desktop connection application installed, I can't use that tool. The way I have my PC at home setup is supposed to allow me to connect through a web browser using http://myhostname.dyndns.org/tsweb (of course, not my real address) but that's not working. Like I've said before, I've made sure that I have IIS installed and running, etc. and all that works fine because I'm getting to the login page for Remote Desktop, but beyond that, it's like the request is gettting lost somewhere trying to find the Remote Desktop PC inside my home network. Now here's another problem and this should probably be in a different post, but I'll put it here just for informational purposes since it's dealing with the same type of issue and may even be related. As an alternative solution, I installed VNC and have tried to connect that way as well. I forwarded the ports, etc. Well, when I try to connect using TightVNC through Internet Explorer, it finds and installs the java plugin, and gives me the password prompt. As soon as I put in the VNC password for my PC, I get an error "Network error: Could not connect to server: 25.101.xxx.xxx:5900" I have a feeling all this is somehow related but I can't figure out how. Thanks for the help everyone!! Brian
    0 pointsBadges:
    report
  • EZorro
    After reading all the replies and results I did not find anywhere that you verified that you have you properly set up RDP on your client system? 1. Make sure it's enabled by going to properties of My Computer and click on "remote" tab. 2. Then add your user account to the Remote Desktop security group on your client system. Last if you are running netmeeting in automatic mode this can prevent a TS or RD connection from another TS or RD system. DID you check your RD setup on your client system?
    0 pointsBadges:
    report
  • Owenmpk
    If your company has the company systems disabled from using RDC or others such as logmein then maybe you are violating policy. I know it is a pain in the butt I used to support 1400 remote users world wide and we were very restrictive due to federal regulations.
    0 pointsBadges:
    report
  • Stevesz
    I did, somehow, miss the part of your company disallowing logmein. (An aside to dwiebesick, it is a trivial thing to prohibit access to web services and web sites va firewall policies, given the proper firewall being in place in a corporate environment. Even many consumer routers/firewalls allow this type of blocking.) If your company is denying access to logmein, and I would presume other, similar services, and has removed Remote Desktop from your PC's, then i would suspect that they are addressing what they perceive to be security issues inherent in allowing such access. Issues they may be trying to address may include, and not be limited to, allowing access to home machines that contain malware that can be transmitted over networked connections, keyloggers, keeping corporate data within the corporate network other than in allowed situations, etc. For you to be bypassing these safeguards put into place by corporate IT would be, as owenmpk suggests, a violation of corporate policy. IT does not unilaterally put these restrictions in place just because they are on a power trip, or having a bad day, they are put into place as part of a policy derived through discussion with the various managers and departments that would be affected. Believe me when I say that these policies are not arrived at lightly, nor to be taken lightly. As part of my job, I have drawn up many such policies, some of which were accepted as written, some of which were modified to fit certain business needs, and some of which never saw the light of day. Bringing in your personal laptop and attaching it to the corporate network is also probably a no-no as well. I would suggest that, if you really need access to your home machine from work, you go through the proper corporate channels to gain such access, it it is to be allowed. Normally, access to the corporate network is allowed from home machines of workers or corporate laptops, if it is needed, via certain controlled methods (ie. VPN). In some cases, machines are scanned, and not allowed access unless they meet certain corporate standards, and said machines can be brought up to those standards automatically, with access then being allowed.
    2,015 pointsBadges:
    report
  • Thair
    One other thing that you can try is to load your logmein on a usb. that way it isn't being loaded onto you system. We have the same problem at the UTD campus. and if you can proxy server around your network try proxy ninja it should help you. Good luck
    15 pointsBadges:
    report

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to:

To follow this tag...

There was an error processing your information. Please try again later.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Thanks! We'll email you when relevant content is added and updated.

Following