Windows 7 Guest Access to SMB Share

I have a 10.8 server setup. I have a share that is available via both AFP and SMB. I have guest access turned on. Why can't I access this share as a guest using Windows 7? Am I doing something wrong?
Windows 7 client is bound to an AD domain, but the Mac Server is not, it is stand alone.
How can I access the guest SMB share with Windows 7 client?
Thanks!

If lagagnon's suggestion doesn't work, I would say try this:
[global]
client lanman auth = no
client ntlmv2 auth = yes
Where I work we are on an Active Directory in which *only* NTLMv2 is allowed to authenticate, and Samba clients must explicitly set "client ntlmv2 auth = yes" in order for them to connect to shares.

Similar Messages

KVM Windows Guest access through VPN

It it possible to access a KVM windows guest through a VPN???
Thanks

Your inspections doesn't include http?

10.4.6, Guest access, ACLs, SMB connections andpermissions problems.

I applied the 10.4.6 Combo update to our Tiger Server sometime last week. Since then Windows
users connecting to the server have been complaining that they are unable to drag files created by Macs into various folders because of permissions errors.
None of the clients are bound to the server, everyone connects as Guest.
Clients are a mix of 10.2.8, 10.3.9 and 10.4.6 on the Mac side, and Win XP Home SP2 and Pro SP2 with all current security patches. Some of the Macs are using MS Office running in Classic mode. ACLs are used on the shares.
Obviously the first place to look is the ACLs, which may be setup by me in a dumb fashion.
I have the "unprivileged" user from the NetInfo directory setup with Full Control over the share, and Deny just set to inherit. Until now this has worked as expected.
Have I got the ACLs completely wrong for this type of share scenairo, or has something got broken with the latest set of patches?
If so, what users or group should I be setting up when the majority of the incoming connections are guests.
XServe G5 Mac OS X (10.4.6)

re you saying I also have to have the root of the data drive set for the Everyone group to have Read/Write access?
No, just the share point needs the privileges you want set. By looking at your ls printout, you have both the file_inherit and directory_inherit controls set for the container folder (Public), so new files created within that container will inherit that ACL entry.
I should have been clearer about the meaning of "container": If fileA has path /Volumes/somedisk/folder/fileA, then folder is the container of fileA; similarly, if folderB has path /Volumes/somedisk/folder/folderB, then folder is the container of folderB. Some documentation refers to container as "enclosing folder." Being a container does not imply being a share point (nor vice-versa); the two are independent. If folder is also a share point, then somedisk is its container.
But back to the question: Your privileges seem correct for the ACL entry pertaining to everyone; however, I've noticed that Mac OS X systems will treat a folder as read-only if all read and write controls are set except for delete and delete_child (or one of them is disallowed via a deny rule). This is because a lot of applications perform Save/Save As in the following way: they create a new temporary file, delete the existing one, then rename the temporary file to the old one's name. Even the Finder reports such folders as read-only, although commands like mkdir and touch work. Even though applications can't complete their Save function, inspection of the affected directory will reveal that the temporary file was created. I think this is just a matter of applications expecting delete to come with the package of read and write; it's a valid assumption if the system is POSIX-only, but ACLs allow more flexibility. Perhaps in future releases of Mac OS X applications will be able to work with ACLs more effectively, rather than in a semi-POSIX manner.
One more thing: You can verify the structures of your volumes by using Disk Utility or diskutil verifyVolume /Volumes/volname. This is essentially the same test as fsck, since fsck calls diskutil when working with HFS+ volumes; however, diskutil offers live verification with Mac OS X 10.4.3 and later, and it sometimes provides more detailed output.
--Gerrit

Mac in Windows server environment with SMB shares

Hello Apple Support Community,
This is my first post here, so take it easy on me.
Here is a brief background before I explain the problem. I'm currently in an environment that has about 35 various Mac computers (Mac Pros, iMacs, Mac Book Pros, etc) from many different generations, but all running 10.8.2 or newer. The enviornment also has several Dell Servers running various OS versions (2003 Std, 2008 Std, and one 2012 Storage Server). Active Directory is currently in place and healthy. The 2012 Storage Server is where we are hosting all of the file shares. Users are connecting to these shares via smb.
We are experincing two problems that may or may not be related.
Problem #1
Occasionally (I have yet to find consistency), when we drag and drop a folder from one location to the other (on the same server, in the same share, and usually source and destination reside in the same parent folder) or if we rename a folder, we'll be prompt for credentials with the message "Finder wants to make changes. Type your password to allow this."
Since our local username and password are different then the Active Directory username and password used to connect to the share, I have observed that usually typing in the local username and password allows this prompt to go away. Any other username or password does not work. However, once the prompt goes away, the folder never actually moves on the share or is renamed. This prompt for a password will repeat over and over until you go away, do something else in a different folder, then come back after a while, then it won't prompt you for a password for the same move or rename operation.
I thought this might be related to permissions at first as we just migrated the data from an old Mac Server to this new 2012 Storage Server, but I have since replicated the scenario with a test share and a series of test subfolders that I just created (no files were involved in the test, just folders). I have also opened permissions to everyone for both the share and the folder structure for this test.
Problem #2
Similar to the scenario above, but rather than moving or renaming a folder or file, when we attempt to delete a folder it will occasionally pretend to delete, then appear back in the share as a folder that no one has permissions to. If you navigate away for a while and then return, the folder has actually been removed.
If anyone has any insight as to why we might be experiencing any of this behavior or direction for how to troubleshoot or solve this, I would greatly appreciate it.
Thanks!

Hello?
Anyone?
Bueller...Bueller....Bueller
It's been a couple of weeks now and no one has any input to help me? Is there something I can provide to get some additional help?
I've done some research over the past couple of weeks and ran into an article (sorry, I have misplaced the source) that indicated adding the Mac to the windows domain would help with Problem #1 by providing single sign-on functionality. I bound all of the macs in the network to the domain and changed all of the user profiles from local to domain. They are now logging in with their domian credentials. For the most part, this appears to have solved the problem. I will find out more tomorrow as there appears to still be one user experiencing the same behavior even after adding his Mac to the domain and having him log in with his domain account and credentials.
This is, however, how the problem started in the first place. It began with just this one user reporting the problem, then eventually everyone was having the problem. I'm no longer feeling confident that this has actually solved the problem.
I've implemented ExtremeZ-IP on the storage server and have redirected the users to using AFP again. This appears to have solved Problem #2.
We now have two additional problems showing up on the network.
Problem #3
Occasionally (again, having a hard time finding any consistency), after opening a file and working on it for a while, we are being presented with an error that a file cannot be written to. Once the error shows up, the problem is persistent. You can save the file as a different name in the same location, and it will take without error. You just can't save the file with the same name. It's as if the file is locked. If I reboot the windows server at the end of the day, the file that was locked no longer has a problem being written to.
We also see this problem with moving/renaming folders on occasion.
Problem #4
Users are reporting that files in a folder sometimes do not appear (the folder appears as blank), but appear fine for others.
I have seen this issue when users connect with different protocols (one with smb and the other with afp - the smb connected user usually doesn't see the file) but in the process of changing profiles from domain to local, I have switched all users to AFP.
I could really use some help with this situation. Anything this community has to offer, suggest, or otherwise help me find resolution would be extremely appreciated.

Windows Server Disconnecting Mac SMB Shares Randomly

The basic plot is I have a Mac Server sharing out files on AFP and SMB. I'm mounting one of those files shares on a Windows 2008 R2 server. Randomly the volume disconnects from the Windows server for a short period, somewhere around 20-30 minutes, and then reconnects. This happens 1-2 times a week.
I'm authentacation to the file share with user account 'Newforma". I have this same user account authentacating for files on other servers as well. At times one server will drop the authentacation while there is no issue with the other server. See the link below for a screenshot.
screenshot: http://redlinetech.files.wordpress.com/2013/04/smb_disconnect_01.jpeg?w=960
The Specs on machines:
Mac Server (dcfiles)
     Xserve2,1
     10.6.6
     Open Directory Master
     Services running: Open Directory, AFP, and SMB
Windows Server (STUDIOSDC10)
     HP ProLiant DL380 G6
     Windows Server 2008 R2 Standard
     Service pack 1 x 64
     Services running: setup as a Newforma Project Center Server, 9th edition.
My Windows server authenticates to our AD server for login, then files are mounted with authentication from our OD server. This does not cause any problems on the other windows servers and it's the same process that my desktop users have. They authenticate to AD for login, and OD for files. We do not bind AD or OD in any way.
Randomly though when I log into my Windows Server (DC10), There is a red 'X' on my mounted file share. If I double click I get an error message that the network volume doesn't exist. Nothing in the Windows Server Logs that I can find that point to an issue.
I believe the issue is the smb service running on my Mac 10.6 server (dcfiles). I think this because when my files are disconnected from the windows sesrver, I can try to authentacate to the Mac server from my mac desktop with AFP and everything works fine. But If I try to connect to the same file share with smb it doesn't connect. No error messages about wrong passwords or such, it never presents me with a login window. Just says the volume doesn't exist.
When I check the smb logs on the Mac server, I find this repeating over and over, it's pretty standard and in there all the time, even when I"m not having issues.
studiosdc10 (192.168.10.21) connect to service dcfiles initially as user Newforma (uid=1033, gid=20) (pid 69112)
[2013/04/08 09:30:16, 1, pid=69112] /SourceCache/samba/samba-235.5/samba/source/smbd/service.c:close_cnum(1289)
studiosdc10 (192.168.10.21) closed connection to service dcfiles
[2013/04/08 09:30:21, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=172 errno=34
[2013/04/08 09:30:21, 1, pid=69112] /SourceCache/samba/samba-235.5/samba/source/smbd/service.c:make_connection_snum( 1092)
studiosdc10 (192.168.10.21) connect to service dcfiles initially as user Newforma (uid=1033, gid=20) (pid 69112)
My concern is the line that says "failed to read DomainAdmin credentials, err=67 fd=172 errno=34". Though nothing seems to be actually be wrong. I can still authentcate to dcfiles with user 'Newforma' from my Windows server. Just worried that might point to something bigger.
I also run across these errors that have me a little more worried:
[2013/04/08 09:03:14, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirecto ry_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=137 errno=34
[2013/04/08 09:03:17, 0, pid=231] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:set_socket_options( 261)
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:set_socket_options( 261)
Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:send_smb(761)
Error writing 4 bytes to client. -1. (Broken pipe)
[2013/04/08 09:03:17, 0, pid=72622] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=19 errno=2
[2013/04/08 09:03:42, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=143 errno=34
[2013/04/08 09:05:20, 0, pid=71861] /SourceCache/samba/samba-235.5/samba/source/smbd/nttrans.c:call_nt_transact_ioct l(2537)
call_nt_transact_ioctl(0x1401c4): Currently not implemented.
What I've Already Tried:
     - Stopping and restarting the SMB service
     - Adding "smb ports = 139” to the smb.conf file on the Mac server
What I'm Considering Trying:
     - Deleting and recreating the the 'Newforma' user account from Workgroup Manager on the Mac server
     - Making the 'Newforma' user account an admin
     - Fearing I might have bigger authentacation issues, demoting my OD master to Stand Alone and re-pormoting to Master.
While I continue to research, document, and monitor the issue ..... any thoughts or ideas would be appreaciated.

The basic plot is I have a Mac Server sharing out files on AFP and SMB. I'm mounting one of those files shares on a Windows 2008 R2 server. Randomly the volume disconnects from the Windows server for a short period, somewhere around 20-30 minutes, and then reconnects. This happens 1-2 times a week.
I'm authentacation to the file share with user account 'Newforma". I have this same user account authentacating for files on other servers as well. At times one server will drop the authentacation while there is no issue with the other server. See the link below for a screenshot.
screenshot: http://redlinetech.files.wordpress.com/2013/04/smb_disconnect_01.jpeg?w=960
The Specs on machines:
Mac Server (dcfiles)
     Xserve2,1
     10.6.6
     Open Directory Master
     Services running: Open Directory, AFP, and SMB
Windows Server (STUDIOSDC10)
     HP ProLiant DL380 G6
     Windows Server 2008 R2 Standard
     Service pack 1 x 64
     Services running: setup as a Newforma Project Center Server, 9th edition.
My Windows server authenticates to our AD server for login, then files are mounted with authentication from our OD server. This does not cause any problems on the other windows servers and it's the same process that my desktop users have. They authenticate to AD for login, and OD for files. We do not bind AD or OD in any way.
Randomly though when I log into my Windows Server (DC10), There is a red 'X' on my mounted file share. If I double click I get an error message that the network volume doesn't exist. Nothing in the Windows Server Logs that I can find that point to an issue.
I believe the issue is the smb service running on my Mac 10.6 server (dcfiles). I think this because when my files are disconnected from the windows sesrver, I can try to authentacate to the Mac server from my mac desktop with AFP and everything works fine. But If I try to connect to the same file share with smb it doesn't connect. No error messages about wrong passwords or such, it never presents me with a login window. Just says the volume doesn't exist.
When I check the smb logs on the Mac server, I find this repeating over and over, it's pretty standard and in there all the time, even when I"m not having issues.
studiosdc10 (192.168.10.21) connect to service dcfiles initially as user Newforma (uid=1033, gid=20) (pid 69112)
[2013/04/08 09:30:16, 1, pid=69112] /SourceCache/samba/samba-235.5/samba/source/smbd/service.c:close_cnum(1289)
studiosdc10 (192.168.10.21) closed connection to service dcfiles
[2013/04/08 09:30:21, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=172 errno=34
[2013/04/08 09:30:21, 1, pid=69112] /SourceCache/samba/samba-235.5/samba/source/smbd/service.c:make_connection_snum( 1092)
studiosdc10 (192.168.10.21) connect to service dcfiles initially as user Newforma (uid=1033, gid=20) (pid 69112)
My concern is the line that says "failed to read DomainAdmin credentials, err=67 fd=172 errno=34". Though nothing seems to be actually be wrong. I can still authentcate to dcfiles with user 'Newforma' from my Windows server. Just worried that might point to something bigger.
I also run across these errors that have me a little more worried:
[2013/04/08 09:03:14, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirecto ry_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=137 errno=34
[2013/04/08 09:03:17, 0, pid=231] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:set_socket_options( 261)
Failed to set socket option SO_KEEPALIVE (Error Invalid argument)
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:set_socket_options( 261)
Failed to set socket option TCP_NODELAY (Error Invalid argument)
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:get_peer_addr(1224)
getpeername failed. Error was Invalid argument
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:write_data(562)
write_data: write failure in writing to client 0.0.0.0. Error Broken pipe
[2013/04/08 09:03:17, 0, pid=72621] /SourceCache/samba/samba-235.5/samba/source/lib/util_sock.c:send_smb(761)
Error writing 4 bytes to client. -1. (Broken pipe)
[2013/04/08 09:03:17, 0, pid=72622] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=19 errno=2
[2013/04/08 09:03:42, 0, pid=69112] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:get_opendirector y_authenticator(247)
failed to read DomainAdmin credentials, err=67 fd=143 errno=34
[2013/04/08 09:05:20, 0, pid=71861] /SourceCache/samba/samba-235.5/samba/source/smbd/nttrans.c:call_nt_transact_ioct l(2537)
call_nt_transact_ioctl(0x1401c4): Currently not implemented.
What I've Already Tried:
     - Stopping and restarting the SMB service
     - Adding "smb ports = 139” to the smb.conf file on the Mac server
What I'm Considering Trying:
     - Deleting and recreating the the 'Newforma' user account from Workgroup Manager on the Mac server
     - Making the 'Newforma' user account an admin
     - Fearing I might have bigger authentacation issues, demoting my OD master to Stand Alone and re-pormoting to Master.
While I continue to research, document, and monitor the issue ..... any thoughts or ideas would be appreaciated.

Can't access smb shares after 10.9.5 upgrade

After the upgrade to 10.9.5 (from 10.9.4) I can not anymore access my smb shares on a NAS server (Thecus N3200PRO) dispite the upgrade says that it "improves the reliability of accessing files located on an SMB server". It had the exact opposite effect with my system.
The NAS server is visible, but after I log in no files or folders are shown (finder window is empy). Also to disconnect the smb share it takes much longer than usual.
To access it with cifs protocol does not help, neither.
Also the workaround by Reinfire (Michael Larson in Can't connect to SMB share after upgrade, to use smb1 instead of the upgrade) does not help at all.
Any solution out there?
-- thanks

hi there,
just a wild guess, but have you tried to connect via Terminal?
/sbin/mount_smbfs //userid:password@ip-of-server/name-of-share
or
/sbin/mount_smbfs //userid:password@dns_name-of-server/name-of-share
You need to have administrative privileges on your Mac to execute said command successfully.
For additional information you can enter (while in Terminal):
man mount_smbfs
and
man nsmb.conf
Glad to hear the problem is solved

SMB Guest Access allowed but greyed out so cant turn it off

Hi guys
I have recently installed 10.6 snow leopard server to setup as a file server. It will be host to a mix of mac and windows clients.
I have installed and setup SMB service:
Role: Primary Domain Controller
By default, Allow Guest Access is ticked and greyed out. I want to disable it but I can click the box??
Any suggestions?
Thanks.
Rik.

I was in the same boat. Found the answer in Terminal (I'm assuming you know what you're doing there):
You can verify the settings by typing (NOTE: the serveradmin command must be run as root):
          serveradmin settings smb
Look for a line reading:
        smb:map to guest = "Bad User"
This indicates Guest Access is ON.
To disable guest access in SMB:
         serveradmin settings smb:map to guest = "Never"
I had to quit and reopen the Server Admin app before the change showed in the GUI.
-Axiom

Smb shares on OSX to Windows not working after upgrade

After upgrading to Maverick and OSX server 3.0 SMB file sharing is broken. I connect from Windows 7 to OSX SMB shares. Some shares work others only work with some folders on the share. Most folders display an error when trying to access the folders from Windows.
I checked file and folder permissions on OSX (finder and ls -l) permissions are the same.

@thePod7, your suggestion on Setting the Lan Manger Authentical Level worked! Only thing missing is the instructions on how to Set the Lan Manager Authentication Level. So I've included it below. Hope this helps someone else having the issue!
On command line....
1. Enter “gpedit.msc” in the Start Search box.
2. Open “Computer Configuration”/Windows Settings/Security Settings/Local Policies/Security Settings.
3. In the right pane, enable the following policies:
Network access: Allow anonymous SID/name translation
Network access: Let Everyone permissions apply to anonymous users
Also please disable the following policies.
Network access: Restrict anonymous access to Named Pipes and Shares
Network access: Do not allow anonymous enumeration of SAM accounts
Network access: Do not allow anonymous enumeration of SAM accounts and shares
Change the following policy:
Network security: LAN Manager authentication level
Change the value to “Send LM & NTLM - use NTLMv2 session security if negotiated”.

Guest Access

I have OS X Lion Server running on a Mac Mini. I just want to enable SIMPLE guest access to a share. This is for a home with Mac and Windows 7 PC's. I dont want user accounts, just using this Mac Mini (or trying to) as a simple file server/iTunes server.
I have created a share. I have enabled guest access. I have even given the entire drive/volume its on "Others" (or whatever it is) read/write permissions and reset the ACL's on the drive, with the share. Windows computers (Windows 7) prompt for a user name and password.
Why? I can login in with the admin account of the Mini server at Windows and get in....but I dont want to login.
Any help would be great!
Thanks,

No, need not have to buy any router. Just in order to show up the Guest Network you need to reinstall/reconfigure the whole router. While reconfiguring the router again make sure the existing Cisco connect should be uninstalled first and then follow the instructions provided in the link: http://www6.nohold.net/Cisco2/ukp.aspx?vw=1&docid=e30f926604334d538668529cb50ad174_21463.xml&pid=80&...

10.7.4 has killed my SMB Shares

I updated a server to 10.7.4 this weekend based on the release notes:
- Address an issue that may prevent files from being saved to an SMB server.
Instead, now my Windows users can't connect at all.
I've manually restarted the SMB service
- sudo launchctl unload -F /System/Library/LaunchDaemons/com.apple.smbd.plist
- sudo launchctl load -F /System/Library/LaunchDaemons/com.apple.smbd.plist
I've removed all my shares and recreated them.
I've restarted the server.
I've gone to Storage in Server.app and propagated the permissions on folders.
So far, none of the previous fixes I've used in the past have worked.
Additionally, my local Administrator can see all the shares, but my Open Directory Users cannot.
Anyone else have this problem or fix it yet?

Solution confirmed once again. Stopped the SMB service, removed SMB from individual shares, started SMB service, then added the option back to the individual shares. I was testing primarily from a Windows 7 client where the local Windows login does not match the Open Directory login being used to access the SMB share on my Lion server.
Once I knew I had some working SMB shares, I tested some different username formats, since I originally suspected that I was using the wrong format:
These formats did not work:
OD_DOMAIN\ODUsername
OD_HOSTNAME\ODUsername
ODUsername@OD_DOMAIN
ODUsername@OD_IPADDRESS
ODUsername@OD_HOSTNAME
The only formats that worked for me were:
OD_IPADDRESS\ODUsername
ODUsername
I find it strange that plain old ODUsername works, as this should pass the local machine name by default, thus my input would be changed to LOCALHOSTNAME\ODUsername. My Windows hostname does not match up with OD, so this shouldn't technically work...
As a control in my testing, I did not change the SMB sharing option from some of my shares, then tested these after the smb restart. Directories where I toggled the status off and back on again were working, while these "control" directories produce the following error when access is attempted (I tested from a Win7 machine). This error is produced before the authentication dialogue is presented:
\\IPADDRESS\Share
A device attached to the system is not functioning.
However, I when I applied this fix to all directories, this error is gone. I just found it strange that it was not revealed until I restarted the SMB service.
I'll have to test further to find out whether this issue is resolved permanently, or if it will come back at some point.

Weird privileges on SMB share

Hi everyone,
I am experiencing weird file access privileges on a Windows server accessed via SMB. *Get Info* shows more than 1 iteration of the same user(s) and groups with varying privileges. There are often problems with items that can not be deleted/moved/overwritten.
The weird privileges are kept when copying the file to the local Desktop. Then they obstruct TM from running successfully. I can see in the log that backupd has a problem (it provides the full path) and stops when it encounters such an item. If I remove all ACLs from the item (by using sudo chmod -R -N ./*) the backup runs fine.
The Windows admin can’t see the several iterations, i.e. he only sees 1 group, 1 user, etc.
Here is a sample screenshot of cmd+i:
Any ideas on how to solve this on the server side? I haven’t yet tried to use chmod on the server shares.
Thanks
Björn

Sorry for bumping this again. Does nobody have any idea what‘s going on here? A hint to point me in the right direction would suffice.
Thanks
Björn

SMB shares all mounted drives regardless permission set or not

Not sure if anyone encountered the same issue, tried google but no luck with it.
I enable the SMB in the "file sharing" on my iMac, and granted the read access to my public folder only. The reason I used SMB instead of AFP is the folder I want to share is on an external USB drive which is formatted as exFAT. When I try to connect to the iMac from my Macbook pro, i can see all the drives, including the internal hard drive and 2 external USB drive, and I can read and write in these drives.
Anyone have a clue why this is happening? Thanks

Thanks for the replies guys. I do not have a firewall enabled. I have some developments (Slight)
I have an SMB share on a windows machine. If I CMD+K and just do SMB://IP.Address then it ask me for credentials.
If I put in completely wrong credentials, the box just shakes when I hit OK.
If I put in correct credentials, it shows me a list of available shares (to that particular user) and then when I click the one I want and hit OK I get a popup "You do not have permission to access this server"
So its obviously taking the login in some way or another, just failing at another part.
I've looked in /var/log and the only log I can see that has anything relevant is system.log (Admittedly I didnt check them all as there are a lot)
I get the below message after a failed attempt to access an SMB share:
Jan 21 12:04:51 Carls-MacBook-Air.local NetAuthSysAgent[1042]: NAHSelectionAcquireCredential The operation couldn’t be completed. (com.apple.NetworkAuthenticationHelper error -1765328228 - acquire_kerberos failed carlnewton@EUDC1PCUBAC: -1765328228 - unable to reach any KDC in realm EUDC1PCUBAC)
EUDC1PCUBAC is the name of the computer that I am trying to access the SMB share on. carlnewton is the name of the user account on that machine that I am trying to use to access the share.
I'm going to start googling this error now but if anyone else has seen it before then input would be appreciated!
Thanks

SMB shares die after waking from sleep mode

When my Macbook is freshly booted, I can access the SMB shares on my linux server just fine. The fun starts when the computer is put to sleep and then awakened. About 50% of the time, the shares on my server are inaccessible after waking from sleep. When I click on the server in the Finder, it just says it's connecting and sits there. Not only are the shares inaccessible, but the server cannot be "ejected" (Item in use). Plus, the system cannot be rebooted nicely. It just hangs with the spinning wheel until I ctrlcommandreset the thing. Other services on the server remain accessible from the Macbook after samba dies (iTunes library, FTP). Occasionally, the shares will come to life if I sleep/wake the computer again, but that is rare.
Tiger worked fine with the same server, it wasn't until the 10.5 upgrade that I began having trouble. I called Apple tech support about the issue, and waited 2 weeks for them to tell me to "install Bonjour on the server." I have formatted and reinstalled Leopard more times than I care to count, but the problem always remains. I've been dealing with this for almost a YEAR now and am totally desperate for a solution. Has anybody ever heard of this before?? The server is running Clarkconnect (Centos derivative).

Hi Gary,
This behavior is not a Safari issue but system related.
Close all applications an run in utilities> disc repair permissions.
After you done reboot an see what happens when your Mac gets to sleep mode again. This time don't open any applications to test it. Just leave it showing your desktop.
Post back with the results ...
Dimaxum

How to disable an smb share?

All our itunes and iphoto libraries are on a windows server that is shared out to our apple devices but I need to change the ip address of the windows server.
The smb share on the macbook (10.6) and the g5 (10.5) is forced at startup to the old ip address and for the life of I me I can't remember how I did it and how to disable it.
Any pointers?
thanks

Login Items, genuis, thankyou - gah had been banging my head on the desk there.
Just an aside, now I'm migrating us over to leopard I can use automator to map my network drives but do I still need the automator 'application' in my login items, I guess, can't try at the moment as copying stuff all over the shop.
regardless thanks again
s

Smb shares read only

Hi all,
Upgraded to Lion from a retail build of Snow-Leopard, upgrade went fine, but noticed i can connect SMB fine to my Win7 shares, but when doing a "mount" command on the MBP side, all mounted shares are read-only !
Permissions for this user are correct (it worked great in Snow-Leopard) with no changes to the Windows side.
Also i am giving credentials when i mount the share.
I realize Apple have written their own SMB stack since they cant distribute Samba anymore, but surely it can mount shares read-write, or is the implementation not ready for prime-time and mounts read-only for now until Apple correct the issue?
Thanks.

You described my situation as well.
I have a Windows XP computer -> Lion SMB share that mounts correctly but has "challenges"
- Files and folders can be created but error messages are displayed on the Windows side. Refresh the window and they are there.
- Files and folders can't be renamed or deleted
A Snow Leopard Mac on the same network -> Lion SMB share works great
Prior to upgrading to Lion the same shares on Snow Leopard worked flawlessly.

Windows 7 Guest Access to SMB Share

Similar Messages

Maybe you are looking for