|
|
People, please understand the problem...
Admittedly few people will need this hint- however, it is the absolute best solution for the situation described by the author (and mine as well).
Some routers, including my Netgear 814 while providing port-forwarding services cannot or will not allow LAN clients to access these forwarded services by domain name. IE: example.com forwards into my LAN through my Netgear 814, final destination is my iMac. Everything is peachy keen from work or anywhere outside the home LAN. HOWEVER, inside the home LAN attempts to access example.com from my iBook fail. I was solving this problem by adding an internal LAN IP address for example.com to my /etc/hosts file. The problem with this approach is that everytime I go to work, I must comment out the /etc/hosts entry in order to access example.com. With this hint, with the DNS server running on the iMac at home, I simply switch Network Locations from the Apple menu, when home and away (I have to do this anyway), and voila everything works perfect. Again, few people will need this hint, but all this talk of NetInfo and /etc/hosts is not entirely relevant to the situation described in the original post, nor in mine. Cheers. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.10 seconds |
|