Lost access to our CIFS Server with Lion

I have the same problem with an EMC NAS. I don't know what the solution is. I will monitor this thread to see if anyone else proposes a workable solution.

I am in same situation too...

please give me a solution......

For now the only way I could access my server was go->connect to server and manually type its address. like smb://192.168.1.100. Didn't work for afp, only samba. if you know the name of the share you want to access you may try to type after the address: smb://192.168.1.100/share_name. hope it works for you too

Sorry to be dense, but are you sure? Samba has been removed in Lion, so smb mounts should fail. The Internet is full of reports where what you described will not work with Lion, and that is my experience too, as well as two colleagues who are also trying the same thing at work. Did you install your own Samba on your Mac?

Stanley,

EMC has a zero day already in place.

More information is available here - link

and on PowerLink.

Best regards,

Drew

I try this on terminal I map a symbolic link to NexentaStor 3.0.5 ok

Mackinado:~ macalister$ mount_smbfs //bio:**********@stor001/documentos /Users/macalister/Desktop/Documentos

Mackinado:~ macalister$ ls -l /Users/macalister/Desktop/Documentos

total 1418624

-rwx------ 1 macalister staff 461948 5 Mar 2010 BOG_PDF_6.2.rar

drwx------ 1 macalister staff 16384 27 Ago 2010 BioSEC

drwx------ 1 macalister staff 16384 15 Nov 2010 Business

drwx------ 1 macalister staff 16384 15 Nov 2010 Documents

drwx------ 1 macalister staff 16384 24 Nov 2010 Livros

drwx------ 1 macalister staff 16384 16 Nov 2010 Nova pasta

-rwx------ 1 macalister staff 80 9 Dez 2009 Novo Documento de Texto.txt

drwx------ 1 macalister staff 16384 24 Nov 2010 PDF

-rwx------ 1 macalister staff 595265546 1 Dez 2009 Procedimentos_syi.rar

drwx------ 1 macalister staff 16384 25 Nov 2010 TEMP~LMV

drwx------ 1 macalister staff 16384 24 Nov 2010 TEMP~MMV

-rwx------ 1 macalister staff 12249088 9 Dez 2009 basil-poledouris-hymn-to-the-red-october-the-hunt-for-the-red-october.mp3

-rwx------ 1 macalister staff 6809 1 Nov 2010 biologo.jpeg

-rwx------ 1 macalister staff 131072 5 Mai 2010 bkp.bin

drwx------ 1 macalister staff 16384 3 Jun 21:37 bkp20101006

drwx------ 1 macalister staff 16384 16 Abr 15:43 bkp20110416

drwx------ 1 macalister staff 16384 16 Mai 02:33 bkp20110516

drwx------ 1 macalister staff 16384 15 Nov 2010 bkphd120

but look this

Mackinado:Documentos macalister$ ssh admin@stor001

Password:

admin@Stor001:~$ su

Password:

root@Stor001:/export/home/admin# cd /volumes/Dados/Documentos/

root@Stor001:/volumes/Dados/Documentos# ls -l

total 709549

-rwxrwx--- 1 bio stor 461948 Mar 5 2010 BOG_PDF_6.2.rar

drwxrwx--- 7 bio stor 23 Aug 27 2010 BioSEC

drwxrwx--- 24 bio stor 69 Nov 15 2010 Business

drwxrwx--- 4 bio stor 20 Nov 15 2010 Documents

drwxrwx--- 4 bio stor 19 Nov 24 2010 Livros

drwxrwx--- 2 bio stor 5 Nov 16 2010 Nova pasta

-rwxrwx--- 1 bio stor 80 Dec 9 2009 Novo Documento de Texto.txt

drwxrwx--- 13 bio stor 52 Nov 24 2010 PDF

-rwxrwx--- 1 bio stor 595265546 Dec 1 2009 Procedimentos_syi.rar

drwxrwx--- 4 bio stor 33 Nov 25 2010 TEMP

-rwxrwx--- 1 bio stor 12249088 Dec 9 2009 basil-poledouris-hymn-to-the-red-october-the-hunt-for-the-red-october.mp3

-rwxrwx--- 1 bio stor 6809 Nov 1 2010 biologo.jpeg

-rwxrwx--- 1 bio stor 131072 May 5 2010 bkp.bin

drwxrwx--- 26 bio stor 110 Jun 3 21:37 bkp20101006

drwxrwx--- 23 bio stor 105 Apr 16 15:43 bkp20110416

drwxrwx--- 4 bio stor 4 May 16 02:33 bkp20110516

correct USER used on NexentaStor and correct Permissions.

Mac Lion try use a current mac user and mac controls on server before authentication on terminal mount or command-K cifs://stor001 and a Nexenta CIFS server reject this configuration.

How to correct this ?

I not try configure a same uid and gid NexentaStor user.

NexentaStor001

root@Stor001:/volumes/Dados/Documentos# id bio

uid=1001(bio) gid=10(staff) groups=10(staff),1001(stor),1002(cica),1004(documentos)

Macbook

mackinado:Documentos macalister$ id macalister

uid=502(macalister) gid=20(staff) groups=20(staff),403(com.apple.sharepoint.group.2),402(com.apple.sharepoint.gro up.1),

12(everyone),33(_appstore),61(localaccounts),79(_appserverusr),80(admin),81(_app serveradm),98(_lpadmin),100(_lpoperator),

204(_developer),401(com.apple.access_screensharing)

We're having the same issues connecting to a Nexenta SAN. We're authenticating via a Windows domain.

Authentication works, because we're mounting the share point, but the access permissions are screwed up.

I'm not sure where the issue lies because when you connect via a Mac joined to the domain, even the ACL list shows correctly in Terminal:

-rwx------+ 1 johnson PHARMACY\Domain Users 22105 Apr 19 2010 toxicall error 4-19-10.JPG

0: group:authedusers inherited allow read,write,execute,delete,append,readattr,writeattr,readextattr,writeextattr,re adsecurity,writesecurity,chown

1: group:PHARMACY\Domain Admins inherited allow read,write,execute,delete,append,readattr,writeattr,readextattr,writeextattr,re adsecurity,writesecurity,chown

By these ACL's I should have full rights to this file; I can open it but not change it, and the finder won't let me into the folder at all.

A system running 10.6.8 connected to the same SAN as the same user has no problems at all.

hi

changing from the indirect NAS naming (e.g. smb://NAS-XX-YY-ZZ for Ready NAS Duo), to the explicit IP address e.g. smb://192.168.111.1 from Finder "Connect to Server" will then allow you to access your NAS device shares (subject to your NAS security settings)

Hopefully Apple will pay attention to this, although AFP works most of the time, it can (and does) get confused and requires a reboot, where as CIFS is quite reliable.

Peter

Nope, this did not fix the issue. I'm not having problems connecting; I authenticate and it's connected fine, but for some reason the permissions are all screwed up.

OS X THINKS that everything is locked on the share, even thoguh when I check the permissions and ACL's in terminal they seem to be correct.

Ah HA!

Like 20 seconds after I posted the last reply I discovered the root cause of the issue: 10.7's versioning system; but it requires a strange sequence of events to puzzle it out.

Connect to the server, it will tell you it's locked, and won't let you past the root level of the share.

Put the Mac to sleep.

Wake it back up.

Voila, you can navigate the mounted volume.

If you now open a file it says it's locked.

I can make changes to it, and OS X asks me if I want to unlock it to save the changes,. If I select unlock, itr lets me save it.

If I close and re-open the file, it's unlocked, but if I try to save changes OS X says 'The document <document name> is on a volume that does not support permanent version storage. You will not be able to access older versions of this document once you close it."

Then it lets me save the changes.

NOW I think I can start isolating the bug here...

Did you ever come across a solution to this problem? I'm having the permissions problem with Lion/Nexenta as well.

Thanks!

I can't even get to the point where I am given the opportunity to provide my access credentials. I have a case open with Apple. They are analyzing logs and packet dumps I sent earlier this week, but still no solution.

The only solution to this issue I've found is the one in my post.

If you cannot access the share at all, most likely it's the DHCP128 authentication method issue. If you're getting the locked folder, go into Terminal and see if you can browse the mounted share in /Volumes. If you can the bus is the same as mine.

For me, and a lot of people in my office, Lion simply will not even attempt to mount file shares (Windows or NAS). It simply displays an error that the file share cannot be found. No mount occurs, nor is any attempt made to authenticate the requester. I have been working with Apple engineering on this issue and it is very clearly a problem with Lion, which is why the first-level tech support guy at Apple who is handling my case referred this issue to an engineer.

Part of the issue is there are at least three bugs I've run across with this issue:

1) There's a bug authenticating against NAS devices with a deprecated encryption scheme.

2) There's a bug(s) with the new Versions stuff in 10.7 that's cropped up (an Apple engineer has confirmed my supposition in my post on the 18th.)

3) There are bugs in Apple's new Active Directory code. (at least one of which I've run into)

I've been told all three of the specific bugs I've encountered are tentatively slated for fixes in 10.7.2, hope your issue is one of them.

Of course, no idea WHEN 10.7.2 is coming out...