x
all questions login
General DNS & Domains Dyn Email Update Clients Dyn Developer

I am trying to remote desktop to my pc that is on a router connected to a modem and am having probelms. So I found this site and I just setup the Free Dynamic DNS service. I also installed the client software to update with my new IP address. Everything seems to be working but when I try to remote desktop to my pc it doesn't connect. I setup port forwarding on my router and modem and nothing. I entered my host name in to a browser and it points to my modems setup page. This is correct? What am I missing.

Steps I took:

and I am getting nothing. Any idea?

UPDATE

I didn't forward 3389 because I changed it to a different port number. I tried remoting from a PC on my Lan and still nothing.

UPDATE

I tried using the port forwarding tester and I get timed out everytime. Even port 80 gets timed out.

UPDATE

Ok I am able to connect in side my network using the ipaddress my router gives me but if I try using my DNS hostname it doesn't connect. I also had someone out side my network try and still nothing. It must be my modem. It is an ActionTec GT701-WG wireless router. I turned of DHCP. Is there any other setting that maybe creating a problem?

more ▼

asked Mar 22 at 01:52 PM

kenshinofkin\'s gravatar image

kenshinofkin
1 1 1 4

Originator has not returned to the thread in over a month. Closing to stop the forum bot bumping it.

Apr 23 at 12:41 PM Cry Havok ♦
10|600 characters needed characters left

3 answers:

You did forward port 3389, did you? Can you do RDP from within your LAN, from another PC?
Edit your message to elaborate on this.
Also confirm that you want to use Remote Desktop Web Connection using IIS with the browser instead of normal remote desktop with mstsc.exe.

(RDP using port 3389 is the reason why it doesn't work from a browser without explicitly specifying the port, because browsers use HTTP (port 80) by default, and this is what your modem's setup page may be listening on. Therefore port 80 cannot be used for RDP.)

Also, you may check the other Q&As tagged remote-desktop to possibly find tips.


Update: Getting it to work from within your LAN (PC to PC) is a kind of prerequisite before being able to connect from remote. So, start with sorting out this. See if your server PC is listening on the specified port with e.g. telnet 192.168.1.77 1234 (example only. Use the IP address of the server PC and the port where the RDP application should be listening to).

more ▼

answered Mar 22 at 02:03 PM

RotBlitz\'s gravatar image

RotBlitz ♦
27.9k 4 14 94

10|600 characters needed characters left

You'll need to forward 3389 from the modem to the router's WAN IP and then from the router to the IP of the PC.

The subnets on the router must be different. That is, if you're using 192.168.1.x/24 for the router to PC link you must use something else, like 192.168.0.x/24, for the modem to router link.


As RotBlitz said, and as is covered here, you must get it working from inside your LAN (using the LAN IP) before you try from outside your LAN. If you've read the other Remote Desktop questions, you'll presumably have checked:

  1. The Remote Desktop service is enabled and running (try netstat -an -p tcp and look for the port number you're using)
  2. The Windows firewall has an exception enabled for that port, or the firwall is disabled

When it works inside your LAN, what tool (remote desktop client, web browser etc) are you using and what port?

more ▼

answered Mar 22 at 02:10 PM

Cry Havok\'s gravatar image

Cry Havok ♦
52k 13 26 222

According to the setup link he provided, he may want to use "Remote Desktop Web Connection using IIS" via browser, not mstsc.exe, so he theoretically can use any available port. Good point with the Windows firewall. I tend to forget it, as I use another...

Mar 22 at 09:54 PM RotBlitz ♦
10|600 characters needed characters left

Let's start out with something simple: Turn the port back to 3389.

Fix the networking issue (same network on both sides of the router.) as described above too, and turn off port forwarding on your DSL modem. By definition you shouldn't be doing ANY port filtering at the DSL modem if you are going to do it at the router. Your DSL modem should be configured to simply pass ALL traffic to your router, and let your router handle all decisions.

more ▼

answered Apr 06 at 05:10 PM

Edward\'s gravatar image

Edward
21 3

10|600 characters needed characters left
Your answer
osqa.question.ask.tags.preview.show

© 1998-2011  Dynamic Network Services Inc.  -  Legal Notices  -  Privacy Policy  -  Contacts     

Powered by Qato