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: Brian Hagemann on Apr 22, '05 11:41:49AM

Seeing this hint actually prompted me to register after 2 years of just reading the site! :)

Just to add my experience... this issue drove me CRAZY a year ago. I host my vanity website internally at home and was developing in Apache, mySQL and using MoveableType at the time. I experienced the same issue that when i turned on port forwarding (80) to point to my desktop, people outside my network could get into the site and MT worked fine, but I could no longer do testing internally. Using the local ip was of no help because of some issue with virtual domains in apache and the relationship with MT... the site would just break or parts would misbehave because they were expecting the referring URL to include the 'real' domain "www.sitename.com" not an IP address.

Because I had the need to plug in an ethernet printer for home use, I replaced the Airport with a 4port Linksys WRTg router. To my surprise the problem completely disappeared. NOW i can get to the website and blog via www.sitename.com from inside OR outside the house. At my office I have a dLink router. Similar need here for port mapping for incoming requests but need to do internal testing of same service. Works FINE.

My conclusion was that the Airport isn't routing properly. Now I don't claim to know the details of routers and how they 'actually' work... but I do know that the Airport was unable to handle this situation and two different other routers work as I would have expected. BTW I had the same problem on both an original Airport and a newer Airport Extreme BS.



[ Reply to This | # ]