New
#11
you are awesome! it worked!
I had to update my GPO and also restart the server but removing the [microsoft network client enforced secured communications] option, I was able to access my samba shares again. Thank you very much.
I had to update my GPO and also restart the server but removing the [microsoft network client enforced secured communications] option, I was able to access my samba shares again. Thank you very much.
Unfortunately I keep having the same error with Windows 7 Professional 32 bit while trying to access a Samba 2.2.x share even after the last setting about "Microsoft network client: Digitally sign communications (always)" and reboot.
I map the directory but can't access to it.
Anyone has any other idea?
Thanks.
Hello,
I think there is an easier solution if you have access to your linux samba server. And, if you are not your Windows computer administrator (in corporative enviroments, for example), probably this is the only solution.
The only thing you have to do is to edit the smb.con file in your linux server (usually in /etc/samba/smb.conf) and add
server signing = auto
It should be enough.
More information about this parameter description in smb.conf
Best regards.
Actually this is a more secure solution> The following security settings of the local security policy's will usually allow you access the Samba servers from Windows 7 machines.
https://www.sevenforums.com/network-sharing/113729-password-protected-network-share.html#post978798
The other solution posted basically turns off digital signing and authentication, the fix outlined in the link only makes a slight adjustment to the Lanman server settings and encryption in order to gain access to the Samba share.
Last edited by chev65; 22 Aug 2013 at 10:03.
Thanks juananzgz, your fix of adding server signing=auto to smb.conf worked perfectly. This is a much better solution, in my opinion, than adding policy changes to the clients.
I was having this same issue as well but I just now fixed it so I thought I'd log in to share.
Computer Policy->Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options
Network security: Restrict NTLM: Outgoing NTLM traffic to remote servers ALLOW ALL
Hi everyone,
I was in trouble too with this error 0x08004005 when trying to access a linux share from my windows seven 64.
I finally solve this by adding the microsoft network client to the "Microsoft Virtual WiFi Miniport Adapter" interface.
This interface is disabled so don't ask me why it has an impact, but it worked for me!
It appeared that my network sharing stopped working suddenly, after several months of usage.
I found the solution here:
Windows cannot access \\machine\sharedfolder, error code 0x80004005
Regards,
Laurent