|
Hello, I've been using DynDNS Free for about a year now and it's absolutely one of the best free services I've ever used. Anyway, I have a couple of Windows machines behind my router at home that I often control via RDP while away from home. To differentiate between the 3 of them I have them all set to listen for RDP connections on a different port. Then I forward the corresponding ports through my router to the appropriate computer. It works, but it's not really the best solution. It's annoying to have to remember which port refers to which computer. I saw that DynDNS Pro offers wildcard support and I think that's what I'm looking to do. Optimally, I would want to be able to say http://box1.myname.homeip.net to connect to box1 and http://box2.myname.homeip.net to connect to box2 and so on and so forth. So basically what I want to know is if the wildcard support offered in DynDNS Pro would allow me to have http://box1.myname.homeip.net point a specific port and http://box2.myname.homeip.net point to another. Any insight on this would be greatly appreciated! Thanks! |
|
Wildcard won't help - you still only have one public IP address, which is all the firewall has to go on (along with the port) when you connect. Very simply, when a connection is made between 2 computers the only things that are available to the server end (the device receiving the connection) are the remote (public) IP address and port and the local (public) IP address and port (along with the protocol). There is no way for it to know what hostname you used to make that connection. Alright, I kind of thought so. Thank you anyway.
May 24 at 08:08 PM
cpinola
|
