One particular Windows 10 PC can't access Samba share 0x80070035 (solved)
I have two Samba shares from two different machines. One is a Raspberry Pi that has never been an issue. The other is a Debian server with a nearly identical configuration. It may actually be identical, and I haven't checked all the global settings.
I have a Windows 10 Education desktop that can access/map the Raspberry Pi, but not the Debian share. I can see it in the Networks tab in File Explorer. I can ping it by name or by IP address. I can SSH into it with PuTTY. But when I click it in File Explorer, I get a 0x80070035 error. I get the same error when I try to map it by IP address. If I put the IP address in the run box, it asks for credentials, but it won't accept my password.
I have three other Windows 10 PCs (Home and Pro) and a Fedora laptop that access and map/mount the Debian share just fine. It's also my Plex server that all clients in the house are able to use without issue. I even have an Ubuntu VM on the Windows PC in question that mounts the share with no problems.
Since every other machine can access the Debian machine, I assume the server is properly configured and the problem must be with the Windows PC. I've compared network settings with my other Windows PCs and everything (everything in Network and Sharing Center, at least) appears to be the same.
Edit: So the problem is now solved in the sense that I have the function I needed, though not in the sense of knowing what was causing the issue. I reinstalled Windows and started with a clean slate. Now, neither share appears in File Explorer, but I can map them both with the IP address.
Obviously, nuking the system isn't an ideal solution, but I needed it to work and starting over became the best option. The shares not appearing in Explorer is a new issue, but since it's not actually affecting functionality, I'm inclined to let it be for now.
networking windows-10 samba
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
bumped to the homepage by Community♦ 20 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
add a comment |
I have two Samba shares from two different machines. One is a Raspberry Pi that has never been an issue. The other is a Debian server with a nearly identical configuration. It may actually be identical, and I haven't checked all the global settings.
I have a Windows 10 Education desktop that can access/map the Raspberry Pi, but not the Debian share. I can see it in the Networks tab in File Explorer. I can ping it by name or by IP address. I can SSH into it with PuTTY. But when I click it in File Explorer, I get a 0x80070035 error. I get the same error when I try to map it by IP address. If I put the IP address in the run box, it asks for credentials, but it won't accept my password.
I have three other Windows 10 PCs (Home and Pro) and a Fedora laptop that access and map/mount the Debian share just fine. It's also my Plex server that all clients in the house are able to use without issue. I even have an Ubuntu VM on the Windows PC in question that mounts the share with no problems.
Since every other machine can access the Debian machine, I assume the server is properly configured and the problem must be with the Windows PC. I've compared network settings with my other Windows PCs and everything (everything in Network and Sharing Center, at least) appears to be the same.
Edit: So the problem is now solved in the sense that I have the function I needed, though not in the sense of knowing what was causing the issue. I reinstalled Windows and started with a clean slate. Now, neither share appears in File Explorer, but I can map them both with the IP address.
Obviously, nuking the system isn't an ideal solution, but I needed it to work and starting over became the best option. The shares not appearing in Explorer is a new issue, but since it's not actually affecting functionality, I'm inclined to let it be for now.
networking windows-10 samba
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
bumped to the homepage by Community♦ 20 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46
add a comment |
I have two Samba shares from two different machines. One is a Raspberry Pi that has never been an issue. The other is a Debian server with a nearly identical configuration. It may actually be identical, and I haven't checked all the global settings.
I have a Windows 10 Education desktop that can access/map the Raspberry Pi, but not the Debian share. I can see it in the Networks tab in File Explorer. I can ping it by name or by IP address. I can SSH into it with PuTTY. But when I click it in File Explorer, I get a 0x80070035 error. I get the same error when I try to map it by IP address. If I put the IP address in the run box, it asks for credentials, but it won't accept my password.
I have three other Windows 10 PCs (Home and Pro) and a Fedora laptop that access and map/mount the Debian share just fine. It's also my Plex server that all clients in the house are able to use without issue. I even have an Ubuntu VM on the Windows PC in question that mounts the share with no problems.
Since every other machine can access the Debian machine, I assume the server is properly configured and the problem must be with the Windows PC. I've compared network settings with my other Windows PCs and everything (everything in Network and Sharing Center, at least) appears to be the same.
Edit: So the problem is now solved in the sense that I have the function I needed, though not in the sense of knowing what was causing the issue. I reinstalled Windows and started with a clean slate. Now, neither share appears in File Explorer, but I can map them both with the IP address.
Obviously, nuking the system isn't an ideal solution, but I needed it to work and starting over became the best option. The shares not appearing in Explorer is a new issue, but since it's not actually affecting functionality, I'm inclined to let it be for now.
networking windows-10 samba
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
I have two Samba shares from two different machines. One is a Raspberry Pi that has never been an issue. The other is a Debian server with a nearly identical configuration. It may actually be identical, and I haven't checked all the global settings.
I have a Windows 10 Education desktop that can access/map the Raspberry Pi, but not the Debian share. I can see it in the Networks tab in File Explorer. I can ping it by name or by IP address. I can SSH into it with PuTTY. But when I click it in File Explorer, I get a 0x80070035 error. I get the same error when I try to map it by IP address. If I put the IP address in the run box, it asks for credentials, but it won't accept my password.
I have three other Windows 10 PCs (Home and Pro) and a Fedora laptop that access and map/mount the Debian share just fine. It's also my Plex server that all clients in the house are able to use without issue. I even have an Ubuntu VM on the Windows PC in question that mounts the share with no problems.
Since every other machine can access the Debian machine, I assume the server is properly configured and the problem must be with the Windows PC. I've compared network settings with my other Windows PCs and everything (everything in Network and Sharing Center, at least) appears to be the same.
Edit: So the problem is now solved in the sense that I have the function I needed, though not in the sense of knowing what was causing the issue. I reinstalled Windows and started with a clean slate. Now, neither share appears in File Explorer, but I can map them both with the IP address.
Obviously, nuking the system isn't an ideal solution, but I needed it to work and starting over became the best option. The shares not appearing in Explorer is a new issue, but since it's not actually affecting functionality, I'm inclined to let it be for now.
networking windows-10 samba
networking windows-10 samba
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
edited Sep 26 '18 at 22:30
Peter Mortensen
8,376166185
8,376166185
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
asked May 5 '18 at 13:53
Sean CroshawSean Croshaw
95
95
bumped to the homepage by Community♦ 20 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
bumped to the homepage by Community♦ 20 hours ago
This question has answers that may be good or bad; the system has marked it active so that they can be reviewed.
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46
add a comment |
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46
add a comment |
2 Answers
2
active
oldest
votes
Here is the relevant sub-section from my answer to a related question.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue. The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS before trying to access one.
A third method would be to simply add your windows username to the samba server's list of usernames.
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
add a comment |
I was able to fix this problem on a Windows 10 (Home) connecting to Ubuntu 16.04 by commenting the explicit smb ports = 139 line in smb.conf
Found the solution on https://www.unix.com/302601412-post5.html
answered Feb 18 at 17:02
PitPit
993
add a comment |
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
});
}
});
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%2f1320007%2fone-particular-windows-10-pc-cant-access-samba-share-0x80070035-solved%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
Here is the relevant sub-section from my answer to a related question.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue. The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS before trying to access one.
A third method would be to simply add your windows username to the samba server's list of usernames.
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
add a comment |
Here is the relevant sub-section from my answer to a related question.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue. The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS before trying to access one.
A third method would be to simply add your windows username to the samba server's list of usernames.
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
add a comment |
Here is the relevant sub-section from my answer to a related question.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue. The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS before trying to access one.
A third method would be to simply add your windows username to the samba server's list of usernames.
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
Here is the relevant sub-section from my answer to a related question.
You may still get "Error code 0x80070035 - The network path was not found" if the samba device you are connecting to does not have a user account name that matches your windows account name.
There are several ways to fix the above "missing username" issue. The first is by placing a valid entry in the Windows Credential Manager. In my case, the entry was for the domain AS5002T, the username admin, and my password.
A second method, which will recover the way windows worked in the past, is to instead "enable insecure guest logons". Insecure guest logons are used on many consumer NAS devices, as a way to let unauthenticated network users "preview" the shares on the NAS before trying to access one.
A third method would be to simply add your windows username to the samba server's list of usernames.
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
answered May 30 '18 at 22:39
OrangeSherbetOrangeSherbet
193118
193118
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
add a comment |
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
The Error code 0x80070035 - The network path was not found could be caused by blocked IPv6 access to the (Samba) share (or non-working IPv6 on client machine). Windows (as of year 2019) doesn't solve the malfunction problem of IPv4/IPv6 with a fallback to the other protocol.
– Milan Kerslager
2 days ago
add a comment |
I was able to fix this problem on a Windows 10 (Home) connecting to Ubuntu 16.04 by commenting the explicit smb ports = 139 line in smb.conf
Found the solution on https://www.unix.com/302601412-post5.html
answered Feb 18 at 17:02
PitPit
993
add a comment |
I was able to fix this problem on a Windows 10 (Home) connecting to Ubuntu 16.04 by commenting the explicit smb ports = 139 line in smb.conf
Found the solution on https://www.unix.com/302601412-post5.html
answered Feb 18 at 17:02
PitPit
993
add a comment |
I was able to fix this problem on a Windows 10 (Home) connecting to Ubuntu 16.04 by commenting the explicit smb ports = 139 line in smb.conf
Found the solution on https://www.unix.com/302601412-post5.html
answered Feb 18 at 17:02
PitPit
993
I was able to fix this problem on a Windows 10 (Home) connecting to Ubuntu 16.04 by commenting the explicit smb ports = 139 line in smb.conf
Found the solution on https://www.unix.com/302601412-post5.html
answered Feb 18 at 17:02
PitPit
993
answered Feb 18 at 17:02
PitPit
993
answered Feb 18 at 17:02
PitPit
993
answered Feb 18 at 17:02
PitPit
993
993
add a comment |
add a comment |
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.
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%2f1320007%2fone-particular-windows-10-pc-cant-access-samba-share-0x80070035-solved%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
I'm having a similar problem, posted about it in this link. Perhaps together, we can overcome this beast of a problem: superuser.com/questions/1322497/…
– OrangeSherbet
May 14 '18 at 21:46