SMB Share

The shell scripts (CLI) which use the mount_smbfs seem to work better. The SAMBA software which used to respond to these commands as well as the GUI UI commands was replaced by a completely lame Apple software server. Why Apple could not understand the value in SAMBA is beyond me.

I am going to try to replace the SAMBA software.

For now the below commands seem to work well at rhe "terminal" window or you can put them in a file ad make that file executable.

Edit a file (mountmovies) and add this line:

mkdir /Volumes/movies; mount_smbfs //pcooper:xxxxx@qnap/movies /Volumes/movies

Where "movies" is the name of the remote share and "pcooper" is the user on the remote server

and xxxxx is the password on the remote server for pcooper. The server name with the files is "qnap".

then in utilities/terminal

$ chmod +x mountmovies

You can put this on your Desktop folder and double click it. I would reccommend making sure the terminal app in the utilities folder has it's preferences set to close upon normal exit. You can add multiple lines in this file for more shares. They get mounted in order. I keep one username on the remote device since Apple broke the OS by removing SAMBA. SMB shares on OSX are also problematic.

PS if you are good with UNIX scripts all of these things can be passed into this script. Unfortunately, I would be called antiquated by thinking to use the best CLI ever created; so therefore I will say that the UNIX command line interface is far beyond the scope of this post. Of course no one knows how to do many things anymore since most of the younger generation seems to want to learn nothing hard. It's called de-evolution and the USA is good at it.

I had the same problem and it took me a while to find a fix, but the fix is easy. You just need to remove all the shares and start over with them.

Go into Sytem Preferences -> Sharing. Select File Sharing and remove all the shared folders.

Then add them back.

Click on Options and select "share via SMB". Select the user name(s) you want to share as. You'll be prompted for a password -- be sure to enter it correctly.

Then go to your windows machine, disconnect the network drive if it's still visible. Reboot (it's Windows...) Then reconnect the network drive as ususal.

That's what worked for me. All the other advice about mounting from the command line and script files didn't work, and seemed oddly complicated and very un-apple. Lion's new SMB works, you just have to start fresh with it.

While resetting the shares on Lion has made them visible from Windows 7 I'm still having some issues.

Certain software I am using cannot locate files if I configuration the search paths pointing to the Lion "server". Theses files are visible from Windows explore but for reasons unknown the software cannot find them. It MAY be a case sensitivity thing but it was not an issue in 10.6 Something in 10.7 SMB is definitely not working the way it did in 10.6.

Apples support solution to me was "copy everything local", yeah right thats a good "fix".

Man... it's exactly the same here. I work with mac and windows (3ds max) and can't connect to Lion through windows (xp and 7). All along hours and hours of lists and googling, can't find nothing. 2 hours on the phone with Apple "technical people" and... NOTHING.

The ONLY FULL WORKING SOLUTION IS.......... back to Snow!

I'm so happy now that everything is working 100%. Not so happy cause lost tons of hours looking for a solution and another tons reinstalling all apps and configurations and files, etc... but now I'm back work and fully operational. Can't calculate the money lost on this stuff. Arrrgggg @%@$@%!@

This seems to be getting worse instead of better. After a few shutdowns and restarts on both sides I can no longer see or access Lion SMB shares. Previous working mapped drives no longer connect and are requesting a user name and password. I key in valid names and passwords but they are getting rejected.

Apple has seriously screwed up SMB to the point were there is no point in even trying to get a windows machine to connect. Guess it's back to PC's if I want to stay in buisness.

This is CNET's quote:

"On the bright side, Apple will no longer by trapped by the limitations of Samba. For example, the version of Samba currently bundled with Mac OS X can run into issues with PCs running Windows 7 that are set to Microsoft's most secure options for file sharing. Apple now has the opportunity to address this shortcoming and perhaps introduce its own innovative improvements to networking between future versions of Mac OS X and Windows."

I don't plan to embrace this statement -- at least not now and maybe not until Lion goes through several patch and upgrades. My opinion is that the previously release of Samba would have been better than what the consumer actually received in Lion first release. Then Apple could have taken time to really get the software up and running without the disruption currently being experienced. Maybe with the current Samba and the GPLv3 that stops a commercial product, Apple was stuck and needed to make a decision. Having software that takes care of the really secure options in Microsoft when is cannot even connect with the simplistic shares and securiy is reasonably useless. The decision to take the intracies of the SMB protocol lightly was not so good. I would like a return to the Samba on Snow Leopard as i putforth in another thread even an optional install of the down release Samba. Anyone listening? I tried sjobs at apple.com to no avail. Maybe there is someone at apple on these discussions.

Some more diagnosis

When using Lion as a SMB "server" for Windows.

If I restart the Lion "server" I must toggle SMB file sharing off and on again for Windows to be able to access the shares. I must do this after EVERY startup.

If I don't stop and restart the SMB services Windows Network cannot see the server. Previously mapped drives will prompt for user/password but Lion will not authenticate even if the user and password are correct.

Even after connecting some of my software is still having problems accessing data on the server.

What ****** me of most about this whole deal is the Apple Tech I spoke with would not acknowlege there was a problem. He also told me they had nothing in the support database or THIS forum indicating that there were any problems with SMB.

More info.

From what I can tell OX 10.7 is running a daemon smbd (a smb daemon) but I do not see the daemon nmdb running. My 10.6 system uses the samba daemon nmdb.

There is a new man page for the smbd damon but information in it is very limited.

The file com.apple.server.plist contain the NetBios info.

I cannot find where the share information is stored but it appears to me that smb.conf and smb.shares are no longer used.

I cannot believe they even said this. I have an entire thread on this. Both sides of removing SAMBA is a train wreck.

While I can see every shared folders on both sides, I have to log with a different account on the Mac and if I copy files to the Mac they're only permitted to that account and are unreadable on the Mac side unless I start changing manually permissions. I cannot log with the same admin account on both machines. I also cannot enable SMB as it rejects the password even though that's the exact same one I logged in with.

If you want we can take this offline as I have compiled and built Samba on nearly every UNIX platform. I am not familiar with this lists rules on postings but I may jump in and replace the SMB Daemon with the original SL version of sambs for my SMB netwiorking. I see just too many problems and lion has yet to have a patch release.

BTW smb.comf is the SAMBA configuration file where there were many many flags and configuration options which Apple did a tremendous job of shipping predominant set of microsoft networking facilities. If you want I will be glad to help.

Is it fixed or?

Running 10.7.2 (11C37)

Created a new user, called it user.

Made the new user a sharing only user.

Made a password, called it user.

Went to System Preferences, Internet & Wireless, Sharing.

File Sharing checked on left.

Plus ➕ under Shared Folders, added external firewire hard disk.

Users on right, added user (user named user as staed above).

Gave "user" Read/Write permissions.

Clicked Options.

Checked both boxes, AFP and SMB.

Checke user named "user".

Dialog box requested password, I typed it in (as staed above, I maded it "user".

I can now see, access and have all the same functionality I had with Snow Leopard via a Windows 7 box connecting to a OSX Lion share!

What changed?

Is there an issue with the 'Administrator" privedledged account called "my account" (as an example), because if I check THAT box, the SMB dialog box requesting a password says incorrect, as previously stated here and everywhere in the world.

Is it possible that when Snow Leopard got upgraded to Lion and the Time Machine backup that migrated all of the user data, etc., to the newly updated Lion, and I could not use the SAME USER NAME, so I made a new user name, yet I called the "nickname" the very same nickname that was used in the previous Snow Leopard install, could that maybe have created the problem?

I'm now very, very confused.

Searching all of these forums, posts, etc., reading the issues regarding even Apple support not "fessing up" to even acknowledging an issue or problem, yet all major magazines, discussions, etc., talk about it, complain about it, and experience it, yet now it's fixed? Or is it not an am I in a Black Hole?

Anyway, now after 3 days, still is working, both ways, Windows 7 to a iMac, and an iMac to a Windows 7 PC.

I can see shared drives each way, copy files each way, etc.

Does anyone else have the issue resolved?

Nope. And my collegues' brand new MBA 11" shipped with Lion is having the same problem.

He's using Windows 7 in a VirtualBox VM on his Mac and when enabling SMB sharing he gets the same file corruption issue as me.

The issue is that if you WRITE data to a share on a Mac you will have a corrupted file if you shrink its size.

Say, if you save a textfile with the content "abcdef" it will be stored as expected on the Mac. However, if you edit the file in notepad and replace all the content with "123" the file on the Mac now contains "123def".

For a batch script example of this issue, please refer to my previous reply in this thread.

I switched to Mac in May and I feel very concerned about the lack of any kind of response from Apple regarding this matter. If I, as a developer, would report anything like this to Microsoft Connect (or even MSDN Forums) I would definitely get a reply from a MS representative. The same goes for any open source project at github. You would get a reply almost immediately. What is Apple doing with all its billions? I mean they aren't spending too much money on staff responding user questions in these forums.

According to Apple the Netbiosd and the smbfs_mount shipped wilh Lion have no problems. I just hope that the .1 or patch release (whatever .2,.3,...) have address all the "no-problems" we are experienceing including the horrible open speed of a share on a windows or Samba/Linux machine. Why didn't Lion come for free with a $29 initial 60 day 2 call support pack. Then GPL3 and Samba would have been addressed and all of the "no-problem" customers would have been saved thousands of hours tracking down bugs and only to be told that the issues do not exist when factual support is presented. The predominance of the folks who don't use microsoft networking would have been no burden.

For serving up files off of apple machines (from an apple machine) I had to enable the Apple File Protocol or afp://aple-machine/share. For my linux Samba machines I set the security to plain old Wotkgroup and use smb://linux-samba-machine. My NAS has AFP has never been very reliable. It does not help a Windows machine connecting to the new netbiosd on the Apple Lion Machine. I believe there is a down grade in Lan Manager LM security on a windows machine that works in that case. It is posted previously or in another thread. I'm not sure whether a corporate policy will allow this downgrade in security but for many it will help.