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 show...
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\
Hi, with the laptop,
SMB 1 Client and server are turned on. Auto disconnect is off.
The home network is showing as Private.
I've overridden the AV/ security.
\\ IP - still not work, but \\hostname does! Says 'I've mis-spelt the IP.'
Security back on and the same occurs. Plus it is intermitent, as I was happily using the mapped drive yesterday.
The AV security log only lists blocking 'searchapp' and 'backgroundtaskhost', but each only once in the last 5 dyas, so that doesn't tally with trying to connect.
I've remapped the drive letter to the hostname and that's working again.
The problem is it's all intermittant. Works fine for a few days, then doesn't.
Thanks
Petes4 wrote:
Says 'I've mis-spelt the IP.'
Obviously that will happen if you type the name wrong - For instance, \\10.0.015 instead of \\10.0.0.15.
It can also happen if you aren't using the correct user credentials. For instance, if you try to access the NAS data volume w/o admin credentials, or if you try to access a private share using the wrong user credentials. So maybe check the Windows Credential Manager, and make sure you have the same credentials entered for both the IP address and the hostname.
Being unable to connect via the host name is a common problem to which I have not determined a solution except for the use of the HOSTS file. Since that isn't working for you, make sure you made a valid entry in the file. A common error is to follow the examples and leave a # at the beginning, which comments out the line.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
