NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CFE
Jan 10, 2016Aspirant
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...
- Jan 11, 2016
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.
CFE
Jan 11, 2016Aspirant
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 = 0
and
>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?
Retired_Member
Jan 11, 2016Try replacing the switch!
- CFEJan 13, 2016Aspirant
Replacing the switch is probably not the answer... all other PC's are OK.
- Retired_MemberJan 13, 2016
CFE wrote:Replacing the switch is probably not the answer... all other PC's are OK.
I only suggested it because, I also had issues trying to reach network devices when going gigi years ago and randomly not able reach NAS folders. Problem was 3 netgear switches (those white plastic POS) replaced with blue metal GS108 and never a had another problem.
Try power cycling the switch next time.