SMB Share

Samba support IS there in lion. From what I understand, the license for the GPL samba project changed and apple could no longer distribute it with OSX. Therefore, they wrote their own implementation from scratch for lion. Unfortunately, it doesnt seem to work very well yet...its very fussy when trying to connect to samba shares especially on windows computers.

I'm not sure what kind of issues you are having but I don't have any problems when I connect to my MBP from my Windows 7 machine? I turn File Sharing on on my MBP, and I've added folders and adjusted r/w access accordingly. Then from my Windows 7 machine I click "Map network drive", input the IP address listed within the Sharing Preference on Lion along with the shared folder (ie. \\10.0.1.20\SharedFolder), and then check the box to sign in under a different credentials and input my Lion username and password. Then I'm connected. What issues are you running into?

I upgraded to Lion. I didn't add or remove any shared folders.

For testing purposes I just added a folder and connected to it. Worked fine for me. I'm not sure if it makes any difference but the username and password on both machines are the same.

What the **** are Apple playing at??? This has completly wrecked my home network!!! ****! How could they screw up SMB and not expect some angry users???

I cant connect with any of the following to SMB shares on my Mac:

Windows7 Pro 64 bit,

XBMC on chipped XBoxes

None of these will even authenticate to Lion to list the available shares.

I can get on with Linux Mint10 (based on UBUNTU), but not as guest, I have to authenticate, and I can only access shares on my main OS X drive. I cant access shares on my external firewire drive, or follow links in my shares to the external drive.

I'm going to log a support call, and if there is no resolution quickly I'm getting my money back.

I can't connect my 6 Tb of media files to my living room media player any longer, it just can't find the Lion iMac while my two other Snow Leopard macs appear immediately. I rang the Apple support line on another issue yesterday and the guy said there would be an update within a week to address this SMB matter and other issues. I had cause to ring the line again today and the operator I got knew nothing about the problem but he too expected an update within the next couple of weeks to address all emerging issues.

I agree with Mista2 that it seems inconceivable that they didn't anticipate the havoc this would cause for various network attached devices. My problem is a frustrating inconvenience though not a big deal but for someone who had a critical business need it would be potentially devastating.

Check to see if you can open any files on the share, and if there is any difference with large or small files.

The biggest of my problems is because I use my Mac Mini as a media hub and file server, (as that is where iTunes is), and was an easy box to setup under snow leopard, and was small and quiet. Now this is completely broken and I've had to move all my media to a slower USB drive and share it form my airport instead (the only other box on the network that is on all the time) and then update the mappings on every device that connects to it. What annoys me most is this looks like it was seen in beta and the GMs and not fixed by Apple.

I was using Snow Leopard and Parallels desktop 6 prior to upgrading to Lion. Now when I save files to the SMB share I used to use, all files are corrupted. If I instead use the drive from Parallels, \\psf\Host, it works like before.

Here is an example of a corrupted file (which I first of all thought was a problem in my script editor software):

http://pastebin.com/MraCG12C

The corruption occurs since files aren't truncated when you write to them.

If you try to create a file using the following commands from the command prompt in Windows, you can clearly see that it overwrites the first bytes in the file without truncating it first.

Repro of the error:

net use s: \\mac\share /user:macusername

cd s:

echo a > test.txt

echo b >> test.txt

type test.txt

a

b

echo FAIL > test.txt

type test.txt

FAIL

b

This leads to files like the one I included a link to.

I wouldn't recommend using SMB shares with WRITE access until this is confirmed as fixed.

READ access from a SMB share on the Mac is no problem. Only when you start writing to it.

So Im hoping as Apple had one million downloads of OS X 10.7 over the last few days, thy might spend a little of their 30 million profit in fixing this massive bug.

However based on the features they left out intentionally on other products, Im not holding my breath.

I wonder If I'm just holding my network wrong? Or if noone was expected to do anythign as oldfashioned as share their drives with other operating sytstems.

Definitely issues with Apples new SMB implementation. I have managed to get SMB working and will try to explain what I think is happening.

As best as I can tell, when we try to map a SMB or CIFS share from the GUI, it appears to send the username and password of the logged in user. It appears to completely ignore any username you add to the url.

The ugly work around (Mount from the CLI)

Fortunately for us, there is the CLI method. You will need to open terminal for this.

First we need to make a place to mount the share to. When you first open terminal, it should place you in your home directory.

Lets make a folder called "data" by entering the following:

mkdir data

In my case, this will have created a folder in my home directory named "data". Now that we have a folder to mount the share to, lets get down to business. Below is the command used to mount a share. I'll explain it:

/sbin/mount_smbfs //myusername@myserver/share data

myusername is the username you need to connect with.

myserver is the server name or IP of the server you wish to connect to.

share is the share name you wish to connect to.

data is the folder you wish to mount this share to, in this case we created "data" as the mount point.

Give this a little time after hitting enter, it will prompt you in the terminal to enter your share's password. As you type, you will not see anything on the screen, but it is taking the password. Once you've completed entering your password it will mount to the folder you specified. You can access your files from in this folder, or if you have set Finder to show mounted shares on the desktop, you will see it on the desktop as well.

The only other odd thing here, is it does seem to have issues with then trying to mount another share from the same server with the same username. It has allowed me to mount other shares with another username on the same server. Really odd.

Not an elegant work around, but it at least gets us to our files. Here's to hoping someone at Apple eventually answers.

Just occured to me. If you are using Time Machine, you might want to exempt any mount points you create. I'm not sure if it won't try and back them up.

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 ( http://www.mucommander.com/ ) 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.