Support

K-12 Forums

Talk with other K-12 network administrators in your state.

Or see all states.

Categories

Vanilla 1.1.4 is a product of Lussumo. More Information: Documentation, Community Support.

This discussion has been inactive for longer than 30 days, and is thus closed.

Router instructions: WRT54GS and Local Names

Bottom of Page

1 to 12 of 12

  1.  
    • CommentAuthorkirks11
    • CommentTimeApr 17th 2009
     permalink
    I've read through many discussions and haven't found a solution to my problem so...

    My setup consists of 2 XP PCs (wired) and a few laptops (wireless) that connect through the WRT54GS router. I followed the instructions for setting up the Linksys routers to use the OpenDNS servers (208.67.222.222 & 208.67.220.220) as Static DNS 1 & 2.

    Problem is when I do that and release/renew my DHCP to get the new settings, I can not ping by name the other machines on the LAN. Ping by IP works fine so the routing is functional. I've check for, and disabled firewalls on these machines as well.

    Obviously I'd like both the OpenDNS and Local names. Any help is greatly appreciated.

    Jason a.k.a. Kirks11
    • CommentAuthorcool110
    • CommentTimeApr 17th 2009
     permalink
    • CommentAuthorkirks11
    • CommentTimeApr 17th 2009
     permalink
    Says add domains to the exception list. I don't have a domain inside my LAN. Just Workgroup: WORKGROUP

    Tried adding it, but pings to the PC still reach out to the internet with my ISP domain attached.
    • CommentAuthorrotblitz
    • CommentTimeApr 17th 2009 edited
     permalink
    So look into your stats (Top domains) what the DNS lookups exactly have been for, and add these to your VPN exceptions. This could be the device/computer names alone, or with .workgroup appended, or the workgroup alone, or even different.

    "with my ISP domain attached"
    Not sure what you mean here. In case it means that you use your ISP's DNS servers instead of OpenDNS', then adding VPN exceptions to your OpenDNS dashboard configuration will have absolutely no effect, of course. You must use the OpenDNS servers to take advantage of any other features.

    Btw, I have a similar equipment as you, but all wireless (this is of no relevance for DNS), and do not face these problems. My router may well be aware what is internal and what is external, so does not forward internal lookups.

    If all does not help, adding the internal devices to your hosts files would help too, but this is not really the preferred option.
    Examples:
    192.168.1.55 myprinter
    192.168.1.56 pc1
    192.168.1.57 pc2
    192.168.1.58 wii
    192.168.1.59 iphone
    192.168.1.60 lt1
    192.168.1.61 lt2
    Note: you cannot use this for devices with DHCP enabled, only for devices with static internal IP address configured.
    • CommentAuthordiacon
    • CommentTimeApr 17th 2009
     permalink
    When you use the names of the devices on the network, you are using NETBIOS for name resolution. Unfortunately, NETBIOS resolution only happens if DNS fails. Since OpenDNS always resolves the name, even if it is to it's "I can't find that webstite" page, NETBIOS is never used.

    There are some creative options on the forums on how to deal with this problem. Most of them do deal with having to use static IP addressing.
    • CommentAuthorrotblitz
    • CommentTimeApr 17th 2009
     permalink
    @diacon
    "Since OpenDNS always resolves the name"
    Not so for the "domains" in VPN exceptions.
    This is what this is good for.
    But, nevertheless, it doesn't really make sense to forward to OpenDNS for internal resolution. This is wrong behavior of Windows (DNS/NetBIOS stuff).
    • CommentAuthorkirks11
    • CommentTimeApr 17th 2009
     permalink
    "with my ISP domain attached" Means that when I Ping XPPC2 from XPPC1 it pings XPPC2.hsd1.or.comcast.net, looking for it on the internet.

    This is also the top domain in my network history .hsd1.or.comcast.net

    I just tried adding hsd1.or.comcast.net to the private list. Pinging XPPC2 worked after a delay.

    Thank you for the help,
    Jason a.k.a. Kirks11
    • CommentAuthorrotblitz
    • CommentTimeApr 17th 2009
     permalink
    Ha, now I know what your problem may be.
    Do a "ipconfig /all" on your PC and you will find something like:
    Primary DNS Suffix: hsd1.or.comcast.net
    Connection specific DNS suffix: hsd1.or.comcast.net

    Go into the TCP/IPv4 settings of your connection and eleminate this stuff under "Advanced"/"DNS". If you still need this setting for whatever reason, add "hsd1.or.comcast.net" as VPN exception.
    • CommentAuthorkirks11
    • CommentTimeApr 18th 2009
     permalink
    I don't have hsd1.or.comcast.net entered anywhere. I don't see the section you're referring to.
  10.  permalink
    Local area connection properties >
    select Internet Protocol, click Properties >
    Click Advanced > select DNS tab
    • CommentAuthorjdmncc1969
    • CommentTimeApr 18th 2009
     permalink
    I am having the same problem. I can not access the local devices by name when using OpenDns. This seems to be a general problem, perhaps someone should write some instructions as to how to fix this? the VPN exceptions is just not a realistic option, especially with local devices still using DHCP as well. there has to be a better way.
  12.  permalink
    Why are VPN exceptions not a realistic option?

    There are no other instructions on how to fix this, AFAIK, aside from adding your network components to all the HOSTS file, and using static addressing. Actually, it is surprising to me that Netbios is even still around, but that is how Netbios works, and any complaints should be forwarded to Microsoft.

1 to 12 of 12

  1.  

This discussion has been inactive for longer than 30 days, and is thus closed.