Solved samba share is not accessible from Windows 7 client...

S2LR · Feb 9, 2012

Hello,

I'm trying to map a network drive from my windows client running Windows 7 Enterprise. The folder is a Samba share on a linux (Fedora core 13) server. When I attempt to map the drive using the folder \\10.1.1.131\earth, I get the message via a dialog box:

Y:\ is not accessible
an unexpected network error occurred

From the explorer window, it appears like the drive got mapped (green line is on) but when I click it on, I get the same message as above.

I can map the Samba share just fine on machines running Vista Home premium and XP professional but I can't get it to work on my Windows 7 box. I'm figuring that the problem is on the Windows side and not on the Linux side since I can map the drive on other machines using different Windows OS.

I've tried all the suggestions of setting the various network security and network access options in the policy editor and nothing seems to work.

If anyone can offer any suggestions or help, it would be most appreciated...

Thanks!

WebMattR · Feb 9, 2012

Might I point you towards this thread? Simpler than proposing you try the different solutions suggested there, one by one.

S2LR · Feb 10, 2012

Unfortunately I tried the suggestions that were given in the thread to no avail. The problem still remains...
What I haven't done is capture data packets using wireshark. Perhaps that is my only recourse at this point try to understand why I can't access the share...

I forgot to mention that the Linux server is using Samba 3.5...

WebMattR · Feb 10, 2012

Is there any security set on the samba share? Perhaps require a password for authentication, and see if that helps? I'm afraid my knowledge of samba is somewhat limited, but I'll still see what I can do towards assisting you.

S2LR · Feb 10, 2012

WebMattR,

Thanks for the feedback and help.

The share itself is defined in the smb.conf file on the Linux server as follows...

[earth]
comment = earth database
path = /media/sdb1
read only = no
guest ok = yes

The security settings in the Standalone Server Options in the smb.conf file are set to

security = share

I'm really quite surprised that this problem isn't more pervasive than it is with Windows 7 and Samba shares...

WebMattR · Feb 10, 2012

Can you require authentication to the server, and try authenticating? I have this feeling that your W7 machine doesn't know how to authenticate.

S2LR · Feb 10, 2012

Is this a change in the policy to require authentication in the W7 client? If so, which policy do I need to change?

Why does W7 require authentication when I don't need to do this for XP or Vista? What is it that makes W7 different from XP or Vista when accessing Samba shares? I don't have any problem getting at my share with XP or Vista.

The whole thing is rather frustrating...

WebMattR · Feb 10, 2012

They changed the way security works rather massively between each rendition of the OS (XP, Vista, and 7).
Have you seen this? My mind thinks the issue is elsewhere, but maybe this is the real trick.
http://www.stat.tamu.edu/how_to/samba_7.pdf

S2LR · Feb 10, 2012

Unfortunately I've already tried what the provided link suggests and it still doesn't allow me access.

Like I mentioned in my original post, Windows appears to map the drive ok but it won't allow me access. If I issue the command from a windows command prompt:

net use Y: \\10.1.1.131\earth

It tells me the command completed successfully and the drive shows up in the Windows explorer. If I click on the drive Y:, I get the message:

Y:\ is not accessible
An unexpected network error occurred

The frustration continues...

S2LR · Feb 13, 2012

Ok...after much pain and searching, I finally found the policy that was not letting me have access to my Samba share on my Linux server from my W7 client. I could map network drive but I couldn't access it (see previous posts above...).

In the Local Group Policy Editor, go to:

Local Computer Policy->Computer Configuration->Windows Settings->Security Settings->Local Policies->Security Options

Find the policy:

Microsoft network client: Digitally sign communications (always)

If this is enabled, change it to Disabled. Be sure and restart your machine for the change to take effect! Pressing the "Apply" button in the Policy Editor after the change is made is not sufficient...

Once I did this, I was able to access my Samba share.

Hopefully this will help someone else who runs into the same irritating problem.

Thanks to those who attempted to help me out.

Regards...

aj203355 · Aug 10, 2012

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.

Bob10 · Nov 19, 2012

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.

juananzgz · Jun 12, 2013

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.

chev65 · Jun 12, 2013

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.

http://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.

bpopp · Jul 11, 2013

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.

Xenux · Aug 3, 2013

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

gilgamir · Aug 22, 2013

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

Solved samba share is not accessible from Windows 7 client...

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

New member

My Computer

Closed

My Computer

New member

My Computer

New member

My Computer

New member

My Computer