|
Upon setting up Internet Guide and enabling it with DynDNS Updater I have now lost the connections between devices inside my local network. Can't share printers, share drives or print to my WI-FI print server. Once I disable Internet Guide on all PCs everything comes back to normal. I'd like to use Internet Guide to filter the content for where others may surf in my network, but I need to be able to have access between devices. Especially printing. Where am I going wrong? Any advice would be appreciated. Thanks -D |
|
The problem is that IG replaces your DNS servers, so if you're using DNS on your LAN then configuring IG on each host will break that. What you'll want to do is configure it on your DNS server (or proxy server) instead. |
|
How were you resolving DNS queries prior to using Intenet Guide? If it was from a local DNS server, that server was getting DNS answers from somewhere else. Now that your local machines are configured to use Internet Guide they are also configured to use DynDNS resolvers at IP addresses 216.146.35.35 and 216.146.36.36. Those servers don't know (and will never know) about your local services. One way around this is to have a HOST table on each machine. Windows PC's HOST table is found at your "windows" folder under \system32\drivers\etc . There is a sample file there. A second way, which is what I have done was to shut down the local DNS server (one more ancient machine out of the equation) and point each PC to DynDNS's Internet Guide resolvers. Then configure an update client on each machine and have it update just its own name. Create A-NAMEs for each machine under your CUSTOM domain name HOSTNAMES under the Host Services. This allows control of each machines surfing abilities without affecting any others. So, each machine has a name GS1, GS2, etc. Each machine gets DNS from 216.146.35.35 and .36.36. Each machine has a DynDNS updater configured to update and report just its own name. Hope this helps. |
|
It is normal that you break local name resolution when using external DNS server addresses on local devices. Please read my explanations on how to easily overcome this. The best approach is to configure the IG DNS server addresses on the router (only), and then disable it in the Updaters on the local computers. Also, it is important that you configure NXDOMAIN responses in your defense plan, so that Windows has a chance to fall back to NetBIOS name resolution after unsuccessful DNS lookups. Don't forget to click the check mark, if this was helpful, so that we know and the matter can be treated as answered.
Mar 06 at 01:56 PM
RotBlitz ♦
|
|
I have the router configured to use the external DNS servers IP addresses and let the intenal devices get the information form the DHCP server on the router. With that said the inside still sees each other and the outside world is controlled by the router. RotBlitz has the correct and easies solution. |
Originator hasn't revisited the question in over a month. Closing to stop the forum bot bumping it.