map network drive to NAS but get error 64 or 58

[PLEESD43]

That is awesome! Thanks for posting this as I was having problems with Windows 7 workstation accessing a Linux share through VPN. When I implemented the 3 changes above I was able to "net use" command to map a drive to it! The Windows 7 computer was imaged with WDS!

 

I sincerely thank you for posting this fix!!!

[andrewpetre]

just fixed another one with only 3 changes so to summarize here's what was changed via secpol.msc under

Security Settings->Local Policies->Security Options

 

Microsoft network client: Digitally sign communications (always)    Disabled

 

We only needed this first bit changed to fix up access to our QNAP. This began to happen only recently to newly deployed workstations after the migration from 2008 (non-R2) WDS to a 2012 WDS server. We brought the WIMs with us, so at a glance it seems as though this is a server setting.

 

 

In any case, thanks for getting to the bottom of this. It was making us all feel quite neurotic to have computers on the same subnet with the same permissions behaving as though they couldn't access the share.

 

 

This should be echoed in the QNAP forums for others.

[mac_shinobi]

Just wanted to add those settings relate to smb signing from what I am aware of on either the client or server os or both - some articles

 

http://support.exinda.com/topic/how-to-disable-smb-signing-on-windows-servers-to-improve-smb-performance

 

http://blogs.technet.com/b/josebda/archive/2010/12/01/the-basics-of-smb-signing-covering-both-smb1-and-smb2.aspx

 

http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

[mac_shinobi]

A quick guide that I made - for windows 7 and scanning from a Ricoh MFD , think this walks through a similar process for the same settings ( I believe ) as mentioned above

windows 7 scan settings v2.pdf