NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
ReadyNAS 104 6.6.0 - Windows workstations can no longer access the SMB/CIFS shares
After two years of smoothe operation, I can no longer access the NAS from ANY Windows workstation.
This includes:
Windows 7 Professional
Windows 7 Home Premium
Windows Server 2008 R2
Windows 8.1 Professional
Windows 7 Ultimate
Windows 7 Enterprise
Windows Vista Home Premium
Things I have ALREADY done:
- Installed SMB Plus and locked SMB version to 2.1 (All other settings tried also)
- Local Security Policy - Changed to Send LM & NTLM, and disabled the need for signing
- Local Security Policy - Restrict NTML Outgoing = Allow All
- Added Registry key "EnableLinkedConnections" DWORD = 1 to system policy section
- Manually downgraded the Windows SMB client to v1, and v2, neither of which have an affect.
I CAN access the share via a DOS command, when manually mapping the drives, and using command line.
net use s: \\server2\share Command completed successfully dir s:
I can see all the files in the share, but doing this through Windows explorer produces the error
Windows can't access this disc
The disc might be corrupt. Make sure that the disc uses a format that Windows recognizes. If the disc is unformatted, you need to format it before using it.
I stress again, that for two years this has worked as intended, but recently I updated to OS 6.6.0, which pretty much mucked everything up, that plus a Microsoft update probably.
I'm in the process of configuring a Windows Server box and moving all my documents over to it from the NAS. What a figgin waste.
4 Replies
Replies have been turned off for this discussion
Very strange, since I am not seeing that from Win7 or Win10 with my RN102. FWIW I haven't made any of the changes you made.
Did you consider using per-incident support? Hopefully someone from Netgear will take a look.
I can't even get that far, but that's probably because the person who registered this device is no longer here, so we can't get into the account.
Update:
As it turns out, the root partition was full of junk files (that all began with SORT_) that it could not write or issue tokens, or even make the semaphore files necessary to make a connection.
I had to buy a support contract just to get that figured out, but now all the shares are operating normally.
Apparently all that stuff was dormant, and the upgrade to 6.6.0 triggered the need for the extra space or something. Either way, all versions of Windows can now access the shares. Leave it to me to be the "OMG HTF DID THAT HAPPEN" customer.
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
