windows 10 mapping to OS X drive

Question

Level 1

8 points

windows 10 mapping to OS X drive

I need to map from Windows 10 to the Macmini drive to share files across the network. I upgraded 3 PCs to Windows 10 from Windows 81 but can only map from one of the PCs and not from the other two after the upgrade. All setting are the same on the three Windows 10 machines. With the two that I can't map with, I am prompted for user name/password but does not work (used Apple username/password). I tried resetting the Apple user password, but still cannot get map to the drive. I even created a new user/password with admin privileges and still could not map over from the Windows PC. I downgradedthe two PCs that I could not use to map back to Windows 8.1 and now cannot map the Macmini drive whereas I was able to do so before.

I'm using the latest version of Yosemite and Server app.
I can connect all three PCs to the Macmini via VPN after minor tweaks (changed Network security: LAN Manager authentication level to use NTLMv2 if negotiated and unchecked require 128 bit encryption for the minimum session security for NTML SSP based clients) on the Windows 10 PCs.
Firewalls are turned off on both the Macmini and Windows PCs.
Windows PCs shows the Macmini in the network.
All computers are configured to the same workgroup.
I can log in and map drive using my Macbook and iMac either via VPN or on my home network.
I can map a Windows 10 drive from the Macmini. I map between the Windows 10 PCs.

Any suggestions? I think the issue is with the how the Macmini handles the Apple username/password, but I'm not sure.

Mac mini, OS X El Capitan (10.11.2), Server App and Windows 10

Posted on Jan 10, 2016 8:40 PM

Reply

Answer 1

Leopardus

Level 4

1,303 points

Jan 13, 2016 12:03 AM in response to ersoohoo

HI ersoohoo,

have you had a look at the security level on the two affected windows machines?

As from Windows 7, on your windows machine(s) effected, check the following registry key;

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa

look for key KeyLmCompatibilityLevel

If this is already set to "1", change that from "1" to "3".

It doesn't require a reboot and takes effect immediately.

Some people reported changing it from 2 to 3 and having the same positive effect.

Yosemite smb authentication is requiring NTLM 3 instead of 1 or 2.

-One other thing

Use the host file on windows machines as to never resolve the mac's name via SMB.

e.g., from windows

\\my_mac_name

did not work until it's added it to the host file

Leo

Reply

Answer 2

ersoohoo Author

Level 1

8 points

Jan 14, 2016 2:02 PM in response to Leopardus

Thank you. I'm not sure if it does the same thing, but when I used secpol.msc to changed authentication Windows Security Policy Network security: "LAN Manger authentication level from Send LM & NTLM - use NTLMv2 session security if negotiated" to "Send NTLMv2 response only," mapping took place immediately. I can now map from all three Windows 10 PCs

Reply