Can't Access Local Network Device such as a Printer, File Server, ETC

Follow

Comments

3 comments

  • Avatar
    2624

    This did not solve the problem with Verizon Actiontec router

  • Avatar
    rotblitz

    Sure, because this solution was thought for Netgear routers with Live Parental Controls enabled, as the forum section clearly says.  It is not intended to help with Actiontec or any other routers.

    Also, this has not much to do with your router, but with editing your local hosts file.  The related hosts file entry for Chris' example would be:

    192.167.1.XXX   printerxyz

    (I'm sure he meant 192.168.1.XXX however...)

    If you do have problems to connect to your internal device by name, post the complete plain text output of the following commands in a new thread and in another more appropriate forum section, so that we may see what's going on.

    nslookup  <devicename>

    ping  <devicename>

  • Avatar
    Alexander Harrison

    Hello,

    For non-NETGEAR routers, there is often a domain suffix (like routername.home) that you can add to your network's "VPN Exceptions" setting under "Advanced Settings" of http://dashboard.opendns.com/settings. Please check into your stats to look for requests ending in .home, .network, or .router and add ".home", etc to the VPN exceptions list to enable them to work locally with OpenDNS. 

    Best regards,

Please sign in to leave a comment.