NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS NV+ v2 - Windows 10 not finding connecting
RAIDiator 5.3.13 (Says up to date.)
Seems to coincide with recent Win 10 updates, but getting unreliable connections to the drive. Was fine before.
No problems getting to the admin webpage and shows up under media connections in explorer, but trying to connect struggles.
I've added the name and IP to HOSTS, but it still comes up 'can't find the name.' Sometimes the IP
I've added SMB 1.0 Client.
Sometimes a reboot solves it, but not always.
This time I've rebooted and it doesn't recognise the name again, but I can connect with the IP address.
This is the same on 2 PCs and on 1 laptop, so I think it's Win 10 and Raidator 5.
Any ideas? Thanks
6 Replies
Replies have been turned off for this discussion
If the hostname and the associated IP address is in the HOSTS file, then it should always resolve the hostname to that IP address. The HOSTS file is checked before the PC tries any other method to resolve the name.
Are you trying to access a particular share ( \\hostname\sharename) , or are you just entering \\hostname in the file manager address bar?
When it fails, can you ping both the IP address and the hostname using CMD?
Hi, StephenB , I had to wait for it to fail again, which it just has. Doesn't fail every bootup.
\\hostname - fails
\\hostname\folder - fails
\\IP - works
mapped drive to \\hostname\folder - fails
Media server with hostname in explorer - works
ping IP - works
ping Hostname - resolves and works.
//hostname/admin - opens web admin page
HOSTS seems to be associating name, except when trying to directly access in explorer.
Currently on Win 10 v2004, with v20H2 waiting to go. Not sure if the upgrade will help or hinder. This is on an old HP workstation.
I've booted up my work laptop. it doesn't have the HOSTS set, but drive is mapped.
mapped drive to \\IP - fails
\\IP - fails
ping - IP -works
//IP/admin - opens web admin page
Media server with hostname in explorer - works.
I've rebooted the NAS and both PCs. The workstation is now working, but the laptop is the same. The NAS is on a power schedule so shuts down each night.
Any ideas? Diagnose finds no errors. Thanks
Petes4 wrote:
I've booted up my work laptop. it doesn't have the HOSTS set, but drive is mapped.
mapped drive to \\IP - fails
\\IP - fails
ping - IP -works
//IP/admin - opens web admin page
Media server with hostname in explorer - works.
This sounds like the SMB 1 client isn't enabled on the work laptop (or is blocked by a work security policy). My company allows SMB 1 only if I am connected to the corporate VPN. Some internet security suites also block SMB 1 by default (Kaspersky for sure and I think Avast might as well).
Another possibility is that your work laptop is classifying your network as public.
Petes4 wrote:
HOSTS seems to be associating name, except when trying to directly access in explorer.
That contradicts Microsoft's guidance ( https://support.microsoft.com/en-us/help/172218/microsoft-tcp-ip-host-name-resolution-order ). The HOSTS file is always checked first.
The format is to put the IP address first, followed by the hostname. At least one space is needed in between. Note that # indicates a comment, so anything in a line after a # is ignored. The file has to be in %WINDIR%\System32\drivers\etc\
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
