Can't See available windows shares (SMB)

[fencepost]

We have 7 macs here. 6 of which can view and connect to windows shares via smb w/out any problems. One has been giving us a problem and I can't find a solution anywhere.

Using apple + k I can connect using smb://serverName/shareName on all 7 machines. I cannot however, connect using smb://serverName. This only happens on certain servers. The other 6 machines can connect w/out any problem.

When browsing through the network and trying to connect using the alias, where it specifically says "To see the available shares for server [SERVERNAME], press Connect" I get the following error message for this one machine:
"The alias [SERVERNAME] could not be opened, because the original item cannot be found."

When connecting via apple + k I get a -36 error...Finder cannot complete the operation...read...write...

Here is the console.log message that occurs when trying to connect and view the shares by either browsing through the network or using apple + k:

mount_smbfs: session setup phase failed: syserr = Permission denied
mount_smbfs: could not login to server [SERVERNAME]: syserr = Permission denied
mount_smbfs: session setup phase failed: syserr = Socket is not connected
mount_smbfs: could not login to server [SERVERNAME]: syserr = Socket is not connected

We get by by typing in the full address (smb://serverName/shareName), but one has to remember the share name.

Does anyone have any idea why this one machine is acting up? And is there a solution. I'm at the point of formatting the drive and starting over.

Thanks

[cameranerd74]

Error (http://appleerrorcodes.com/) -36 is an I/O error, which make this behavior seem even more strange. Since there's only 1 machine acting up, blowing it off and starting over might not be a bad idea.

[Raven]

Sometimes this happens if the "server" is set to share only a folder within it to specific users... So if you try to simply connect to the machine with no specific user authentication, or one tyhat is not set to be allowed on the root of the drive, you get error 36 as well...

[Reddog]

Sometimes the -36 error has been known to be solved by deleting the Keychain entry for the server affected (it fixed my problem).

Pat

[osxfan57]

Ever since Tiger, I cannot connect to the XP Pro machine on my home network. In the Finder's Network browser, I see the XP machine but I can't connect to it. If I try, get "Sorry, the operation could not be completed because an unexpected error occurred. (Error code -41)." I can try again or cancel, but it won't ever connect. Same problem if I use Cmd-K to connect, whether I use smb://servername/sharename or just smb://servername. I have turned off and then reenabled sharing on the XP box, and have ensured that the Firewall has ports 137, 138 and 139 open for SMB. But previously, rather than eroor -41, I had been getting ""The alias [SERVERNAME] could not be opened, because the original item cannot be found" with the option to fix or delete the alias. Either one would fail, though, with an alert that I didn't have the right permissions to modify the XP machine. I am completely stumped. Any ideas of how to fix this?

We have 7 macs here. 6 of which can view and connect to windows shares via smb w/out any problems. One has been giving us a problem and I can't find a solution anywhere.

Using apple + k I can connect using smb://serverName/shareName on all 7 machines. I cannot however, connect using smb://serverName. This only happens on certain servers. The other 6 machines can connect w/out any problem.

When browsing through the network and trying to connect using the alias, where it specifically says "To see the available shares for server [SERVERNAME], press Connect" I get the following error message for this one machine:
"The alias [SERVERNAME] could not be opened, because the original item cannot be found."

When connecting via apple + k I get a -36 error...Finder cannot complete the operation...read...write...

Here is the console.log message that occurs when trying to connect and view the shares by either browsing through the network or using apple + k:

mount_smbfs: session setup phase failed: syserr = Permission denied
mount_smbfs: could not login to server [SERVERNAME]: syserr = Permission denied
mount_smbfs: session setup phase failed: syserr = Socket is not connected
mount_smbfs: could not login to server [SERVERNAME]: syserr = Socket is not connected

We get by by typing in the full address (smb://serverName/shareName), but one has to remember the share name.

Does anyone have any idea why this one machine is acting up? And is there a solution. I'm at the point of formatting the drive and starting over.

Thanks

[ashoush]

Sometimes the -36 error has been known to be solved by deleting the Keychain entry for the server affected (it fixed my problem).

Pat


Pat-

Thank you for this. It worked like a charm.

[hkd]

Here is the way I managed to solve it for myself (connecting from Tiger to XP Pro).


1. Click Start, and then click Run.
2. Type regedit, and then click OK.
3. Navigate to the following key:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\LanmanServer\Parameters
4. In the right pane, double-click the IRPStackSize value.

NOTE: If the IRPStackSize value does not already exist, use the following procedure to create it:a. In the Parameters folder of the registry, right-click the right pane.
b. Point to New, and then click DWord Value.
c. Type IRPStackSize.

IMPORTANT: Type "IRPStackSize" exactly as it is displayed because the value name is case-sensitive.

5. Change the Base to decimal.
6. In the Value Data box, type a value that is larger than the value that is listed.

If you created the IRPStackSize value using the procedure described in step 4, the default value is 15. It is recommended that you increase the value by 3. Therefore, if the previous value was 11, type 14, and then click OK.
7. Close the Registry Editor.
8. Restart the computer.

[mikegodz]

Thank you, thank you, THANK YOU!!! :D You're instructions solved a problem I thought I would have to live with forever. How did you figure it was a registry issue?

[osxfan57]

It was a while since I posted my problem and it has long since been fixed. However, a related problem (at least I suspect it's related) has cropped up. I can see and connect to the XP machine no problem. But file transfers are painfully, exceedingly slow, either direction. Have no idea why. I have 100 Mb ethernet connections between the PC and Mac through a router. Other computers that guests bring over (laptops) that are XP boxes have fast normal transfer speeds with the Mac. But this one particular XP machine is super slow. Any ideas how to address this? Thanks.

[JeffFun]

Hi,
You say that your problem has long been fixed. Could you please tell me what worked for you? I have the same problem in that I have several external drives that all can be accessed wirelessly except for one which gives the "Sorry, the operation could not be completed because an unexpected error occurred (Error code -41)" message. Any help would be greatly appreciated.