smb shares on OSX to Windows not working after upgrade

Any one have any luck with this, none of my Windows machines can connect to any shares on the server after the upgrade.

I have exactly the same problem. My Windows 7 x64 SP1 client successfully connected to SMB shared folders on my MAC Mini Server Mountain Lion (OS X 10.8). After upgrading to Maverick (OS X 10.9) and Server 3.0 my Windows 7 x64 SP1 client cannot connect to the SMB shares anymore. It keeps prompting for username and password. I am using Open Directory and tried different network accounts but no joy.

I ran a network capture on the Windows 7 x64 SP1 client and noticed the connection was failing with “LOGON_FAILURE”. However the same user account can access mail, print services, etc., so the account is not locked or the password expired.

I then tried to connect to the SMB share using the local system administrator account and it worked!

I only have one user using a Windows 7 x64 SP1 client machine so I created a new local user account, local group and assign the necessary permissions for the Windows user to access the SMB shares and worked fine.

Obliviously this is not a solution but a workaround and this may not be very practical if your network have few users using Windows clients connecting to SMB shares on your MAC Mini Server running Mavericks (10.9) and Server 3.0.

In my case it looks like the upgrade caused issues with Open Directory network user accounts authenticating to SMB shares from Windows clients.

I hope this helps!

So I was finally able to restore my connections from my windows clients. What I did was the following:

• Set Lan Manager Authentication Level to "Send NTLMv2 response only"
• Connect from the client without specifiing a domain, just enter the shortname and password.

Hi there,

i also use a lot of windows connections to Mountain Lion or Mavericks

what worked for me was to make a netlog.bat file

containing:

@ echo off

net use/delete w:>nul

net use F[disk letter]: \\0.0.0.0\Sharename /user:user password

exit

and put that in the startup folder of the windows machine..

now there is a stable connection every time te windows machine boots..

hope this helps..

@thePod7, your suggestion on Setting the Lan Manger Authentical Level worked! Only thing missing is the instructions on how to Set the Lan Manager Authentication Level. So I've included it below. Hope this helps someone else having the issue!

On command line....

1. Enter “gpedit.msc” in the Start Search box.

2. Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.

3. In the right pane, enable the following policies:

Network access: Allow anonymous SID/name translation

Network access: Let Everyone permissions apply to anonymous users

Also please disable the following policies.

Network access: Restrict anonymous access to Named Pipes and Shares

Network access: Do not allow anonymous enumeration of SAM accounts

Network access: Do not allow anonymous enumeration of SAM accounts and shares

Change the following policy:

Network security: LAN Manager authentication level

Change the value to “Send LM & NTLM - use NTLMv2 session security if negotiated”.

Outstanding Ben.

This is an older article, but it helped me with my Windows 10 and my home Mac network!

PERFECT!!!!

I am trying to connect my mac to my windows file server but every time I try to connect with the username and password it says the username or password is wrong even though it isn't. the windows can connect to the mac file server with no problem. I tried to do the policy thing but it says that gpedit.msc is not even their please help!!😕

It says I don't have gpedit.msc

Thank you! It's work!!!

Thank you Ben, It's worked on my macos Server (10.12) and Windows 10!!!