Benches macOS

15

Connect to Server vs mount_smbfs

apple Verified

Imported from the Apple Support Forums via the Wayback Machine 🔗

Using 10.4.2, trying to connect to windows shares via Connect to Server (Apple+K) suddenly stopped working. I am either receiving Error -36 (instead of the authentication dialog), or complaints that my user id/password are wrong, depending on the share/server.

What is strange is that I am able to connect via Terminal ONLY when I use the -I switch.

e.g. mount_smbfs -I <host> -U <user> -W <domain> //<server>/<share> <mount point>

I have tried creating the /etc/nsmb.conf file as seen elsewhere in the discussions, and put entries in /etc/hosts and /etc/lmhosts. Trying to connect via IP, FQDN and e.g. smb://<domain>;<server>/<share> makes no difference at all.

How different is the finder connect method from the raw mount command, and is there another workaround/manual fix? An hour on the phone with Apple Care only resulted in the dreaded "Archive and install" suggestion (which I was forced to do last month to resolve another issue).

Many thanks to all in advance,

LJR

15 replies

Sign in or join Beachball Help to reply.

  1. 0

    Christophe THEVIGNOT

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi,

    I have the same problems! I have read that it might be linked to the "packet signing" and/or the security policies from the Win 2003 server. I still don't have an answer!

    Christophe

  2. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, packet signing certainly does have something to do with it, but there must be another work around. However, as stated above, if NetBios resolution is disabled with the -I switch via the command line, I am able to connect, and even navigate to that share via the Finder.

    So basically, what I am looking for is somewhere else in the system where I can specify the -I switch so Finder doesn't choke like its *Nix counterpart.

  3. 0

    Chris Wallans

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hey James,

    what value to you put in after -I??? what would be the host? As far as I know we don't have a host on our network.

    Thanks

  4. 0

    chairman rod

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I have tried creating the /etc/nsmb.conf file as seen elsewhere in the discussions, and put entries in /etc/hosts and /etc/lmhosts. Trying to connect via IP, FQDN and e.g. smb://<domain>;<server>/<share> makes no difference at all.

    Complete SWAG - have you tried putting LMHOSTS in /usr/lib/samba ?

    From the man page:

    lmhosts is loaded from the configuration directory.
    This is usually
    /etc/samba or /usr/local/samba/lib.

  5. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    the parameter after "-I" is the server name or IP that has the share.

    (if you don't have a host on your network, what would you be trying to connect to?)

  6. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Thanks for the suggestion - will try when I return to the office. At this point, any edumactated guess is appreciated 😉

    BTW - UNhappy to report that nothing has changed with the 10.4.3 update, as others in the forum have noted.

  7. 0

    chairman rod

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Trying to correlate problems with SMB from different posts -

    you mention using mount_smbfs ... does it work using smbclient from terminal ?

    smbclient //shared/directory -W workgroup -U username -d4

    When using smbclient, it
    does try to read from /etc/lmhosts

    startlmhosts: Can't open lmhosts file /private/etc/lmhosts. Error was No such file or directory

  8. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Yes, smbclient also works, but once again only with "-I"

  9. 0

    chairman rod

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Did you run it with d4, and did it try to read your /etc/lmhosts ?

    Just curious.

  10. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I do not need d4 from the command line to successfully connect.

    And yes I tried /etc/lmhosts which makes no difference.

  11. 0

    chairman rod

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    yes, I know you don't need d4, it's (obviously) debug information. And, according to the debug, when I ran the command it said it attempted to read /etc/lmhosts ... so... I was just wondering whether the debug gave you enough info to determine whether /etc/lmhosts was being accessed, and if not, why not....

  12. 0

    Langley James Rock

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Forgive my ignorance.

    Here's what I found:

    FROM TERMINAL:

    with debugging, the system does complain about the entry not found in /etc/lmhosts, then tries to look the server up via WINS. Still fails.

    added entry to /etc/lmhosts and changed ownership to root:wheel

    connection string no longer complains about host lookup, and now can connect (via terminal) without specifying -I switch.

    FROM Finder (CTRL-K):

    Still broken, but now worse: Before, if I mounted the share via Terminal, I could access the share via the Finder.

    Now, the mount point completely disappears entirely from the GUI, and is only available via the cd command in Terminal, or if I do a finder "Go to folder". With the latter, at least I get the mount point back and have it show up (too bad Apple chose to remove the refresh command).

    Egad!

  13. 0

    Todd Andrews

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    I've been able to use Finder to access Windows shares (and I access them constantly) since 10.3 and all updates through and including 10.4.2. But since 10.4.3 I'm getting the error -36 problem. Here's what the console log shows:

    -----

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mb
    getmem(449): incomplete copy

    mount_smbfs: can't get server address `STARMAN-II':

    Unknown host

    mount_smbfs: can't get server address: syserr = Network is down

    -----

    I have verified that the mb
    getmem message is placed in the console log at the same time I try to use Finder to connect to the Windows share.

    The only way I can get around the error -36 through Finder is to mount a share manually through Terminal, and I have to specify the IP address of the Windows machine (since it's saying it can't get the server address) in order for it to work. I created a script that looks like this:

    -----

    [ ! -d /volumes/$1 ] && mkdir /volumes/$1

    mount_smbfs -I 10.0.0.2 //user:password@starman-ii/$1 /volumes/$1

    -----

    Eventually I'm hoping for a more permanent solution so I won't have to keep a script around that has a password hardcoded into it.

    What has changed in 10.4.3 to cause Finder and mount_smbfs to not be able to resolve the netbios name?

    I'm also experiencing the problem another poster reported where the mounted share doesn't appear in the GUI (Finder).

  14. 0

    Christophe THEVIGNOT

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Hi,

    I still have got the same problem with my iMac G5 10.4.3 when trying to connect to our Windows 2003 server on our LAN. I could join the Active Directory domain. But, I cannot browse shares on the Win 2003 server and I cannot see the printers available on the LAN. I can do it via the terminal not from the finder. I can also do it using Sharity 3 for example. All other Windows and FreeBSD clents are able to do it without any problem!

    When I try from the Finder I get from the logs I got this:

    - smb
    smbnegotiate: server configuration requires packet signing, which we dont support

    and this:

    - mount_smbfs: error from NetrShareEnum call: exception = 382312522

    - mount_smbfs: tree connect phase failed: syserr = Permission denied

    - mount_smbfs: could not login to server BRU-MAIL1: syserr = Permission denied

    Best,

    Christophe

  15. 0

    Peter Wadsack

    Imported from the Apple Support Forums via the Wayback Machine 🔗

    Here, connecting to smb server via <command>-K from Finder has not worked since 10.3.9. And it still doesn't in 10.4.3. ftp has worked fine, in either direction.

    Reading this thread, I tried what worked for some of you.

    -- no luck with mount_smbfs from terminal:

    mount_smbfs: session setup phase failed: syserr = Authentication error

    with console reporting

    mount_smbfs: session setup phase failed: syserr = Authentication error

    mount_smbfs: session setup phase failed: syserr = Socket is not connected

    mount_smbfs: could not login to server WM-WARP: syserr = Socket is not connected

    -- with smbclient from terminal,

    smbclient //wm-warp/p -W ibmpeers -U peter -d4

    the debug shows some searching on Tiger's part, but it then resolves the correct IP and port, and I get to a smb: > prompt.

    This, however, has no effect whatsoever in finder.

    Perhaps I'm putting the wrong thing into 'go to folder' - what SHOULD go there?

    Whatever SMB issues Apple claimed to resolve with 10.4.3 [they weren't specified], it doesn't appear to have fixed mine.

    Oh, if it wasn't clear from the above, the server is running OS/2 Warp peer.