You can make a difference in the Apple Support Community!

When you sign up with your Apple Account, you can provide valuable feedback to other community members by upvoting helpful replies and User Tips.

Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Windows 10 can't connect to OS X server 10.10.3

Running OS X server 10.10.3 (will be updating to 10.10.4 and server 4.1.3 tonight after hours)

Open Directory working just fine.

Macs on the network all connecting

Windows 7 and win XP clients connecting fine

We have 3 windows 7 clients -- all have been able to connect for months without an issue to OS X server. I did have to do the security policy "tweaks" to get win7 to connect at first but they have been stable since first setup. Here is a link to the smb "tweaks" I have done in the past for windows 7 that have always worked just fine http://www.macwindows.com/OSXServer.html#050310c

The NEW Issue.

One of the windows 7 clients got upgraded to windows 10 and now it can not connect to the server using (the users) normal network account (OD). if I use the OS X server's Local administrator account from the win10 client it connects to the shaire without an issue. I created a new Local account for the user and that account can connect but word and excel say the files are read only. I have made sure the new local account is in all the groups on the server and even added the account with read and wright directly to the share point. T

o be clear the network accounts (OD) can not connect at all from windows 10 error is you do not have permission to access the server, but local accounts on the server connect to the network shares and allow files to be seen. Anyone have any ideas?

I have a feeling that security setting on the windows 10 client seeds to be lowered like the past tweaks I have done but win10 is so new maybe no one has really troubleshooter this issue.

If you have any questions just ask, will try an provide any info that is not clear.

Thanks Scott Seifert

Posted on Aug 12, 2015 10:26 AM

Top-ranking reply

Duane Deal

Level 2

193 points

Posted on Jan 24, 2017 8:25 AM

It may actually be because a security setting on the Windows client is set too low. Check your NTLM (LAN manager) setting. OS X blocks anything below level 3. You can change this in the local security policy (Secpol.msc) or edit the registry ( HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Lsa LMCompatibility level. Change the level to 3.

View in context

19 replies

Jan 7, 2016 2:38 AM in response to äppel.de

I have applied this procedure in two windows 10 computer but it does not help.

- LAN Manager Authentication Level NTLMv2 response only

- Network Security: Minimum session security for NTLM SSP Based (including secure RPC) Clients is set to Require 128-bit encryption.

- \\WORKGROUP\username

Please give us some clue what we can do now.

Thanks.

Regards

Sazzad kabir

Jan 7, 2016 3:24 AM in response to sazzad_kabir

just for clarification:

all "\" are backslashes

Syntax of server address in Windows 10:

\\Windows server-name or IP address\sharepoint

Syntax of Login name:

workgroup\username

workgroup = Windows workgroup which you configured for your network

default in OS X = workgroup

Please note, that the login name does not start with backslashes.

I can only say this for networks that don't use an Active Directory - if you use an Active Directory domain in your network, then the scheme of the username might be different.

I just tested this on a Windows 10 machine which was freshly upgraded from Windows 7 a few days ago.

I did not make any changes in the Windows 10 registry.

Jun 20, 2016 2:41 AM in response to sazzad_kabir

Hello all,

I think that I´ve found the Problem. In Login window, instead of: WORKGROUP\username you must write: Local Host (PC name)\username and be sure to Active the secound Option as well.(connect with another....)

"Local Host"\username

Regards, Mohsen

Sep 13, 2016 6:27 PM in response to mohsenfromCologne

That did it for me. I remember now, that was what Windoze 7 would do automatically. The problem with Windoze 10 (and I use Pro) is that it is no longer an operating system for professionals. It is simply geared to the social users. And, unfortunately, it would seem that is the direction Mac is going. For my server, I have tried everything up to Sierra Beta and I am back to Snow Leopard Server.

Thanks for your help.

Windows 10 can't connect to OS X server 10.10.3