Separate names with a comma.
Discussion in 'Mac OS X Lion (10.7)' started by ataboc, Jul 20, 2011.
I have heard that it has been disabled.
Is that true?
Has anyone successfully used SMB share with 10.7?
Pretty sure they removed samba in this version...it was horribly out of date
But, now we can no longer use Windows shared folders, unless we use FTP, which is even more outdated.
Not only does SMB work, but now there is DFS support too!!
Well, that's good then!
SMB3, which Boxee and XBMC rely on, is no longer on Lion.
You gotta manually install it, which is a pain, lots of Terminal codes.
Search "install samba 3 boxee" on google, probably top result.
smb works great with our 5Big Network 2
that's what i'll have to do.
They've got their own version of samba due to licensing constraints is what I've heard.
I've definitely connected to samba shares from Lion.
It's buggy though, but then I've always found Mac -> Windows connections via samba to be buggy.
I haven't had the samba shares show up in the shared list yet. I've been having to manually connect to them via the smb:// url. But I've had to do this many times with previous versions of OS X, so it's not like this is something amazingly new.
To suggest they've completely removed the only way to connect to windows shares is a bit silly though. I don't see how anyone could say that with a straight face.
I am having problems that seem to be SMB related. After Lion installation, my scanner cannot "see" my Mac on the network. Worked fine with Snow Leopard.
I can see SMB shares from Lion on Windows computer or iPhone (using NetPortal app).
I cannot see SMB shares on WDTVLive Player
I cannot open any SMB shares from Windows on the Lion
All of it worked in Snow Leopard.
If anyone has a solution or workaround, please post here.
When I upgraded my mac mini to Lion I could still access my Snow Leopard SMB shares on my iMac but when I upgraded my iMac to Lion I could no longer access the SMB shares from the mini anymore in Boxee. Turns out Lion uses a new version of SMB that the current version of Boxee doesn't understand yet. As a workaround I just mounted the shares on my mini into a local directory, e.g:
mount -t smbfs //<username:<pwd>@<imac_IP>/<smb_share> /<local_dir>
mount -t smbfs //firstname.lastname@example.org/share1 /local_mounts/movies1
then in boxee, I just add the local directory as a media source and boom...I'm back in business until Boxee adds support for this new version of SMB.
When I try doing this in Terminal it is giving me "usage" info on mount (it lists the various types of commands) as if what I'm typing in is unacceptable.
mount -t smbfs //"user":"password"@"192.168.1.1"/content/local_mounts/media
The above is what I put in with the exception that I altered the stuff above in quotes to be real stuff (i.e. instead of "user" I have wdtv, etc.)
For me, my MBP is no longer showing up on my Win 7 machine, it used to work fine under SL after enabling sharing in system preferences. Anyone with the same issue?
SMB was painfully slow when trying to access NAS. Lion blows.
No problems here using SMB to connect to Windows Server 2000, 2003, 2008, 2008 R2, or NetApps.
I'll seriously PayPal $25 to anyone who can get my shares working. I've installed Samba3 but just need help getting the config file and auto-launch going so my WDTV Lives can hit the shares again.
No problems with SMB here - in fact it is more reliable than in SL and fewer massive delays loading folder contents. There is an amusing dialog that occasionally comes up saying it can't find the share, WHILE I am quite happily browsing it and -I- can find it. This has caused no ill effects thus far - touch aluminium.