Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

SMB mount failure workaround Network
I couldn't mount an SMB share on a linux box from my Panther install for love or money. I tried all the suggestions I could find (eg command-K instead of browse, using the full path, change workgroup name in directory services, etc.), and none of them worked.

I'm running 10.3.5, connecting to an SMB share on a Linux box. I can browse and see all the different domains and shares, but I can't log onto them through any of the different GUI options. What I could do was create a folder in my home directory (let's call it XYZ) and then, in Terminal, use the following:
mount_smbfs -W DOMAIN //USER:PASSWORD@MOUNT/SHARE /Users/YOURUSERNAME/XYZ
Replace the words in CAPS with the appropriate ones for your circumstances. This essentially mounts the share and connects it to the named folder. Which when double-clicked on will browse that share.
    •    
  • Currently 3.00 / 5
  You rated: 3 / 5 (6 votes cast)
 
[22,044 views]  

SMB mount failure workaround | 6 comments | Create New Account
Click here to return to the 'SMB mount failure workaround' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
SMB mount failure workaround
Authored by: tamás on Sep 13, '04 01:35:01PM

I and others have had problems connecting the shares with long names. If you can, try shortening the share name on the sharing computer and see you are then able to mount properly. I believe the error I am describing might be on this hints forum in a discussion about "error -50"?



[ Reply to This | # ]
SMB mount failure workaround
Authored by: wsdr on Sep 13, '04 01:40:48PM

I've been beating my brains out on a related issue which involves tunnelling smb over ssh. Here's the deal:

I create a tunnel to one of my church's PowerBooks like so:

sudo ssh -L 139:192.168.0.101:139 root@church.addr.org

Where 192.168.0.101 is a Win XP box with a share established and church.addr.org is the public address of my PowerBook.

But when I try to connect from my local desktop using Connect to server like this:

smb://localhost
or
smb://localhost/SHAREDDOCS
or
smb://guest@localhost/SHAREDDOCS

or even:
smb://workgroup;localhost/SHAREDDOCS

and every other iteration of localhost, 127.0.0.1, workgroup no workgroup, etc., I get this error each time:

The Finder cannot complete the operation because some data in "fill in the above" could not be read or written. (Error code -36).

If I take my computer and go onsite, I can connect with just:

smb://SERVER

And it works great. I can also do this from the computer that is my SSH tunneling machine.

As part of my SSH tunnel, I also add -L 5900:192.168.0.102:5900 to tunnel my VNC and it works great, so I am confident that my SSH tunnels are working.



[ Reply to This | # ]
SMB mount failure workaround
Authored by: dfbills on Sep 13, '04 02:06:44PM

Looks to me like you need to include the increase port number on the local machine and specify it locally to get the traffic routed through the tunnel.

Try this:

sudo ssh -L 139:192.168.0.101:10139 root@church.addr.org

then connect with:

smb://localhost:10139



[ Reply to This | # ]
SMB mount failure workaround
Authored by: Dan B on Sep 13, '04 02:52:01PM

SSH tunnels TCP traffic, but SMB mounting currently (as of 10.3.5) involves UDP queries which are not tunneled. What you are describing was possible with 10.3.3 and earlier (I know because I used to do it, and now it no longer works).



[ Reply to This | # ]
SMB mount failure workaround
Authored by: imacusr on Sep 14, '04 06:22:24PM
The problem might be with the way 10.3 handles localhost as an alias (see this hint for details). Try changing 'localhost' in your example to '127.0.0.1' and see if that makes a difference; it worked for me when forwarding VNC over ssh suddenly broke after upgrading to 10.3.

[ Reply to This | # ]
SMB mount failure workaround
Authored by: imacusr on Sep 14, '04 06:23:53PM

Ah, n/m; I see that you already tried with both 'localhost' and '127.0.0.1'.



[ Reply to This | # ]