|
Hi, I have a question that hopefully someone can answer. I have multiple PCs on my network and I have my router configured to route different external ports to port 3389 on each pc. e.g. pc1 - ip 192.1.1.1 external port 3389 internal port 3389 pc2 - ip 192.1.1.2 external port 3390 internal port 3389 pc3 - ip 192.1.1.3 external port 3391 internal port 3389 This allows me to remote desktop to different pcs without having to reconfigure the port on each pc. This works fine so long as I use the ip address (either internal or external). I can also connect to pc1 (external port 3389) using my dyndns host name. However I cannot connect to pc2 or pc3. I'm guessing that this is because of some problem with using a port other than 3389 through dyndns ? Just wondering if anyone has got remote connections to multiple pcs working through dyndns and how they did it ? Thanks oops, sorry I didnt realise comments were not globally visable. Just have a single router, EnGenius 9855g. I can connect IF i use the internal ip addresses, 192.168.x.y I can connect to the primary pc if I use the external ip address, but I cannot connect using my dyndns hostname. – lbassom yesterday I have the router setup to update dyndns if the ip changes. I also have the router set to forward the external ports to port 3389 on the different internal ip addresses so I don't have to reconfigure the remote desktop port for each pc. Everything works fine if I use ip addresses, either internal or external. I can also use the hostname to connect if i'm connecting from another pc on my home network. The problem seems to be if I try to connect from a pc that is not on my home network, then I can only connect if I use the ip address, not the host name. – lbassom yesterday Edit 08/26/2010 My router allows me to forward an external port to a different internal port, so I have the following set up: pc1 external port 3389 to internal port 192.168.1.1:3389 pc2 external port 3390 to internal port 192.168.1.2:3389 pc3 external port 3391 to internal port 192.168.1.3:3389 This allows me to remote desktop to each pc without having to change the port on the pc. I can remote connect if I use the 192.168.x.y address, I can also connect if I use the external xxx.yyy.zzz.aaa address. But if I try to use the dyndns hostname (which maps to the correct ip address) I cannot connect. But, just to add to the confusion, if I use the dyndns hostname from one of my local pcs I can connect to other local pcs (I don't know if something odd is going on and it's not really using the external ip address because it has figured out its all on the local network??) I have checked the ports are open and looked through that guide. The connection is there as I can connect using IP addresses, there's just something messed up with the host name somewhere. Thanks |
|
The combination of symptoms sounds confusing and strange. From what I can see, connection attempts to your IP address on ports 3390 and 3391 time out. Either the port mappings are incorrect or the relevant computers have software firewalls blocking the traffic (such as Windows Firewall). However, connections to your IP on port 3389 seem to be properly established without any problems. Are you sure you have tested from outside your network? Not sure where you are getting that impression, I never said anything about getting timeouts. The problem I have is that while I can connect using the ip address I cannot connect using the dyndns hostname.
Aug 27 at 05:44 AM
lbassom
|
|
Comment notification only goes to the person who made the post you're commenting on. If you use comments others will not know you've added information. It is better to edit your question. You can only forward any port to a single system. That means you can only forward Does your hostname resolve to the WAN IP of your router - it sounds like it doesn't. Finally, can you answer the questions in the second paragraph please. |
Not sure where you are getting that impression, I never said anything about getting timeouts. The problem I have is that while I can connect using the ip address I cannot connect using the dyndns hostname. If you want us to have a look (trying to identify what's different when using the hostname and when using the IP), please post your hostname. |
|
Hi, seems to bee a routerproblem. Your configuration works fine in my Environment. extern mstsc \...dyndns.org:13391 --> intern \pc1:3389 extern mstsc \...dyndns.org:13392 --> intern \pc2:3389 Using FRITZ!Box 7270. Cu Jörg |
|
Do you only have a single modem or router? Can you expand upon your question, since at one point you say it all works, then you say it only works for the first computer (the one using Have you checked with the open port tool to see if the ports show as open and have you worked through this guide? Just have a single router, EnGenius 9855g. I can connect IF i use the internal ip addresses, 192.168.x.y I can connect to the primary pc if I use the external ip address, but I cannot connect using my dyndns hostname.
Aug 25 at 02:00 PM
lbassom
I have the router setup to update dyndns if the ip changes. I also have the router set to forward the external ports to port 3389 on the different internal ip addresses so I don't have to reconfigure the remote desktop port for each pc. Everything works fine if I use ip addresses, either internal or external. I can also use the hostname to connect if i'm connecting from another pc on my home network. The problem seems to be if I try to connect from a pc that is not on my home network, then I can only connect if I use the ip address, not the host name.
Aug 25 at 02:42 PM
lbassom
|