OS X can connect to Windows machine, but can't access shared folders
I can create new folders on my Windows XP machine, set them to "shared".
On my Mac, I pick Finder → Go → Connect to Server → smb://192.168.1.4 → Connect → Name / Password.
It even shows me all the names of the newly created shared-folders on my PC, but when I try to actually connect to any of them I get
connection failed, there was an error connecting
Any idea on what would cause that? The fact that it successfully gets so far—to actually showing me my PC share-names—must mean I have 99% of this working correctly, i.e. the physical connection, the IP address, the user name, the password, etc.
Still, I can't seem to access the folders themselves.
I've tried this with my Windows XP firewall on/off, and Norton AntiVirus on/off. Same problem.
Everything did work fine, 4 months ago. Were there any odd OS X or Windows updates released recently? I always apply them all.
smbclient on the Mac does correctly find the XP machine, my XP user name, and accepts my XP password.
I get the following from that smbclient command:
Doing spnego session setup (blob length=16)
server didn't supply a full spnego negprot
Got challenge flags: ...
Got NTLMSSP flags: ...
Got NTLMSP flags: ...
Domain=[XPMACHINE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES
I'm not sure why a standard XP box can't "supply a full spnego negprot". Whatever that means.
Using XP's RegEdit to change my IRPStackSize from 11... to 13, 15, 20, 22... still gives that "NT_STATUS_INSUFF_SERVER_RESOURCES" error on the Mac.
macos windows-xp osx-snow-leopard network-shares file-sharing
edited Nov 14 '11 at 19:29
Carol
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
add a comment |
I can create new folders on my Windows XP machine, set them to "shared".
On my Mac, I pick Finder → Go → Connect to Server → smb://192.168.1.4 → Connect → Name / Password.
It even shows me all the names of the newly created shared-folders on my PC, but when I try to actually connect to any of them I get
connection failed, there was an error connecting
Any idea on what would cause that? The fact that it successfully gets so far—to actually showing me my PC share-names—must mean I have 99% of this working correctly, i.e. the physical connection, the IP address, the user name, the password, etc.
Still, I can't seem to access the folders themselves.
I've tried this with my Windows XP firewall on/off, and Norton AntiVirus on/off. Same problem.
Everything did work fine, 4 months ago. Were there any odd OS X or Windows updates released recently? I always apply them all.
smbclient on the Mac does correctly find the XP machine, my XP user name, and accepts my XP password.
I get the following from that smbclient command:
Doing spnego session setup (blob length=16)
server didn't supply a full spnego negprot
Got challenge flags: ...
Got NTLMSSP flags: ...
Got NTLMSP flags: ...
Domain=[XPMACHINE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES
I'm not sure why a standard XP box can't "supply a full spnego negprot". Whatever that means.
Using XP's RegEdit to change my IRPStackSize from 11... to 13, 15, 20, 22... still gives that "NT_STATUS_INSUFF_SERVER_RESOURCES" error on the Mac.
macos windows-xp osx-snow-leopard network-shares file-sharing
edited Nov 14 '11 at 19:29
Carol
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
On your Mac, open Terminal.app, and entersmbclient //192.168.1.4/name-of-share -d 3to get us some debug messages from the process. If you have a username, add-U usernameto this command. We should then be able to see what fails.
– slhck
Sep 14 '11 at 21:53
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57
add a comment |
I can create new folders on my Windows XP machine, set them to "shared".
On my Mac, I pick Finder → Go → Connect to Server → smb://192.168.1.4 → Connect → Name / Password.
It even shows me all the names of the newly created shared-folders on my PC, but when I try to actually connect to any of them I get
connection failed, there was an error connecting
Any idea on what would cause that? The fact that it successfully gets so far—to actually showing me my PC share-names—must mean I have 99% of this working correctly, i.e. the physical connection, the IP address, the user name, the password, etc.
Still, I can't seem to access the folders themselves.
I've tried this with my Windows XP firewall on/off, and Norton AntiVirus on/off. Same problem.
Everything did work fine, 4 months ago. Were there any odd OS X or Windows updates released recently? I always apply them all.
smbclient on the Mac does correctly find the XP machine, my XP user name, and accepts my XP password.
I get the following from that smbclient command:
Doing spnego session setup (blob length=16)
server didn't supply a full spnego negprot
Got challenge flags: ...
Got NTLMSSP flags: ...
Got NTLMSP flags: ...
Domain=[XPMACHINE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES
I'm not sure why a standard XP box can't "supply a full spnego negprot". Whatever that means.
Using XP's RegEdit to change my IRPStackSize from 11... to 13, 15, 20, 22... still gives that "NT_STATUS_INSUFF_SERVER_RESOURCES" error on the Mac.
macos windows-xp osx-snow-leopard network-shares file-sharing
edited Nov 14 '11 at 19:29
Carol
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
I can create new folders on my Windows XP machine, set them to "shared".
On my Mac, I pick Finder → Go → Connect to Server → smb://192.168.1.4 → Connect → Name / Password.
It even shows me all the names of the newly created shared-folders on my PC, but when I try to actually connect to any of them I get
connection failed, there was an error connecting
Any idea on what would cause that? The fact that it successfully gets so far—to actually showing me my PC share-names—must mean I have 99% of this working correctly, i.e. the physical connection, the IP address, the user name, the password, etc.
Still, I can't seem to access the folders themselves.
I've tried this with my Windows XP firewall on/off, and Norton AntiVirus on/off. Same problem.
Everything did work fine, 4 months ago. Were there any odd OS X or Windows updates released recently? I always apply them all.
smbclient on the Mac does correctly find the XP machine, my XP user name, and accepts my XP password.
I get the following from that smbclient command:
Doing spnego session setup (blob length=16)
server didn't supply a full spnego negprot
Got challenge flags: ...
Got NTLMSSP flags: ...
Got NTLMSP flags: ...
Domain=[XPMACHINE] OS=[Windows 5.1] Server=[Windows 2000 LAN Manager]
tree connect failed: NT_STATUS_INSUFF_SERVER_RESOURCES
I'm not sure why a standard XP box can't "supply a full spnego negprot". Whatever that means.
Using XP's RegEdit to change my IRPStackSize from 11... to 13, 15, 20, 22... still gives that "NT_STATUS_INSUFF_SERVER_RESOURCES" error on the Mac.
macos windows-xp osx-snow-leopard network-shares file-sharing
macos windows-xp osx-snow-leopard network-shares file-sharing
edited Nov 14 '11 at 19:29
Carol
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
edited Nov 14 '11 at 19:29
Carol
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
edited Nov 14 '11 at 19:29
Carol
51
edited Nov 14 '11 at 19:29
Carol
51
edited Nov 14 '11 at 19:29
Carol
51
51
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
asked Sep 14 '11 at 20:32
BonnieBonnie
3124
3124
On your Mac, open Terminal.app, and entersmbclient //192.168.1.4/name-of-share -d 3to get us some debug messages from the process. If you have a username, add-U usernameto this command. We should then be able to see what fails.
– slhck
Sep 14 '11 at 21:53
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57
add a comment |
On your Mac, open Terminal.app, and entersmbclient //192.168.1.4/name-of-share -d 3to get us some debug messages from the process. If you have a username, add-U usernameto this command. We should then be able to see what fails.
– slhck
Sep 14 '11 at 21:53
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57
On your Mac, open Terminal.app, and enter
smbclient //192.168.1.4/name-of-share -d 3 to get us some debug messages from the process. If you have a username, add -U username to this command. We should then be able to see what fails.– slhck
Sep 14 '11 at 21:53
On your Mac, open Terminal.app, and enter
smbclient //192.168.1.4/name-of-share -d 3 to get us some debug messages from the process. If you have a username, add -U username to this command. We should then be able to see what fails.– slhck
Sep 14 '11 at 21:53
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57
add a comment |
1 Answer
1
active
oldest
votes
I would suggest using sharing using the Advanced Sharing Options. It has great more customizable options in terms of user control etc. Sometimes shared folders arent accessible to other users (which you can view in the advanced mode).
To activate file sharing in XP, open any window (My Computer, C Drive etc.) and click
Tools -> Folder Options.
On the 'View' Tab, uncheck the option 'Use simple file sharing (recommended)' - It appears in the list below.
Now while sharing, you can select the users for whom you share. Select 'Everyone'. It will work.
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
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%2f335656%2fos-x-can-connect-to-windows-machine-but-cant-access-shared-folders%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
I would suggest using sharing using the Advanced Sharing Options. It has great more customizable options in terms of user control etc. Sometimes shared folders arent accessible to other users (which you can view in the advanced mode).
To activate file sharing in XP, open any window (My Computer, C Drive etc.) and click
Tools -> Folder Options.
On the 'View' Tab, uncheck the option 'Use simple file sharing (recommended)' - It appears in the list below.
Now while sharing, you can select the users for whom you share. Select 'Everyone'. It will work.
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
add a comment |
I would suggest using sharing using the Advanced Sharing Options. It has great more customizable options in terms of user control etc. Sometimes shared folders arent accessible to other users (which you can view in the advanced mode).
To activate file sharing in XP, open any window (My Computer, C Drive etc.) and click
Tools -> Folder Options.
On the 'View' Tab, uncheck the option 'Use simple file sharing (recommended)' - It appears in the list below.
Now while sharing, you can select the users for whom you share. Select 'Everyone'. It will work.
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
add a comment |
I would suggest using sharing using the Advanced Sharing Options. It has great more customizable options in terms of user control etc. Sometimes shared folders arent accessible to other users (which you can view in the advanced mode).
To activate file sharing in XP, open any window (My Computer, C Drive etc.) and click
Tools -> Folder Options.
On the 'View' Tab, uncheck the option 'Use simple file sharing (recommended)' - It appears in the list below.
Now while sharing, you can select the users for whom you share. Select 'Everyone'. It will work.
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
I would suggest using sharing using the Advanced Sharing Options. It has great more customizable options in terms of user control etc. Sometimes shared folders arent accessible to other users (which you can view in the advanced mode).
To activate file sharing in XP, open any window (My Computer, C Drive etc.) and click
Tools -> Folder Options.
On the 'View' Tab, uncheck the option 'Use simple file sharing (recommended)' - It appears in the list below.
Now while sharing, you can select the users for whom you share. Select 'Everyone'. It will work.
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
answered Sep 15 '11 at 3:47
venomrldvenomrld
60748
60748
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%2f335656%2fos-x-can-connect-to-windows-machine-but-cant-access-shared-folders%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
On your Mac, open Terminal.app, and enter
smbclient //192.168.1.4/name-of-share -d 3to get us some debug messages from the process. If you have a username, add-U usernameto this command. We should then be able to see what fails.– slhck
Sep 14 '11 at 21:53
@Carol Please register on the site, otherwise you can't have your accounts associated.
– slhck
Nov 14 '11 at 19:57