0

Using Windows Server 2008 R2, I have configured a simple remote desktop access and IIS, then I used my external IP address to ensure that the default IIS web page is reached.

I connected localy to the server using Remote desktop and succeeded. Then, I tried RDP with the same external address used to connect to the IIS and failed. FYI, I am using dynamic-dns.

I have also tried using the domain name: since mydomain.com is both the name of my machine and also the name of my web site, and mydomain.com resolves normaly the IP address.

I have tried to find in Remote desktop Session host configuration in Administrative tools, if is there a way to configure dynamic IP but failed, hard to find on google too.

Is there an idea on this please ?

Sami-L
  • 253
  • 2
  • 6
  • 17

1 Answers1

3

It sounds like you need to port forward TCP port 3389 to the server in the router/firewall.

joeqwerty
  • 109,901
  • 6
  • 81
  • 172
  • I already configured the router -> firewall -> Virtual Servers -> fixed local IP address of the server -> to allow the RDP on its port number. You remember the port number changing question ? – Sami-L Nov 06 '12 at 18:16
  • Have you verified that the server is listening on that port for RDS? – joeqwerty Nov 06 '12 at 18:20
  • Yes of course, do you remember Firewall predefined rule question, when it was question to change port number and create a new rule with the new number. – Sami-L Nov 06 '12 at 18:22
  • Yes, but that only addresses the firewall. RDS has to be configured to listen on the port. Have you done that? When you connect internally what port are you connecting to? – joeqwerty Nov 06 '12 at 18:27
  • I have changed the port number in the registry, and I use the same port to connect localy, it works. – Sami-L Nov 06 '12 at 18:29
  • Also, I just made a telnet from my client machine to that port number, and failed. – Sami-L Nov 06 '12 at 18:30
  • Ok, then check the firewall rule and see what network profile it's set to allow for. Also, what network profile is the NIC on the server using? – joeqwerty Nov 06 '12 at 18:30
  • Firewall rule is created only for TCP not for UDP and is set to allow all profiles. Sorry for the second question I cannot understand your meaning. – Sami-L Nov 06 '12 at 18:37
  • It would be great if you transfer this discussion to chat since I have not enough reputation. – Sami-L Nov 06 '12 at 18:40
  • OK. Are you sure that when you're connecting internally that you're connecting to the new listening port? How are you specifying the port when you connect? – joeqwerty Nov 06 '12 at 18:41
  • Yes, I am currently connected internally to the fixed IP address 192.168.1.10, when connecting I provide the next: "192.168.1.10:xxxx" – Sami-L Nov 06 '12 at 18:44
  • And when you connect externally are you connecting like x.x.x.x:yyyy, where x.x.x.x is the public ip address and yyyy is the new port number? – joeqwerty Nov 06 '12 at 19:24
  • Yes, of course. – Sami-L Nov 06 '12 at 19:36
  • thank you very much for your valuable help, I've learned so much from you, finaly found the dysfunction source, it is caused by the recently changed RDP listening port, which had to be set the same not only in the local port zone but also in the public port zone in the router firewall port forwarding. – Sami-L Nov 06 '12 at 20:02
  • OK, so it was a router/firewall issue. Good to know. Glad you got it working. cheers :) – joeqwerty Nov 06 '12 at 20:07