|
Dyndns has been configured on my Billion router and Dyndns Updater has been installed on my server. I can access the server via RDP on the local network but not from outside. I have configured port forwarding to forward port 3389 to my servers ip 192.168.137.1 . I'm still unable to connect. Moved comments into body of question
|
|
You don't need to use any of these services to run Remote Desktop. Historical Edits
Edit No, if you're trying to use a Remote Desktop client you only need 3389/TCP open. You are testing with a Remote Desktop client and not a web browser I hope? I'm currently running on a 3G connection on a ADSL/3G router.
Mar 24 at 09:43 AM
frutek
My appoligies Havok. I have moved the line to ADSL to make things easier. Now I get a ping reply from the dns address. But I'm still unable to connect remotely.
Mar 25 at 06:27 AM
frutek
My router wan ip is 41.246.xx.xx, my host name resolves to the exact same ip. I dont have any other routers or network devices. The firewall has been turned off. NAT is enabled on my router,could that cause an issue?
Mar 25 at 07:50 AM
frutek
Yes I have. Port 3389 is open, but 80 isn't. Do I need port 80 to be open?
Mar 25 at 09:52 AM
frutek
|
|
Well, |
|
I'm having the exact same problem. DSL connection, PortForward config utility opened the port on the router AT&T 2wire router Firewall in Server 2008 Standard is OFF http://checkip.dyndns.com:8245/ -- resolved the correct IP Open Port Tool -- found the port OPEN 3389 I can ping 127.0.0.1 w no errors I can RDP through the LAN "SERVERNAME" with no issue running DNS Updater 3, as recommended for Server editions on windows.. help!!! If i switch my router to DMZ zone, it works... but then i cant access my database server on the lan.. please help.. Please, ask your question as a question, not as an answer to somebody else's question.
Apr 08 at 10:11 PM
Cry Havok ♦
|
It has been more than a month since the originator last visited this thread. Closing to stop the forum bot bumping it.