Can't connect from Windows 10 to Mac Mini using SMB
0
I have a Mac Mini running OS X 10.11 where I set up SMB to share a set of files with my Windows machine (I have Windows as the client, connecting to the Mac). I used to use Windows 7 and everything worked perfectly; now I have upgraded to Windows 10 (the 1803 version) and it doesn't connect anymore.
After searching around, I configured Windows 10 to use only NTLM2 when authenticating (as per https://www.reddit.com/r/osx/comments/3r5q16/cant_access_my_mac_from_windows_10/cwlohrv), but it still didn't work.
What happens is:
- I click the "Connect to network share" option in Windows 10.
- I type in the Mac's address, using the IP address to make sure it connects regardless of naming problems:
\192.168.1.xxx(share name). I also use "connect using other credentials". - Windows asks me for username and password. I type them in. Windows asks me again. I type them in again.
- Windows fails with an error code:
0x8007035 The Network path not found.
I enabled SMB logging in the Mac, and this is what I get when Windows connects:
digest-service[531]: label: default
digest-service[531]: dbname: od:/Local/Default
digest-service[531]: mkey_file: /var/db/krb5kdc/m-key
digest-service[531]: acl_file: /var/db/krb5kdc/kadmind.acl
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: netr probe 0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: od failed with -1561745588 proto=ntlmv2
digest-service[531]: digest-request: user=BIGBRAIN4Paulo
digest-service[531]: digest-request kdc: ok user=MACMINI-DE32AEPaulo proto=ntlmv2 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_ALWAYS_SIGN, NEG_NTLM, NEG_SIGN, NEG_TARGET, NEG_UNICODE
So... what's going on? As I said, everything worked perfectly with Windows 7, and I haven't touched anything in the Mac's setup since then.
windows networking windows-10 mac smb
asked Jan 4 at 11:26
PaulJPaulJ
85811328
add a comment |
0
I have a Mac Mini running OS X 10.11 where I set up SMB to share a set of files with my Windows machine (I have Windows as the client, connecting to the Mac). I used to use Windows 7 and everything worked perfectly; now I have upgraded to Windows 10 (the 1803 version) and it doesn't connect anymore.
After searching around, I configured Windows 10 to use only NTLM2 when authenticating (as per https://www.reddit.com/r/osx/comments/3r5q16/cant_access_my_mac_from_windows_10/cwlohrv), but it still didn't work.
What happens is:
- I click the "Connect to network share" option in Windows 10.
- I type in the Mac's address, using the IP address to make sure it connects regardless of naming problems:
\192.168.1.xxx(share name). I also use "connect using other credentials". - Windows asks me for username and password. I type them in. Windows asks me again. I type them in again.
- Windows fails with an error code:
0x8007035 The Network path not found.
I enabled SMB logging in the Mac, and this is what I get when Windows connects:
digest-service[531]: label: default
digest-service[531]: dbname: od:/Local/Default
digest-service[531]: mkey_file: /var/db/krb5kdc/m-key
digest-service[531]: acl_file: /var/db/krb5kdc/kadmind.acl
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: netr probe 0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: od failed with -1561745588 proto=ntlmv2
digest-service[531]: digest-request: user=BIGBRAIN4Paulo
digest-service[531]: digest-request kdc: ok user=MACMINI-DE32AEPaulo proto=ntlmv2 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_ALWAYS_SIGN, NEG_NTLM, NEG_SIGN, NEG_TARGET, NEG_UNICODE
So... what's going on? As I said, everything worked perfectly with Windows 7, and I haven't touched anything in the Mac's setup since then.
windows networking windows-10 mac smb
asked Jan 4 at 11:26
PaulJPaulJ
85811328
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38
add a comment |
0
0
0
I have a Mac Mini running OS X 10.11 where I set up SMB to share a set of files with my Windows machine (I have Windows as the client, connecting to the Mac). I used to use Windows 7 and everything worked perfectly; now I have upgraded to Windows 10 (the 1803 version) and it doesn't connect anymore.
After searching around, I configured Windows 10 to use only NTLM2 when authenticating (as per https://www.reddit.com/r/osx/comments/3r5q16/cant_access_my_mac_from_windows_10/cwlohrv), but it still didn't work.
What happens is:
- I click the "Connect to network share" option in Windows 10.
- I type in the Mac's address, using the IP address to make sure it connects regardless of naming problems:
\192.168.1.xxx(share name). I also use "connect using other credentials". - Windows asks me for username and password. I type them in. Windows asks me again. I type them in again.
- Windows fails with an error code:
0x8007035 The Network path not found.
I enabled SMB logging in the Mac, and this is what I get when Windows connects:
digest-service[531]: label: default
digest-service[531]: dbname: od:/Local/Default
digest-service[531]: mkey_file: /var/db/krb5kdc/m-key
digest-service[531]: acl_file: /var/db/krb5kdc/kadmind.acl
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: netr probe 0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: od failed with -1561745588 proto=ntlmv2
digest-service[531]: digest-request: user=BIGBRAIN4Paulo
digest-service[531]: digest-request kdc: ok user=MACMINI-DE32AEPaulo proto=ntlmv2 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_ALWAYS_SIGN, NEG_NTLM, NEG_SIGN, NEG_TARGET, NEG_UNICODE
So... what's going on? As I said, everything worked perfectly with Windows 7, and I haven't touched anything in the Mac's setup since then.
windows networking windows-10 mac smb
asked Jan 4 at 11:26
PaulJPaulJ
85811328
I have a Mac Mini running OS X 10.11 where I set up SMB to share a set of files with my Windows machine (I have Windows as the client, connecting to the Mac). I used to use Windows 7 and everything worked perfectly; now I have upgraded to Windows 10 (the 1803 version) and it doesn't connect anymore.
After searching around, I configured Windows 10 to use only NTLM2 when authenticating (as per https://www.reddit.com/r/osx/comments/3r5q16/cant_access_my_mac_from_windows_10/cwlohrv), but it still didn't work.
What happens is:
- I click the "Connect to network share" option in Windows 10.
- I type in the Mac's address, using the IP address to make sure it connects regardless of naming problems:
\192.168.1.xxx(share name). I also use "connect using other credentials". - Windows asks me for username and password. I type them in. Windows asks me again. I type them in again.
- Windows fails with an error code:
0x8007035 The Network path not found.
I enabled SMB logging in the Mac, and this is what I get when Windows connects:
digest-service[531]: label: default
digest-service[531]: dbname: od:/Local/Default
digest-service[531]: mkey_file: /var/db/krb5kdc/m-key
digest-service[531]: acl_file: /var/db/krb5kdc/kadmind.acl
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: netr probe 0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: init request
digest-service[531]: digest-request: init return domain: MACMINI-DE32AE server: MEGA-MEDIA-CENTER indomain was: <NULL>
digest-service[531]: digest-request: uid=0
digest-service[531]: digest-request: od failed with -1561745588 proto=ntlmv2
digest-service[531]: digest-request: user=BIGBRAIN4Paulo
digest-service[531]: digest-request kdc: ok user=MACMINI-DE32AEPaulo proto=ntlmv2 flags: NEG_KEYEX, ENC_128, NEG_VERSION, NEG_TARGET_INFO, NEG_NTLM2, NEG_ALWAYS_SIGN, NEG_NTLM, NEG_SIGN, NEG_TARGET, NEG_UNICODE
So... what's going on? As I said, everything worked perfectly with Windows 7, and I haven't touched anything in the Mac's setup since then.
windows networking windows-10 mac smb
windows networking windows-10 mac smb
asked Jan 4 at 11:26
PaulJPaulJ
85811328
asked Jan 4 at 11:26
PaulJPaulJ
85811328
edited Jan 4 at 11:48
PaulJ
asked Jan 4 at 11:26
PaulJPaulJ
85811328
asked Jan 4 at 11:26
PaulJPaulJ
85811328
asked Jan 4 at 11:26
PaulJPaulJ
85811328
85811328
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38
add a comment |
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38
add a comment |
0
active
oldest
votes
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390476%2fcant-connect-from-windows-10-to-mac-mini-using-smb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1390476%2fcant-connect-from-windows-10-to-mac-mini-using-smb%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
idk if this is any use, mainly it discusses what you already tried, NTLM2 only - apple.stackexchange.com/questions/152900/…
– Tetsujin
Jan 4 at 11:37
@Tetsujin: thanks. As mentioned, I already changed that in my Windows 10 machine.
– PaulJ
Jan 4 at 11:50
Try using the "net use" DOS command. You can pass in the credentials on the command-line (yeah yeah, not secure if someone else is logged into your PC and can see your Task Mgr). When I've had strange (Windows-to-Windows) fileshare access problems, this has always helped. That said, I've been unable to connect my PC and my Mac since Windows 8, so something else really changed besides NTLM, which shouldn't come into play with a Mac fileshare.
– jimtut
Jan 4 at 15:38