Can't connect via SMB

Hi, I have Active Directory on Windows Server 2008 with DFS file share, some Windows and some MAC computer. Till 10.6 using dfs via finder cmd+k and smb://server/share works fine for all user.

Now with LION my Windows-Admin-Account works still fine. No problem.

BUT if I login with another account (maria) with less rights I got errors on some shares. I find out that maria has no read right for the root folder on the problem-shares.

OK-Share: maria has at least read right on the root folder! ( Traverse folder / execute file )

Problem-Share: maria has only the following rights on the root folder.

List folder / read data, Read attributes, Read extended attributes.

For some subfolders has maria of couse more rights.

We use this settings, because nobody should see folders where he/she have no access rights. With other words everybody see only the folder where he/she has access rights and the other folders not.

Till Lion a good solution ;-)

Now I map the share ( with errors ) and Finder can´t access the share. But with Terminal or muCommander I can access all sharefolders.

Hope Apple bring a fix soon.

kkausu

@ Eduardo

Regardless of their reasons for ommision of a proper bona fida SMB process, it is INEXCUSABLE that it hasn't been fixed yet. Apple are acting so irresponsibly in dealing with this and many other issues with Lion.

To release this pile of cat crap to unsuspecting business users who can now no longer access centralised company resources other than by utilising USB keys and the like is quite frankly shocking. We have a ridiculous scenario where we have had to set up ad-hoc folder sharing on OSX and manually place files via USB keys into these folders because we can't access out €3000+ NAS drive.

Our NAS drive is on a FIXED IP address. So how the **** can it not see the file share? Linux can connect, android phones can connect, PC's can connect, even an old Atari ST can connect, but can the €2000+ iMacs? Can the Mac Pro's? Well, yes some of them still running 10.6 can connect, anything using 10.7 are useless.

Pathetic, there is no other way of describing their behaviour.

Apple, if you are listening, keep the **** away from industry, you are starting to remind me of my Windows 3.1 days. I have a new catch phrase for Apple, "It just won't work"

Cross posting from: https://discussions.apple.com/thread/3196311?answerId=15810135022#15810135022

~~~~~~~~~~~

After several full Saturdays and Sundays chasing this down (and about 300 restarts), I have my Windows to Apple SMB Share connectivity issue narrowed down and worked around. This applies to OSx 10.7.0 and 10.7.1 on a MacMini (7/2011 Server w/SSD) with Shares under SMB, being connected to by Windows 7.

Basic Environment:

IF

1) you restart OSx and your Windows systems CANNOT connect because you get a prompt for userid/password or a not accessable message AND

2) after 2 or 3 minutes you can Start and Stop SMB Sharing with either Server.app (File Sharing) or Preferences/Sharing/File Sharing/Options/SMB on/off (individual IDs do _not_ have to be turned on / off) AND

3) the userid and password are exactly the same on both the client (Win7 or OSx) and the Sharing system AND

4) then Windows sytems can connect

Then the problem is a Race Condition in the Services Startup of OSx. The SMB service is dependent on some security process (guessing) which is completely late in the startup cycle.

You can test this with the following commands in a terminal window (AFTER the system is up and quiesced):

sleep 60

sudo serveradmin stop smb

sleep 5

sudo serveradmin start smb

After talking to Apple Enterprise Support to confirm the issue, I moved the above commands into a launchd script as a work around (this is NOT recommended unless you know what you're doing). Note the initial 60 second sleep - 30 seconds was not long enough. This has been filed with Apple Enginering, they'll figure out what to do about it going forward.

Part of my problem, is that I'm on a new MacMini (7/2011) which boots from local SSD, it just boots up too fast. If you're on a slower older system - this should not be an issue.

Some other things which I learned on this journey:

1) Do not use unload/load of the SMB plist - that does not work for this issue

2) OD accounts do not work. Wish they would, they dont

3) Hacking the windows registry as in previous versions to support the previous Samba SMB release (10.6.x and lower) is NOT the problem with any 10.7 release. OSx 10.7 Supports SMB2, as does Vista and Win7.

page 2 of this link

https://discussions.apple.com/thread/3197723

And here is the text that I wrote in it in case you still can't see it.

I had problems with this a few months ago so I took time off to not think about it. Now, I've returned to this and I must have had magic under my fingertips.

For my Lion to Windows XP Pro file sharing, it looks like I found a fix on my end.

1. First, I went into Sharing > File Sharing

I added my Public folder since I must have removed it some other day.

2. Next, I went into Network and removed my existing Wifi connection and created a new one.

Then I went into Advanced, TCP/IP > set Using DHCP > Renew DNS Lease and then added my WINS Workgroup name.

3. I went to Go>Connect to Server>entered my PC's local IP address as smb://###.###.#.###/ and BINGO! I have a connection. It connected to my PC as a Guest even though my Guest login is turned off on my PC.

It didn't ask me for a login info like it used to under Snow Leopard.

Now, I'll wait and see if my connection disconnects. So far, it's been 15 minutes and still have a connection.

I hope this helps someone else.

>>> Note: Since finding this solution, my network connection with Windows XP Pro SP3 has not been lost. It's been 8 days and my Mac is still connected to a Windows share folder as I write this <<<

Skazzy,

In my case, the SMB share I am accessing is hosted by a Linux box. The changes must be made on the server hosting the share you wish to access. Here are the steps I took:

1. Using terminal, SSH into the Linux box.
2. Type (without the quotes): "sudo vi /etc/avahi/services/samba.service"
3. Arrow down until you get to the section of XML included in my post
4. Press the letter i to enter insert mode
5. Change <port>139</port> to <port>445</port>
6. Press Esc to return to command mode
7. Type :wq to write your changes and quit.
8. Restart the avahi service using whatever method your Linux distro supports
9. Exit the SSH session
10. Mount your SMB share in Finder as before.
11. Have a beer.

Our Windows7 computer always has issues connecting when it's turned on. We are able to log in every time if we do the following:

• press Windows + Break key
• change settings
• select network ID
• select this computer is not part of a domain
• enter "WORKGROUP" as the workgroup name (or whatever your workgroup is for both Mac and PC)
• restart the computer
• the computer should connect with any account on Lion Server (username/password)

This is painful, but it works everytime for us. Apple is aware of this and working on improving SMB.

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.

Hi,

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.

Cheers,

M.

*****

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 http://technet.microsoft.com/en-us/library/cc738867(WS.10).aspx)

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...

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

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!