Skip navigation

smb shares on servers inaccessible after mountain lion upgrade?

167264 Views 218 Replies Latest reply: Nov 16, 2013 7:07 AM by mpvecchi RSS
  • ilgfo Calculating status...

    Alberto, hello fellow italian!

     

    I understand it makes absolutely no sense - i am puzzled and i am not BS'n.

     

    My scenario last night trying SMB was at home over a hardware VPN back to my office.

     

    The syntax i used was the only one that worked, i swear on my daughters life. i havent rolled backwards to my original config to try and break it but here are the changes i made on my mac last night.

     

    1. Tried every smb syntax possible with no luck

    2. I went to my wireless adapter and added my internal DNS server as secondary DNS, primary is my ISP

    3. I added my domain.local to search domains in the same tab

    4. I also changed the netbios name to a shorter version and under workgroup i used my netbios domain name.

     

    tried syntax again with no luck and started playing and the one i mentioned work. I will gladly post a video if ya dont believe me. When i get some spare time i will roll all settings back and disect this and post. There are alot of posts that make zero sense to me here. Now if someone can tell me how to hack activesync to connect to exchange 2003 on my mac i would be in heaven! We are not going to Exchange 2010 until last quarter of this year :-(

     

    Arrivederci!

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    This is what I got using your syntax. 192.168.6.241 is Win2008-R2 server

     

     

    smb://192.168.6.241:Administrator

    001.png

     

    That does produce the same result as smb://192.168.6.241

     

    The following string smb://Administrator@192.168.6.241

    got this. The username box is already filled with Administrator

     

    002.png

     

    If I also type the password smb://Administrator:secretpassword@192.168.6.241

    I get this

     

    003.png

     

    and... smb://Administrator:secretpassword@192.168.6.241/Share

     

    004.png

     

    I'm connecting to the remote Win2008 server through a VPN

    iMac, OS X Mountain Lion (10.8.2), iMac12,1
  • ganjubasoff Calculating status...

    set right system time on mac and windows server!

  • Kosta88 Level 1 Level 1 (0 points)

    I also have a very weird issue. I am new to OSX and have ML running now. Everything is fine except ONE thing.

    I can access my SMB shares, access other computers, cross-platform, File Browser iPad, I tested whatever I was able to find.

     

    However, there is one thing that I can't get to work, no matter what I do!

     

    I own a QNAP NMP-1000P multimedia player on my TV, and this thing works great with Windows. I can access all my shares, and as with any Samba, I just need an IP, path, login and password.

    However, when the same paths are shared on Mac, my Qnap can't access them.

     

    I tried everything I could think of, including creating an alternative user with sharing rights and sharing only those folders.

     

    Keep in mind, all shared shares, with any kind, work from other windows notebook and Apple device, but when it comes to accessing those same shares under the OSX, it fails, miserably and consistently.

     

    Anything I can do to make it work?????????

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    I guess you already updated QNAP firmware.

     

    Maybe the problem is related to the new OS X SMBX that superseded SAMBA since OS X Lion appearance.

     

    The QNAP user guide reports that you can also use NFS as a protocol to access remote sharing.

     

    NFS Manager is a graphical front end to manage NFS share on OS X.

  • Kosta88 Level 1 Level 1 (0 points)

    Indeed, the firmware is latest.

     

    SMBX - possibly, however weird that W7 machines *can* access it.

     

    However, in the meantime, as you noted, I used NFS Manager, and that worked out! (I wasn't aware of NFS existing under OSX until yesterday evening, I didn't even know what it is, I'm very new on this "UNIX" market, but learning fast!)

    Also alternatively, I can use SMBUp to create shares that are also accessible.

     

    Weird enough, both solutions work flawlessly, only the built-in one fails.

     

    A single question pertaining to NFS:

    If I assign for example /Volumes/Data HD/Movies to the NFS, I can read it with the QNAP, however I don't like the "unfriendly" name. Is it possible to map it to like /Movies or something? Similar to Samba, where I share a folder, and it is later accessible via xx.xx.xx.xx/Movies?

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    Kosta88 wrote:

     

    SMBX - possibly, however weird that W7 machines *can* access it.

     

    SMBX is Apple's implementation of SMB protocol and is not SAMBA.

    SMBX only support SMB2 while dropping support to SMB1.

     

     

    A single question pertaining to NFS:

    If I assign for example /Volumes/Data HD/Movies to the NFS, I can read it with the QNAP, however I don't like the "unfriendly" name. Is it possible to map it to like /Movies or something? Similar to Samba, where I share a folder, and it is later accessible via xx.xx.xx.xx/Movies?

     

    I never used NFS so I cannot answer to this question. It's not clear what do you mean with "unfrendly name", but I suppose that's the way NFS announces share points.

  • Kosta88 Level 1 Level 1 (0 points)

    Alright, so it's Apple again who f*cks us, lol.

     

    Is there a reason to drop a support for SMB1? I don't know much about it, but a simple quesiton if there was a reason?

     

    Well, imagine wanting to map a share on a device (Qnap) which doesn't have a keyboard, but only mobile-phone-alike keypad for typing in the name. Takes a while for each share, and I have about 5-6 of them. Once set up, OK, it's done, but looks terrible on the screen too. With Samba it would simply look like this:

    xx.xx.xx.xx/Movies-NAS

    xx.xx.xx.xx/Movies-Disk

    xx.xx.xx.xx/Photos

    xx.xx.xx.xx/Music-Router

    xx.xx.xx.xx/Music-Disk

    etc.

    Now with NFS, it would look somewhat like this:

    xx.xx.xx.xx/Users/xxxxxxx/Photos

    or

    xx.xx.xx.xx/Volumes/DataHD/Photos

    etc.

     

    It would be nice if I could map xx.xx.xx.xx/Users/xxxxxxx/Photos => /Photos.

    So it would again look like Samba eg:

    xx.xx.xx.xx/Photos

    I hope now it's a bit more understandable.

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    Kosta88 wrote:

     

    Alright, so it's Apple again who f*cks us, lol.

     

    That's incorrect. Apple moved away from SAMBA because Samba 3 was released under GPLv3 licence which prevent Apple from bundle it in a commercial product.

     

    Is there a reason to drop a support for SMB1? I don't know much about it, but a simple quesiton if there was a reason?

     

    Also the latest Microsoft Windows 8 and Windows 2012 do not support SMB1 anymore. I gave a link in my previous post which explains the technicalities.

     

    ...

     

    Now with NFS, it would look somewhat like this:

    xx.xx.xx.xx/Users/xxxxxxx/Photos

    or

    xx.xx.xx.xx/Volumes/DataHD/Photos

    etc.

     

    It would be nice if I could map xx.xx.xx.xx/Users/xxxxxxx/Photos => /Photos.

    So it would again look like Samba eg:

    xx.xx.xx.xx/Photos

    I hope now it's a bit more understandable.

     

    Yes. I got the point , but as I told you I never used NFS and I do not know the working details.

  • Kosta88 Level 1 Level 1 (0 points)

    Ah alright, I get it. Didn't know all those things, nice to learn more about it. So shortly said, if I had W8, I wouldn't be able to connect to my windows share from the QNAP, since it doesn't support SMB1?

     

    About the explanation, sorry, I misunderstood

     

    I will see on another forums maybe I can get an answer to that. Meanwhile, SMBUp is working fine, I can access everything.

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    Kosta88 wrote:

     

    So shortly said, if I had W8, I wouldn't be able to connect to my windows share from the QNAP, since it doesn't support SMB1?

     

    Right.

  • dsavi Calculating status...

    Samba supports smb v2 since version 3.5. Recent QNAP installations are running Samba version 3.6.3. This cannot be the reason for the non-working smb shares.

  • Kosta88 Level 1 Level 1 (0 points)

    Nevertheless dsavi, the shares are working via SMBUp, they work with windows 7, they are *not* working with OSX native. I am now using NFS, via NFS manager as both are native to OSX and QNAP. Working well, except that it won't resume the movie when stopped, like it usually does with Samba. NFS is however much faster.

  • Alberto Ravasio Level 4 Level 4 (3,160 points)

    Samba 3.5 was released on March 1st, 2010 and contained an experimental implementation of SMB2.

     

    QNAP NMP-1000P is approximately a mid 2010 product. I doubt QNAP was an early adopter of the new Samba version, and usually, updates for older products don't get major system enhancements during their lifetime.

  • Kosta88 Level 1 Level 1 (0 points)

    I'm actually also quite happy to be away from Samba. It's quite slower and less responsive than NFS, for example start/stopping/fw/rew on MKVs on the Gigabit network is via NFS way faster than it's with Samba, even on the lowly device like DNS-323. The difference from the computer, be that windows or OSX, is like 3x faster when loading the movie...

Actions

More Like This

  • Retrieving data ...

Bookmarked By (10)

Legend

  • This solved my question - 10 points
  • This helped me - 5 points
This site contains user submitted content, comments and opinions and is for informational purposes only. Apple disclaims any and all liability for the acts, omissions and conduct of any third parties in connection with or related to your use of the site. All postings and use of the content on this site are subject to the Apple Support Communities Terms of Use.