Only being able to connect in Win 7 using the IP address

What happens if you enter https://EricNAS/admin in your browser window?

Also, try opening a command box and enter "ping -a 192.168.0.3" and see if it reports a host name. Note that the -a needs to be lower case.

after I did the ping -a 192.168.0.3 the hostname started to show up (but in all caps "ERICNAS".
But after a reboot I lost it again. I tried to change the Hostname to ERICNAS on the Netgear ReadyNAS NV+. That did not help.

This is not case sensitive, so EricNAS, ERICNAS, ErIcNaS should all behave the same. No need to change the hostname.

A similar test is to ping EricNAS by name. (ping EricNAS).

When you are seeing the hostname, then you should be able to use it to access both Frontview and with windows explorer. So if you see the hostname again with ping -a, try the https and \\EricNas\folder tests, and see if it works then.

yes the ping ericnas is working and I can access both Frontview and with windows explorer.
But why do I keep losing it after reboot?

Maxum1965 wrote:
yes the ping ericnas is working and I can access both Frontview and with windows explorer.

Good. So that narrows the issue down. Everything is working, but discovery is slow.

Maxum1965 wrote:
But why do I keep losing it after reboot?

The PC has to learn the host name from the network every time it boots up. This shouldn't be taking that long, but obviously it is.

1. can you estimate about how long you need to wait after reboot before the name is found?
2. If you go into control panel, and open "network and sharing center" is the network type set to "home network"
3. If you then click on "advanced sharing options" on the upper left, is "network discovery" turned on?

yes, the network discovery is turned on.

yes , the network type set to "home network".
it does not find it unless I ping it.

Ok. This is on a wired connection? Or wireless?

Also, you might try turning off the Windows firewall (or any third-party firewall you have installed). Turn off real-time virus protection while you are at it. Then test again. Probably you will need to reboot, disable stuff, and then try it (avoiding the initial ping).

We do now have a workaround (annoying but functional) - which is to ping the NAS after rebooting the PC. So there is some progress I guess. Whatever is causing this might also interfere with finding other devices (network printers for instance) so it is worth tracking down.

Its on both wired connection and wireless. but mostly on the wireless.
I will try turning the stuff. and see what happens.

Thanks for your time and help on this :)