SMB File Sharing on Lion

Accoding the solution with muCommander...

Which "bonjour service" did you choose? I guess the "nameofyourcomputer"[SMB] and which user/passwd did you use (see the following screenshot)

I had the same problem with my Maxtor Shared Storage NAS.

Since upgrading to Lion I was unable to connect to the network shares defined on the Maxtor NAS.

I read somewhere on the Internet that the new Apple implementation of Samba is buggy, since, when connecting to a SMB share, it does not use the username that you enter in the "Connect to server" dialog box in Finder, but instead it uses the name of the logged on user in MacOSX.

So I defined in the NAS a new username, identical to the user name that I am using in MacOSX, and I was able to connect to my network shares in the NAS exactly as it worked with Snow Leopard, and without the need to install other software.

I hope this helps ...

I think that Apple should be ashamed.

In the passed I was a heavy Windows user.

Bought my first Macbook Air last year with Snow Leopard.

Amazing how goot it works and how nice bonjour and smb......Everything was easy and I became a real MAC fan.

Could easely reach my Linux server at my work and use the MAC Secure CRT as a terminal for using my Linux counter software.

THIS ALL ENDED WITH LION.

No support to fixe it and there was no warning from Apple that SMB would not be in Lion.

Otherwise I would not have spend my money for lion.

Afther 4 months waiting for a fix I diceded tot go back to Snow Leopard.

Everything is working again but it took me two days to install all the aplications again (including Parrallels and Windows) and so on.

This is NOT what Steve Jobs mentioned when he proclaimed that a MAC is easy and the user should only be buzy doing nice things on a MAC and not be buzy installing and fixing.

I don't want to be working with terminal ore what so ever to get my MAC to do what it is supposed to do.

The helpdesk of Apple: ask your Networkspecialist......That would be me.....and I have no clue

So Apple: Be ashamed of youself and give me back SMB to do my work, using the features of Lion including iCloud.

I am not sure if this will be helpful but I have found a very simple solution from my IT guy. I am running a Mac Mini with Lion 10.7.2.

I awoke this morning to find that the SMB network drives (enterprise) that I previously mounted to could not be accessed. After looking around and trying many of the solutions mentioned on various forums, my IT suggested the following:

In the 'Connet to Server' dialog box, I had previously typed:

'smb://shareddrive/folder'

He suggested a simple change by adding the full qualified domain name (example):

'smb://shareddrive.institutionname.org/folder'

This worked!

Now, let's hope it keeps working

Hey Vmac, good info thanks.

The domain resolution is probably a new requirement - that's not actually too much of a 'bug'.

From my end Samba still works - no apple updates have broken it yet.

Apple has basically stepped back from the server market completely, if you want a server, look elsewhere. Yes Yes they have the mini, but no ext3/4 /reiser file system support and no good native RAID - that puts them squarely in the toy category.

So my little server toy works great, but all of the important things I get outside of Apple, very sorry to say.

If you look at iCloud, it doesn't run on apple hardware, or even their software. In a way this is a good thing - they are focusing really what they are good at, and they never really 'got' the server concept.

Yeah thanks Vmac, good stuff - sure it'll help lots of people.

What i personally not getting to work is connecting to a WDTV mediaplayer.. The player recognizes the iMac, and lets me authenticate - but that's it - never get to browse the shared drives.

I can't edit the way the mediaplayer connects - specifying domain name or anything.

I've just installed Lion and found that I could no longer access my Maxtor Shared Storage NAS device via SMB. It kept giving "permission denied" errors, and it I couldn't find a way to re-enter the desired user/pass even after deleting the old network password from the keychain.

The solution finally that worked for me was to specify the NAS username and password in the "connect to server" address string: i.e. smb://user:pass@server.address/share.

Hope this helps someone else

I had the same problem: WDTV live, OSX Lion on my Macbook, no chance to get the Password authentification for SMB sharing right. This little program did the trick for me:

http://code.google.com/p/ps3mediaserver/

Just install it and select the folders you'd like to share, there's even an simple option to share the itunes Library. No I'm able to stream all my movies, photos, songs etc. from my Macbook to WDTV live.

I have the same problem, No matter how I configure the share, my wdtv live reports either that the share is not there or is incorrectly reported as empty.

Hope they fix smbx in an update. Ports + samba3 is a PITA for something which should work out of the box.

This did the trick for me, too.

It's not as elegant as having it all available in the Finder (as in Snow Leopard and previously), but it solves my issue of being able to access the files on the WDTV Live from my MacBook Pro.

Hi madp01,

Can you possibly remember and find where you read the information about Apple SAMBA not using the username from the "Connect To" box?

I am having problems connecting to a Samba share based on credentials from my corporate LDAP server. I've been suspecting that Apple was mangling the login credentials (which have worked fine since Leopard). I would love to find any further confirmation of this.

Thanks,

Thanks. I did see those. Right now, I'm trying the solution of adding my username to the URI before the server name. Just username, but not password. The connection process still went to my keychain for the password. We'll see if that fixes my problem.

Well, in my case the issue is different: when I try to connect to my Maxtor NAS, it just doesn't connect as if the username or password are incorrect. No message is displayed and there is no error message in the system.log file.

The only way I was able to make it work was to define in the NAS the same username that I use on the Mac.

It seems however that it may also work by connecting to the network share using the command line interface (in terminal), but I have not tried yet.

This behaviour is with Lion, when I had Snow Leopard it used to work fine.

Yes indeed this is not the same problem as mine.

in my case I connect with Guest user to the shared drive.

Anyway could you try if in Terminal is working :

mount_smbfs //Username:Password@ServerName/SharedDisk /Volumes/MAXTOR

(make sure that folder MAXTOR exists before executing this command)

For exemple in my case I use this command:

mount_smbfs //Guest:@THOMSON/Disk_a3 /Volumes/THOMSON

I use EyeConnect which is similar to PS3 server. I have PS3 Server installed as well but it doesn't seem to work as well. Two problems. While this allows me to stream content via UPnP, subtitles aren't supported in UPnP. The alternative then is copying files over to a drive attached via USB to the WDTV Live. I also find this solves a lot of problems as far as speed, and isn't interrupted if my MacBook Pro is turned off or doing something else processor intensived. But now in 10.7.4, the finder doesn't see my WDTV Live anymore. So the only way to copy files to it seems to be to unplug the cable from the WDTV, plug it into the Mac, copy over the files I want, and then plug the drive back into the WDTV Live. This is a major step backward from Snow Leopard where everything just WORKED. I really hope at least one of these companies is looking for a solution. There are lots of things I like better about Lion, but there are a few really stupid things too. For example I can't seem to find a way to default search by file name instead of contents. I know there is a pull-down menu, but it means that I have to take my hand off the keyboard every time I do a search. It's just seemingly little things like that that end up being really inconvenient. But for a number of reasons I can't go back to Snow Leopard now, so all I can do is wait for a solution.