Previous 1 2 3 Next 132 Replies Latest reply: Jun 29, 2015 3:24 AM by Ben.Stratton-Woodward
upeace Level 1 Level 1

Prior to installing Lion, I would connect to our shared drives at work via SMB.  Today, after installing Lion, I can't connect to my shared drives.  The one SMB connection that works is to an FTP server.  I connect via SMB to map the drive in my Finder rather than using an FTP program.  This still works fine.


However, I can't connect to the shared drive for file sharing.  In the Connect to Server box, I have "smb://PathToFiles" .  Is smb://  the correct prefix to use now that Lion is funky with SMB support?


I'm sorry...I really don't know much about SMB connections, what kind of server it is that I'm trying to connect to, or much else.  I know we run Windows Exchange, but I'm not sure if that's the server that hosts these shared drives...I just need to connect to get back to work.  Any help would be AWESOME.

Solved by upeace on Aug 10, 2011 3:27 PM Solved
I (or I should say, my IT guy) finally fixed my problem!  I outline the solution in as much detail as I can on my blog: .  Basically, all I need to do is go into my Terminal and manually mount the drive.  I have no idea why this works though Terminal and not through the Connect to Server panel, but it does.  Since it's so simple, I'm expecting a Software Update from Apple soon to fix the problem for good. I hope this helps any of you who are in the same position as I have been (frustrated out of your mind).
Reply by Governa on Aug 1, 2011 1:59 PM Helpful
For those of you trying to access SMB shares, I found a free and easy solution. Since a lot of people report they are able to access their NAS using apps other than the Finder itself, I decided to look for a free Lion-compatible File Manager to use instead of Finder. I have found muCommander ( ) and indeed it works fine. All I did was click on the button highlighted bellow, go to "bonjour services" and select my NAS. It prompted me for my username and password and voilá, it works fine.  I keep Finder for everyday use and just load muCommander when I want to access the NAS. At least now I don't have to start my WinXP VM anymore just to access it. Hope it helps you all.
Reply by upeace on Aug 2, 2011 7:13 AM Helpful
I have posted this problem on my blog along with a more complete review of Lion.  Hopefully it will attract some more attention to the issue, and maybe someone will leave a solution in the comment section there.  If so, I'll be sure to update this forum with the info.

All replies

  • Daryl12345 Level 1 Level 1

    The same for me. No SMB connections to 2 Windows 7 PC's. Only and old Win XP PC is connected via SMB.

    But it takes 8 Minutes before my new Lion detects the XP PC.


    Help would be really apriciated...

  • fernin8r Level 1 Level 1

    Same for me.  This is not good.  I really need to connect to my office network drives.

  • upeace Level 1 Level 1

    Okay, so here's some follow up info after talking with my IT department.


    The server that I'm trying to connect to is 2008 Windows File Server.  We employ Active Directory for permissions and validation.


    My IT guy thinks that the reason that I can connect to the FTP side of things via SMB is because, in that case, I have root-level access to the content.  In all the other directories that I'm trying to access, I do not have root level access.  Something with the way Lion is connecting is not properly working with Active Directory and denying me access to the folder.  He said that this same problem existed on OSX 10.4, but had gotten significantly better in 10.5 and 10.6.  In his opinion 10.7 is a major step backwards.  I would have to agree.


    Obviously, the solution to this problem is not to have IT give me root level access...that defeats the purpose of permissions.  I also cannot expect my IT department to recalibrate settings on our server to help me fix a problem that Apple caused.


    I'm leaning towards reverting back to 10.6 Snow Leopard to solve this problem.  I'm definitely kicking myself for jumping on Lion so early...I just wish that I had known about this problem before installing.

  • Monty1945 Level 3 Level 3



    I'm a Network Manager/Engineer, in an AD Domain, and SMB works fine for everyone that needs to be able to access their shared drives. "Root Level, or not". I've not had a single complaint about Lion, with mapping drives, dropping WiFi connections, etc - so far it all works as advertised.


    You might want to rejoin the domain, and see if that helps. We didn't have to do anything here, and it all works fine, in Lion.





  • Bob Bousfield1 Level 1 Level 1

    Hi there,


    Can I ask if you have tried an unbound Lion machine connecting to these shares?



  • upeace Level 1 Level 1

    Hi Monty, thanks for chiming in. 


    What if my machine is not on the domain?  I ask that question isn't. 


    We are a very PC-centric organization, so Macs have always been more "tolerated" than anything.  If we can get them to work on our network, that's usually good enough.  For that reason, none of the Macs in our building are actually on the domain.


    As Rob asked, have you tried any machines that are non-domain?

  • krusty19k Level 1 Level 1

    Hi, I've got a similiar problem after I set up Lion...


    I've got a PC, running Windows NT (I know, it's old, but I can't change/update it) and with Lion I can't access to its SMB sharings... No problems with Snow, no problems with Windows XP, and no problems with Windows 7 Pro (but I had to change this settings in Admin Tools


    There is a way to enable access to old sharings?

    Or a way to "downgrade" to Snow Leopard's Samba?


    Thanks, have a nice day...

  • maybeapreacher Level 1 Level 1

    I have something to add:


    connecting with Lion to a "Windows Server 2008 R2 SMB Share" without a Domain works just fine in our local network.


    We have several locations we are connected with through a VPN tunnel. When trying to connect to a "Windows Server 2008 R2 Share" with or without domain in a remote network, that does not work.


    In our VPN here there is nothing blocked, all ports are going through. But since there is no difference between a 2008 R2 IN a Domain or NOT in a Domain I would blame the VPN and not the Domain.


    But since every port is open I can't pinpoint where it comes from.


    So, any help apreciated, and hopefully my information helps getting answers for other as well!


    Have a nice day

  • Xeno_22 Level 1 Level 1

    I heard that Lion only supports SMBX - whatever it is...


    I also can't connect to my samba fileserver with an avahi broadcasted SMB service.

    But my Samba broadcasts itself, and that way works here.

  • maybeapreacher Level 1 Level 1

    smbx is version 2.0 of the smb protocol.


    The problems out there that lion can't connect to NAS Systems is because most manufacturers just implement smb 1.x.


    But Windows Server 2008 is smb 2 (smbx) out of the box, so that can't be the problem!

  • Piccolib Level 1 Level 1

    I`m having the same problem at my office!


    I`m the only one using MacOSX and the rest network are windows based, i just cant print and acess files on teh server!


    I would apreciate any help!

  • Robert Jordin Level 1 Level 1

    Having the same problem here.  Was able to connect to my office via VPN -> SMB before Lion using Snow Leopard and aft the Lion upgrade...nada.  Can connect to the VPN (Cisco) but that is as far as it gets.  May have to go back to Snow Leopard was well.


    I really wish the first rule of upgradeing was "do no harm..."


    Any help would be appreciated.  Everything else in Lion worked fine, however, this is huge.

  • upeace Level 1 Level 1

    Ok, so here's an interesting update.  I took some screenshots to help communicate what I'm trying to say.


    There are two key folders that I'm trying to connect to via SMB.  One is a public folder, which is accessible to anyone on our domain, and the other is a departmental drive.



    Connect to Server.png


    Now, when I push "Connect," I get the folder that indicates that I do not have permissions to view the contents.





    However, when I toggle the folder view, I can actually get into the folder.  In other words, simply changing the view to thumbnail view instead of column view, the folder contents appear.



    Public 2.png


    This little "hack" however, does not work when trying to access the departmental folder.  I would have to guess that this is because my departmental content is two folder levels above "nyfiles" while the public content is only one level...?


    Does this help any of you see what the problem might be?  I'm really getting tired of having a PC sitting next to me all the time to move files back and forth that my Mac can't connect to.  However, I'm scared to downgrade to Snow Leopard and potentially lose data.  So, if anybody (maybe someone from Apple...hint, hint) can give some advice to resolve this, that would be amazing.

  • Robert Jordin Level 1 Level 1

    Just found out that my attempting to log on to my files at work via SMB, you know, way I could using Snow Leopard, was causing the the Windows server to panic and was asked to stop trying.  A fix would sure be nice..

Previous 1 2 3 Next