Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[timandjulz]

First problem:
Computers get an IP address via DHCP and the router shows their names.  But the DIR-655 does not act as the DNS server as it should.  That is, it does not resolve the IP address when given a computer name.

Example: mylaptop gets ip address 192.168.0.195.  The router shows the name "mylaptop" in its dhcp client list.  mydesktop gets ip address 192.168.0.196 and has primary DNS of 192.168.0.1.  "ping mylaptop" does not resolve.

Second problem:
I thought I would fix this by setting the local domain name on the router.  Thus I would "ping mylaptop.mynetwork.org" or just "ping mylaptop.mynetwork".  When I set the local domain and save, the router restarts (acceptable) but the domain name is empty (unacceptable).

How can I fix these two problems?
Thanks,
Tim

[ttmcmurry]

The 655 isn't a DNS server, so it would not be possible to ping your system name.  The 655 *is* a DNS relay but don't confuse it with a DNS server.  It's not a router's place to be a DNS server anyway.

Now if you pinged your system's IP address, it would work fine.  IIRC, the names you see on the 655 is the resolved netbios name of your computers.  If you've ever looked at Mac or iPod systems in that same list, you'll notice their names are empty (unless on the Mac you set up PC File Sharing).  PING cannot resolve via netbios or WINS, it must do so within DNS.

There is *very* different behavior in every edition of windows regarding system names and whether or not it's using DNS, WINS, or NetBIOS for a specific lookup context (for example if you typed \\server in windows explorer, it has different lookup methods than using ping).  Ping.exe however hasn't changed much over the years as it still uses DNS for resolution.

If you nbtstat to search for your laptop from your desktop, you would be more successful.

Alternatives would be to find an old computer (free), install Ubuntu on it (also free), and enable its DNS & DHCP server.  Modify your 655 to disable DHCP and make sure DNS relay is enabled.  Point your server's DNS relay to your 655's IP address and make sure your DHCP scope options agree.  If you're going to use a real DNS suffix, make sure it's *.local (e.g. myhome.local) unless you plan on registering the domain with a public DNS registrar.

You can do the same with Windows Server Standard but that costs more money than free.  And Ubuntu can do it just as well.

My last suggestion is to (when it's released) purchase Windows 7 on all of your computers and use the HomeGroup feature to locate other computers within your home network and easily maintain file, printer, and resource sharing.

[timandjulz]

Why would there be an option to configure the local domain name for the router if the router does not provide basic lookups on the lan?  Every other router I have seen that has a local domain name configuration also provides lookups on the lan.  (DNS?  netbios? something else?)

The documentation states that wireless devices will be given the domain name configured in the router.  What would the point of giving a consistent domain name be if there is no ability to use it via DNS?

Confused

Thanks,
Tim

[ttmcmurry]

Please understand -- If you set your 655 to use mynetwork.org as your suffix, then the DNS server at mynetwork.org would need to be notified of the ip address and host name assigned to that computer.  Since the 655's DHCP facility can't update the DNS records on mynetwork.org's server, then there is no possibility that would ever work.  Hence the need for a local DNS server.

I hate to say it but you need a clearer understanding of what DNS does, how to use it, and where & what it applies to.  I'm not being mean, only realistic.  Someone who understood DNS wouldn't ask a question like that. 

Regarding your other points:

A local domain name is completely optional- that's actually a DHCP option (is forwarded to a client when as its connection-specific dns suffix).  If you leave it blank, the 655 will assign a suffix provided by your ISP, if any. 

It's as optional as the "Host Name" field under Setup-> Manual Internet -> Internet Connection Type (DHCP).

Please understand that Windows has mechanisms to detect other computers on the network without a DNS server present on your local subnet.  99.9% of home systems behind a router work without any issue in this manner - all the way down to Windows 3.11.

I can't speak for other vendors products-- but if you look up dd-wrt (a replacement firmware for Linksys and other similar routers), as advanced as it is over stock Linksys firmware even it doesn't have a "proper" DNS server, it only maintains a cache with local and isp dns servers.  Meaning, if you don't have a DNS server on your private subnet, the router won't know the DNS names of your local systems.  (link)

If you want to know what systems your Windows computer is aware of via NetBIOS, drop to a command line and type "nbtstat -r" and it will show you the list of systems and workgroups for which it knows on your network. 

[timandjulz]

ttmcmurry, I can see why you would think I don't know how the DNS protocol works.  I do.  The help on the router gives an example of "mynetwork.net" and I was just going with that.

What I was trying to get across is that I tried to use a local domain name with and without a top level domain specified.  i.e. I tried "mynetwork" and "mynetwork.net" and in neither case did the router save the setting.

My real question is why doesn't the router save the local domain name configuration?  Regardless of its purpose, the configuration does not get saved.

Cheers,
Tim

[EddieZ]

ttmcmurry, I can see why you would think I don't know how the DNS protocol works.  I do.  The help on the router gives an example of "mynetwork.net" and I was just going with that.

What I was trying to get across is that I tried to use a local domain name with and without a top level domain specified.  i.e. I tried "mynetwork" and "mynetwork.net" and in neither case did the router save the setting.

My real question is why doesn't the router save the local domain name configuration?  Regardless of its purpose, the configuration does not get saved.

Cheers,
Tim

The router is not the one saving the local domain name. The local domain names are broadcasted through netbios protocol by the clients and used by the router. There is a setting in http://192.168.1.64/Basic/Network.shtml that gives you some control over netbios broadcasts. If those settings are correct (they are available only when using DHCP since on bridge mode the network broadcasting is performed by another device).

The domain prefix does not have anything to do with this, by the way. This is not a DNS issue.

Just read through this thread with similar problems. http://forums.dlink.com/index.php?topic=3811.15

[timandjulz]

I upgraded my firmware to 1.31NA and the problem is solved.  All windows machines ping each other by name and my Ubuntu Jaunty machine worked after installing winbind.

The problem was caused by my router not being able to save settings correctly (as originally reported... would reboot after changing settings and the new settings would be lost).  I reset the router (reset button on back) and upgraded the firmware (for grins) and the problem went away.

As I said before, this is a common functionality found in all routers I have ever owned so was a bit surprised it didn't work.  I didn't experiment with settings so can't say if there was something specific I changed.  But my network configurations are now:

Turned on:
o. Always Broadcast
o. NetBIOS Announcement
o. Learn NetBIOS from WAN
o. Under NetBIOS node type: Mixed-mode (Broadcast then Point-to-Point)

I hope this information helps someone else in the future.

Cheers,
Tim

[EddieZ]

"Learn netbios from WAN" might give you some security issues. It permits NetBIOS traffic from Any to Any from the WAN to the LAN and is usually only necessary if you deploy the DIR inside your perimeter Internet firewall.

[timandjulz]

Good tip EddieZ.  I disabled and it still works.

New configurations that are checked/turned on:
o. Always Broadcast
o. NetBIOS Announcement
o. Under NetBIOS node type: Mixed-mode (Broadcast then Point-to-Point)

[EddieZ]

Good tip EddieZ.  I disabled and it still works.

New configurations that are checked/turned on:
o. Always Broadcast
o. NetBIOS Announcement
o. Under NetBIOS node type: Mixed-mode (Broadcast then Point-to-Point)

Unless you have a WINS server you can stick with broadcast only. But mixed mode does not influence the setup.

[timandjulz]

SOLUTION:
I confirmed that "Broadcast Only" configuration works.  I will close this topic after this post but wanted to confirm the final working configuration AND thank EddieZ for his helpful contribution.

First off, if you have a similar problem with configurations not saving then perform a hard reset and consider upgrading your firmware.

New configurations that are checked/turned on:
o. DHCP Server is on
o. Always Broadcast
o. NetBIOS Announcement
o. Under NetBIOS node type: Broadcast only

Cheers,
Tim