NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
WNDR4500 / Windows + Linux + NAS / cannot always reach by hostname
My network generally works well. I've got DHCP handing out IP addresses and a few fixed IP's for printers and NAS devices. I've got the following devices on my network all managed through wired and wireless connections:
- Windows PC's (mostly Win7)
- Ubuntu
- NAS (Buffalo Storage, WD Cloud)
- iPad / iPhone
The biggest thorn in my side is the "random" loss of capability to access machines via their hostname (e.g. KITCHEN-PC, NAS-A). I am not running a Windows Server. All PC's connect either wirelessly to a WAP or through a hardwire connection to a switch that is hardwired into the Netgear WNDR4500.
Some days (weeks?) I just lose the capability to reach shared resources (folders, NAS) on the network by hostname. The hostname could be the name of the Ubuntu box, the name of the NAS, or the name of another PC. Usually when one goes, they all go - I cannot connect to any of them by hostname. Typically, this happens on a laptop that I take back and forth from work. At work, everything is fine; all devices can be accessed by hostname. At home, not so much. For the last week, none of my devices could be reached by my laptop using their hostname, but all of them can be reached by their IP address. Yet, all of the attached devices on my WNDR4500 have names associated with their IP addresses.
Is there a feature in the WNDR4500 that provides this name resolution service? DNS? WINS? ... ?
What happens if you try nbtstat -a <hostname> from your work laptop to one of your machines? Check nbtstat -r afterwards to see if the counters increase.
Can you look at the advanced adapter settings on your laptop and see whether a WINS server address is configured? You probably also want to make sure that NetBIOS over TCP/IP is enabled.
You may also want to look at the Windows registry for the NetBIOS node type. I believe the key is HKLM\SYSTEM\CurrentControlSet\Services\NetBT\Parameters\NodeType. The values are explained at this link.
12 Replies
Does this only happen with your work laptop, or do other machines experience this symptom, too?
AFAIK, the WNDR4500 is not a WINS server, nor does it participate in Windows name resolution. In a home setting, Windows name resolution is serverless and is handled through the use of broadcasts. If you have multiple IP subnets, then name resolution will not work. Most home networks are a single subnet. I assume yours is, too.
In a work setting, Windows name resolution is often handled by an Active Directory or a WINS server. I kinda wonder if, perhaps, your work laptop is trying to contact a work server for name resolution? You can try using nbtstat at the Command Prompt to troubleshoot name resolution problems. Wikipedia has a page on it (link). nbtstat -a <hostname> will attempt a name resolution. It's equivalent of nslookup for Windows names. nbtstat -r will give you stats on resolution requests performed by broadcast and by server. If the server count is non-zero, then your laptop is probably trying to contact a server. nbtstat -c will display the local name cache.
This article is helpful for understanding Windows name resolution (link).
Hmmm... makes sense...
I got this...
>nbtstat -r NetBIOS Names Resolution and Registration Statistics ---------------------------------------------------- Resolved By Broadcast = 0 Resolved By Name Server = 0 Registered By Broadcast = 0 Registered By Name Server = 0and
>nbtstat -R Failed to Purge the NBT Remote Cache Table.
Seems like this PC is living in a lonely world. It cannot find anything and I cannot purge the table. I would hope that a purge would force it to await broadcasts and rebuild the table. Any ideas?
