Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Solve a Remote Desktop Client port forwarding problem' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Solve a Remote Desktop Client port forwarding problem
Authored by: mkutny on Apr 22, '05 11:48:07AM

I experienced something similar with an older D-Link router I had (although my newer routers - both D-Link and Linksys - haven't exhibited this). It wouldn't let you "loop back" to the external IP (nor its dynamic DNS entry). I did find that some simple entries to the hosts file took care of this (pointing the domain to my internal address), but I had to comment them out on my laptop when I was on the road (otherwise the mysite.dnydns.org would be looking for an IP on the LAN). Apache was listening on its local IP, so whether a request came via the router or directly on the LAN, it still worked as long as the host header was "mysite.dnydns.org".

One last note: you can allow Apache to handle multiple IPs for individual and multiple sites, using virtual directories and hosts. It involves some more entires to add to the httpd.conf, but it will work.



[ Reply to This | # ]