Windows XP won't accept uname/password for samba share
I'm trying to connect to a samba share using windows XP Professional.
I type \motherhome into My Computer's address bar, and as expected a "Connect to mother" dialog appears for me to type in my username and password for samba running on \mother.
The samba instance on \mother is Samba v4.0.10 configured as an active directory with domain HOME (realm home.something.net). So I type in my username and password:
As soon as I click ok, The same box reappears no different from before, except that the password is cleared.
What's weird is that if I run net use H: \motherhome /user:HOMEmatt, the output is this:
The password or user name is invalid for \motherhome.
Enter the password for 'HOMEmatt' to connect to 'mother': {types password}
The command completed successfully.
What steps can I take to debug this issue?
windows-xp network-shares samba
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
add a comment |
I'm trying to connect to a samba share using windows XP Professional.
I type \motherhome into My Computer's address bar, and as expected a "Connect to mother" dialog appears for me to type in my username and password for samba running on \mother.
The samba instance on \mother is Samba v4.0.10 configured as an active directory with domain HOME (realm home.something.net). So I type in my username and password:
As soon as I click ok, The same box reappears no different from before, except that the password is cleared.
What's weird is that if I run net use H: \motherhome /user:HOMEmatt, the output is this:
The password or user name is invalid for \motherhome.
Enter the password for 'HOMEmatt' to connect to 'mother': {types password}
The command completed successfully.
What steps can I take to debug this issue?
windows-xp network-shares samba
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18
add a comment |
I'm trying to connect to a samba share using windows XP Professional.
I type \motherhome into My Computer's address bar, and as expected a "Connect to mother" dialog appears for me to type in my username and password for samba running on \mother.
The samba instance on \mother is Samba v4.0.10 configured as an active directory with domain HOME (realm home.something.net). So I type in my username and password:
As soon as I click ok, The same box reappears no different from before, except that the password is cleared.
What's weird is that if I run net use H: \motherhome /user:HOMEmatt, the output is this:
The password or user name is invalid for \motherhome.
Enter the password for 'HOMEmatt' to connect to 'mother': {types password}
The command completed successfully.
What steps can I take to debug this issue?
windows-xp network-shares samba
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
I'm trying to connect to a samba share using windows XP Professional.
I type \motherhome into My Computer's address bar, and as expected a "Connect to mother" dialog appears for me to type in my username and password for samba running on \mother.
The samba instance on \mother is Samba v4.0.10 configured as an active directory with domain HOME (realm home.something.net). So I type in my username and password:
As soon as I click ok, The same box reappears no different from before, except that the password is cleared.
What's weird is that if I run net use H: \motherhome /user:HOMEmatt, the output is this:
The password or user name is invalid for \motherhome.
Enter the password for 'HOMEmatt' to connect to 'mother': {types password}
The command completed successfully.
What steps can I take to debug this issue?
windows-xp network-shares samba
windows-xp network-shares samba
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
edited May 12 '17 at 12:58
Pierre.Vriens
1,24561218
1,24561218
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
asked Oct 18 '13 at 16:27
Matthew SainsburyMatthew Sainsbury
11115
11115
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18
add a comment |
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18
add a comment |
1 Answer
1
active
oldest
votes
The Windows machine must have been caching something vital, because rebooting the machine fixed the problem. It seems many authentication problems can be solved by something as simple as a reboot, so maybe it's a good idea to try this before messing with the active directory and potentially breaking it.
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
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%2f661894%2fwindows-xp-wont-accept-uname-password-for-samba-share%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
The Windows machine must have been caching something vital, because rebooting the machine fixed the problem. It seems many authentication problems can be solved by something as simple as a reboot, so maybe it's a good idea to try this before messing with the active directory and potentially breaking it.
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
add a comment |
The Windows machine must have been caching something vital, because rebooting the machine fixed the problem. It seems many authentication problems can be solved by something as simple as a reboot, so maybe it's a good idea to try this before messing with the active directory and potentially breaking it.
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
add a comment |
The Windows machine must have been caching something vital, because rebooting the machine fixed the problem. It seems many authentication problems can be solved by something as simple as a reboot, so maybe it's a good idea to try this before messing with the active directory and potentially breaking it.
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
The Windows machine must have been caching something vital, because rebooting the machine fixed the problem. It seems many authentication problems can be solved by something as simple as a reboot, so maybe it's a good idea to try this before messing with the active directory and potentially breaking it.
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
answered Oct 19 '13 at 7:52
Matthew SainsburyMatthew Sainsbury
11115
11115
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%2f661894%2fwindows-xp-wont-accept-uname-password-for-samba-share%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
The windows XP machine has a local user account with a different password. Could this be an issue, even if I am explicitly logging in as HOMEmatt and not LOCALPCmatt?
– Matthew Sainsbury
Oct 18 '13 at 16:28
is your samba configured to only allow up-level (NTLMv2) connections? if so, you can either reduce the security for samba, or in your local security policy (on xp, secpol.msc) you can tell it to use more stringent encryption. imss.caltech.edu/node/396
– Frank Thomas
Oct 18 '13 at 16:35
thanks for posting. To be honest I am an utter noob with active directory, so your comment taught me about different authentication levels. I have since solved the problem by simply rebooting the machine. What tools should I be using to figure out these and other problems with active directory?
– Matthew Sainsbury
Oct 18 '13 at 16:52
I'd offer some options if I could. I just know this hack from dealing with many different types of clients for samba.
– Frank Thomas
Oct 18 '13 at 18:18