Can't Access ReadyNAS Ultra Share from Windows 7 Only

[GibsonCRG]

So, I must love ReadyNAS - I have an NV, and NV+ and an Ultra all on the same subnet. From a Windows XP machine, I can access any of the three with no problems. But from a Windows 7 machine, I can access the NV and the NV+ just fine, but on the ReadyNAS Ultra, I get this error when I try to open the device to view the shares from the Windows 7 Network window:

\\NAS_03 is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Logon failure: account currently disabled.

This NAS appears to be configured and running OK, as the other XP computers can access it; this computer seems to be OK as it can access the other two ReadyNAS (the NV and the NV+). The username on the ReadyNAS Ultra matches the username on the Windows 7, but on both the Windows 7 and the Ultra, there is no password set for the user. I've also tried the suggestion I found elsewhere to set the Networking options to allow 40- and 56-bit encryption in the Advanced Network Settings, but that didn't have any effect.

Thoughts or suggestions appreciated!

EDIT: oh, yes - I'm running in a workgroup environment on a home network, not an AD environment.

[Dave_Evans1]

I had the same problem until I created a user on the ReadyNAS that matched the windows username I was logged in with. I set the password the same too, not sure if that was required or if it would have just challenged for it.

N.B. don't forget you can't create a user on the NAS with the same name as an existing share.

[GibsonCRG]

I went thru a support ticket with Netgear, and they were able to find a fix for the problem, even if the original cause is a bit of a mystery. I had a username on my ReadyNAS that matched my Windows username. At their suggestion, I changed the username on the ReadyNAS, at which point I was able to access the shares again. The mystery is, when I changed the username back, I was STILL able to access the shares. So, what the underlying cause was, is still a mystery.

If you run into this, the last suggestion from Netgear (which I didn't put into place as the problem seemed solved), was to go into the Frontview management application, Go to Security--> User and Group Accounts, and "on the drop-down option on the top-right side, select Preferences, then select 'Disabled' on the 'Private home shares for users' and click Apply." I believe the thinking is that the private home share that's created (that matches the username) might be causing a conflict of some kind (note - I have two other ReadyNAS devices, all with the same configuration, so I might have several of these private shares going).

Anyway, problem solved, and wanted to post the fix here in case it helps anyone else. Cheers!

[jillybean]

Thankyou!
I have just set up a new Ultra 2 (already have a duo) and had exactly this problem. You saved me a lot of frustration.

[GibsonCRG]

Glad to hear it! For what it's worth, after the first issue, my ReadyNAS Ultra has worked like an absolute champ. I've added two add'l hard disks at different times, and the RAID-X has expanded as advertised to handle the new volumes. I've also had two power failures before I realized that my UPS had bit the dust, and the NAS handled them smoothly with no data loss - just a several hour RAID re-synch. It happily does it's weekly internal check as well as the bi-monthly full volume check (based on my scheduling) and they notify me that they take place, and when they complete (so far, all with no errors). This really is a top-notch device, it's very, VERY quiet, and I think it has earned its accolades and is worth wrestling with the initial issues.

I've seen a firmware update come down recently, but I have NOT yet applied it, so don't know if it might address this issue that I ran into.

[jillybean]

GibsonCRG wrote:
I've seen a firmware update come down recently, but I have NOT yet applied it, so don't know if it might address this issue that I ran into.

It doesn't appear to - I did that update as part of the initial setup before I did anything else but still ran into this problem.

[Papagaiou]

I resolve a similar problem.

I had a share with the same name as the windows account name on the client Win 7! This prevents the login to the Nas via samba!

I just rename the share and voila it works!

[cartes]

SOLVED!

After several hours of searching and trying different solutions, this worked for me:

Programs > Accessories and right click on Command Prompt, select "Run as Administrator" to open a command prompt.
Reset WINSOCK entries to installation defaults: netsh winsock reset catalog
Reset TCP/IP stack to installation defaults. netsh int ip reset reset.log
Reboot the machine.

Thanks to FizzyMyNizzy's post at http://www.dslreports.com/forum/r26888906-How-to-reset-my-NetBIOS

I found that as I then went in to the accounts of my four family members, each one's share became recognised from Network > NAS (or whatever you've called yours), one by one and user/login details weren't needed as the details were the same on Windows as on the NAS.

[BrianL2]

Hi guys,

Thanks for sharing the workaround that fixed your SMB access to your ReadyNAS shares. @GibsonCRG you may now tag this thread as resolved by clicking the "Accept as solution" button in one of the responses posted on this thread.

Kind regards,

BrianL
NETGEAR Community Team