NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
User field in the ReadyNas NV+ to short for windows 10 live account
My 10+ year old windows 7 64 pro PC was just replaced and I find out a major headache which I hope there is a easy solution to both worlds.
My old PC was running a local account ie " God " and my nas was setup for that user acount with a private share ie "\\readynas\God". I'm happly running along and filling up that private share ever since I got the Nas.
My new Windows 10 PC comes along and look Windows realy wants me to create an acount using our email info ie "God@hotmail.com". Note I do like the idea of my account settings across computers being linked and would like to move foreward using my live account.
So of course I try to set "windows credential manager" that I want to access the "\\readynas\God" location with my old "God" account info but the Nas refuses me to access anything belond the guest privileges.
Try to create "God@hotmail.com" user account in the Nas but of course my real hotmail acount is 22 charactors long and the nas will only let me use 20. So much for updating in the Nas my "God" user to "God@hotmail.com".
Seems my only option is to forget using the live account ablity on the new PC and just create a new LOCAL windows 10 account "God" OR I could create a new shorter hotmail acount to get both worlds. My problem is my old acount is going back to I think 1994, which I just feel it's to much work to get everyone and websites to go with a new email.
My real hope is, could the Ready Nas do a firmware update which will allow the fields to be what ever the maxium vaule Windows 10 will alow for users and passwords?
Or am I being a blockhead and it is possible to use "God@hotmail.com" and still access my private Nas share of "\readynas\god" ?
I'm sure a solution to this post will help many who just transfered to windows 10 and no this has nothing to do with any readynas app or cloud access. Its either a problem with the nas or windows credential manager.
Fire is out and no need for a firmware update to let the nas use account info longer then 20 charactors or having to run a "non live" windows 10 account =P.
So I was being a blockhead as I did know the answer.
In my case I couldn't access the Nas with my known credentials was because Windows 10 was displaying me as a Domain PC.
Starting to suspect I logged back into my windows 10 live account and back to the basics I used "local/god" in the user field with the standard password (as I deleted my previous entery in the credental manager). Walha I can now access all my exsiting nas directories like I could under windows 7 or as a local account with windows 10.
Maybe someone can explain why windows 10 ( at least when running a live account ( ie user account someone@hotmail.com)) thinks it should act like it's on a domain when configured as part of a workgroup? Or at least on this fresh clean windows 10 pro install. Note: a explaination is not a responsibility of the Netgear comunity but it would help other down the road who might read this post witht the same problem of Nas access with windows 10.
8 Replies
Replies have been turned off for this discussion
If your PC user name and password do not match an account on the NAS, the NAS should prompt you for a name and password. Enter your old ones. If you don't want to have to do that every time, click the box that tells Windows to rememember the information in the Credentials Manager.
I agree with Sandshark's suggestion.
A Windows 10 live account username can't be used to login to the NAS. We don't support those accounts.
I knew the account information was different as I wanted to use my hotmail acccount as my username. I was hoping that someone knew of a trick so I could use an account on the NAS that was 22 charactors long, for the NAS will only accept 20.
I also entered my old user account info in the windows account manager for the NAS address under the live account which Windows 10 now accepts. The nas or windows rejected so I presume either I am over looking something or some authorization failed.
As for the lack of suggestions I'm presuming the NETgear ReadyNasNV+ has gone the way of the dino, became a fossil. Not buying another so I will not know if other models or manufacturers have the same 20 charactor limitation.
It's sad since it was such a good unit which I dont see being outdated, just over looked for company profits.
This post Permissions-Windows-10-RTM also here was parallel to my issue even though it didn't have a successful outcome either.
Cosmic75 wrote:
I'm presuming the NETgear ReadyNasNV+ has gone the way of the dino, became a fossil.
Unfortunately, the NV+ v1 simply doesn't have competitive performance anymore. It's a solid product (mine is still running) but newer ARM-based NAS are both faster and less expensive. So it really didn't make sense for Netgear to continue to sell it.
Cosmic75 wrote:
As for the lack of suggestions.
You DID get suggestions that would solve the problem, you just didn't like them.
THE best approach for you is use a simple account name on the NAS (without the @, etc) and enter it into the Windows Credential Manager. The PC will then use it automatically. That works with Windows 7 and Windows 10.
You can get around this by creating an account on Windows without first setting up the Microsoft account during setup. This was also the same behavior in Windows 8/8.1.
When you create with Microsoft account, it doesn't use the classic "username" style.
Fire is out and no need for a firmware update to let the nas use account info longer then 20 charactors or having to run a "non live" windows 10 account =P.
So I was being a blockhead as I did know the answer.
In my case I couldn't access the Nas with my known credentials was because Windows 10 was displaying me as a Domain PC.
Starting to suspect I logged back into my windows 10 live account and back to the basics I used "local/god" in the user field with the standard password (as I deleted my previous entery in the credental manager). Walha I can now access all my exsiting nas directories like I could under windows 7 or as a local account with windows 10.
Maybe someone can explain why windows 10 ( at least when running a live account ( ie user account someone@hotmail.com)) thinks it should act like it's on a domain when configured as part of a workgroup? Or at least on this fresh clean windows 10 pro install. Note: a explaination is not a responsibility of the Netgear comunity but it would help other down the road who might read this post witht the same problem of Nas access with windows 10.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
