Strange problems on SMB shares

I have several OS X 10.6.3-10.6.6 clients connecting to my Windows 2003 R2 server using SMB.
I'm seeing very strange problems such as users that cant move or delete files saying that they dont have permissions even though they have.
When i look at open files on the server it seems that sometimes the list says that the file is open even though the user don't have the file open. And the list in Windows Server shows C:\DIRPATH\FILENAME.TXT:AFP_Resource
Anyone have any ideas on whats going on?

Similar problem here, I created a guest user for a neighbor (windows 7), with just sharing privileges not login, and he can access every folder and disks in my network, even having only privileges to read just some. Contacted Apple some week ago, and no response so far. I think that SMB is broken in the leopard side.

Similar Messages

  • Problem with SMB share

    Hi!
    I have a problem when connecting to a SMB file share on a Windows 2003 R2 server (also acting as a Domain Controller for the Active Directory domain) using OS X 10.5.2.
    I've just reinstalled Leopard to rule out any problems with messy configuration on the client, but the problem persists. The newly installed Leopard client is not a member of the AD domain at the moment.
    When connecting to the server share (with cmd+K in Finder), I have to login using a AD account. The share is after successful login accessible through Finder and I could traverse the folders and read / copy all the files on the share. I could also save smaller files (less than 16 KB) to the server.
    However, if I try to save a larger file (more than 16 KB) the files gets created on the server share, but stays a 0 KB. The access to the server share freezes during 60 seconds and the "Copy" window just tells me it has copied 0 KB of the file so far. No data seems to be written to the file at all.
    After Finder gives up, the "Copy" windows tells me that "The operation cannot be completed because you do not have sufficient privileges for some of the items".
    From time to time Finder has also disconnected the share during problems, and OS X has crashed on me in kernel panic four times when testing. I haven't been able to track down the action triggering these errors yet.
    The shares on the server works just fine when using the same username/password from a Windows XP client machine.
    I don't see this problem when mounting a share from a Windows XP client in Leopard.
    What could be wrong here? Is there some setting on the Windows server that has to be done to work with Leopard? (I've read about the SMB signing, but Leopard shouldn't need the signing to be turned off, should it?)
    At the moment I'm having a hard time using the shiny new MBP at work, so any help on this would be highly appreciated!
    Best regards, Jonas Mixter

    I have an issue with OSX Leopard (10.5.2) , where by I can't write to NTFS shares on W2K3 servers with SMB signing turned on and IPV6 disabled for the interface.
    To recreate the issue:
    Create a folder named test that contains two files one named ._test.txt and test.txt on OSX and copy to an SMB share on W2k3.
    This results in spurious errors about permissions and locked files.
    Copying a file larger than 4k results in the error:
    "The operation cannot be completed because you do not have sufficient privileges or some of the items."
    Using mount_smbfs from a shell on OSX results in the error: "Permission denied"
    host:~ user$ mount_smbfs //user@server/share /Volumes/test-smbmount/
    Password:
    host:~ user$ cp test.docx /Volumes/test-smbmount/
    cp: /Volumes/test-smbmount/test.docx: Permission denied
    Using smbclient from a shell on OSX results in SUCCESS!!!
    host:~ user$ smbclient \\\\server\\\share -U user
    Password:
    Domain=DOMAIN OS=Windows Server 2003 3790 Service Pack 2 Server=http://Windows Server 2003 5.2
    smb: \> put test.docx
    putting file test.docx as \test.docx (784.7 kb/s) (average 784.7 kb/s)
    smb: \>
    There is an alternative solution if you do need to drag and drop in your gui world, it'll cost you $120
    link: http://www.thursby.com/products/dave-eval.html
    I have mailed the developer as he has obviously identified the root problem of the issue and I urged him to share his patch/resolution with Apple in the interests of the user community and a darn nice thing to do.I had a response form the developer to my request. I sent my workaround solution to the developer and stated that in my opinion the pricing for the software seems unnecessarily high based on the functionality it provides and way above what I would be willing to pay to resolve one small issue.
    <developers response>
    Pricing is a difficult topic to discuss -- but if you have no use for the product, any price is too much. As for reporting bugs to Apple, they'll listen to customers much sooner than they'll listen to developers. And they have some of the brightest engineers I know. If you report the bug to them, they'll likely have it fixed in the next update.
    </developers response>
    I couldn't find away to report the bug myself so I had a friend do it for me. The response I had back from Apple was less than satisfactory.
    They believe that the issue is to do with NTFS streams and that a file containing ".com.apple.smb.streams.on" needs to be created and placed into the root of shared volumes. This is not a fix!
    If you want to prevent writing the "Apple Double" files to a remote share, enter the following into a terminal:
    $ defaults write com.apple.desktopservices DSDontWriteNetworkStores true
    Problem still exists.
    ref: http://docs.info.apple.com/article.html?artnum=301711
    <apple double description>
    ref: fhttp://docs.info.apple.com/article.html?artnum=106510
    Before Mac OS X, the Mac OS used 'forked' files, which have two components: a data fork and a resource fork. The Mac OS Standard (HFS) and Mac OS Extended (HFS Plus) disk formats support forked files. When you move these types of files to other disk formats, the resource fork can be lost.
    With Mac OS X, there is a mechanism called "Apple Double" that allows the system to work with disk formats that do not have a forked file feature, such as remote NFS, SMB, WebDAV directories, or local UFS volumes. Apple Double does this by converting the file into two separate files. The first new file keeps the original name and contains the data fork of the original file. The second new file has the name of the original file prefixed by a "._ " and contains the resource fork of the original file. If you see both files, the ._ file can be safely ignored. Sometimes when deleting a file, the ._ component will not be deleted. If this occurs you can safely delete the ._ file.
    </apple double description>
    I am not the only one this issue. A quick peruse on http://macwindows.com/ will show that numerous people are suffering and numerous workarounds have been suggested. Sadly none of which work for me. Each work around is stranger than the previous. Such as disabling IPV6 and updating Daylight Savings Time.
    The issue lies with the samba integration. I am primarily a Gentoo Linux user and this kind of bug would have been resolved almost instantly if present in open source software.

  • WRT350N - V2.00.20: Write access problem to SMB share from Mac OS X 10.6.2

    Hi everyone, i've got a problem trying to write a file on the SMB share of the wireless router WRT350N from a MAC OS X 10.6.2 Finder (but also from a Leopard).
    I've got no problem neither reading from mac or writing from win.
    I've tried to write by cp command from terminal without problem.
    Sorry for my english and thanks everyone,
     Mr Proc 

    Same issue on my WRT610N V2. I am using iMac Intel running 10.6.2. Error -36 prompted when copying files to the USB share disk from the Finder. Working fine when on PC running XP.
    Another issue is DDNS can't report the router IP to DynDNS.com although it status that the update is successful and completed. After updated, the router's IP is still different to the IP shown on the DynDNS.com. I need to type the IP manually to the DynDNS.com
    Hope the new firmware would fix these problems.
    Thanks 
    Message Edited by rickysuper on 11-27-2009 12:00 AM

  • Problem accessing smb share since change to Windows 8

    Hy,
    I have a smb share folder on my router (I connect a pen and is shared in the network), with no password.
    I am able to access from Windows 7 and Linux, but not from Windows 8.
    The reported error is:
    The device or resource (SERVER) is not set up to accept connections on port "The File and printer sharing (SMB)".
    Which is obviously wrong, since I can access it from other OS.
    How can I solve this or get more information on the underlying issue.
    I've read several threads in here about similar problems, but nothing worked in my case (services are running, smb-cifs is active and there's no error about IPRStackSize and I turned off firewall and antivirus).
    Thanks in advance

    is your network public or private? in order to access shares you need to be on a private network in windows 8.
    Change Network Status Using Settings Charm
    1. Press Windows Key + I combination on the keyboard to reveal the
    Settings charm. Now in the bottom, click on the Network icon there. Alternatively, you can click on the
    Network icon in the notification area on the
    taskbar.
    2. Now in the Networks section, right-click over the network whose status you’re looking for to change, select
    Turn sharing on or off.
    3. Finally, you have the options to select between Private and
    Public status for your network. If you select Yes, turn on sharing or connect to devices, the network will be switched to Private status.
    <ins class="adsbygoogle" data-ad-client="ca-pub-5950002284129980" data-ad-slot="6708462760" style="width:336px;height:280px;display:inline-block;"></ins>

  • Mac OS X 10.5.7 Server - Problem with SMB-Share

    Hi@all,
    i've following problem with my Mac OS X Server.
    I want to disable the virtual share points of SMB with Server-Admin.
    After disabling the virtual share point and saving, the virtual share points are autmotically enabled again. I don't know why and how i can solve this problem.
    Does anybody know, what is going wrong?

    Try the Server Products forums.

  • SMB share strangeness with OS X Lion

    Since upgrading to OS X Lion I have some issues with SMB shares. I can connect to my macs share but when I create a new file or folder on the mac from within Windows Vista the file name seems to get corrupted temporarily. If I create a new folder for example the folder will appear with the name 'ew Folder' with some strange character on the end. Then if you try and interact with this folder, try to change it's name or navigate into the folder you can't. If you refresh your view of the share then you can see that the folder was actually named correctly as 'New Folder'.
    I have just updated to 10.7.1 and I still get the problem so I thought I would see if anyone else is seeing it.
    This makes using the share complicated as you have to keep refreshing every time you make a change. Is there anything that I can do to get around this?

    I'm experiencing a similar issue with smb shares on Lion.  Windows clients can connect, but simple DOS commands do not work against the SMB share.
    "Dir" works
    "Dir *.bat" returns nothing, eventho there are batch files in the directory.  Simply put wild card directory listing does not work.
    You must specify the executable or batch file name with extension in order to run it.  "ABC" doesn't work, but "ABC.exe" works.  "EFG" doesn't work, but "EFG.BAT" works.
    Anyone with info please advise...
    Thanks,
    -John

  • Problems copying files to a SMB share.

    Hello,
    Having some odd issues since moving to 10.6. It appears to be a combination of two problems.
    We are in a PC based Active Directory environment. The Mac is bound to the AD and has a Mobile account configured. The problem is with copying files to the network Home folder.
    On attempting to copy a file to the network drive I received a "The operation can't be completed because you don't have permission to access some of the items" error. This only seems to effect some files. I checked the permissions on both the file I was attempting to copy and the destination folder. I had full read/write access to both.
    I attempted to copy the file with the terminal and got an error that I was unable to copy the extended file attributes of the file as I did not have permission.
    Using the xattr command I could see that the file had the com.apple.TextEncoding attribute. I used the xattr -d command to delete the attribute and I was then able to copy the file with the Finder. Another file I tested that I could not copy had the com.apple.FinderInfo attribute. Deleting this attribute also allowed me to copy the file.
    It seems that any file with extended file attributes in 10.6 cannot be copied to our SMB shares. I have tested this on all of our 10.6 Macs with exactly the same result. 10.5 has not had the same problem.
    Now for the second problem. After copying the file as part of the testing I attempted to copy the same file over and replace the existing file and got the error "The Finder can't complete the operation because some data in "" can't be read or written (Error code -36)". I attempted to this a number of times and found that approx 50% of the time it does copy with no error. Checking the Console gives me the following message for the times it does give an error :
    27/10/09 4:03:27 PM /System/Library/CoreServices/Finder.app/Contents/MacOS/Finder[153] Allocator race detected: transaction is not verified for -101/2 - test7.txt
    Any light that can be shone on this issue would be great. This means for us that OS X 10.6 is fundamentally broken and can't be installed on any machines.
    -Justin

    Just posted on the Entourage Help Blog: Workaround for saving Office 2008 files to SMB servers in Snow Leopard
    http://blog.entourage.mvps.org/2009/12/workaroundfor_saving_office_2008_files_to_smb_servers_insn.html
    According to Craig, a poster on the microsoft.public.mac.office newsgroup:
    Changing the owner of the share to NETWORK SERVICE will solve the problem. I have tested this on a test share I set up during troubleshooting and it works! I have told my MS support rep about the workaround and she was going to spread it around. She mentioned that Apple appears to have a fix in the works but not to expect it to be released until February!

  • SMB Share Problem

    I have Windows Server 2003 with a couple SMB shares setup. My problem is that on my schools network I am able to connect no problem to the server when in my Dorm building. However when I go to a different building finder says "The server may not exist...Check the server name or ip address..." I am trying to connect using the Servers IP Address, I have also tried using DNS name and that doesnt work either. The catch is that when I am running Vista through Boot Camp I am able to connect no problem to the SMB Shares using the IP address, so Im curious as to whats different within the two OS's that one can connect and the other cannot.
    All connections are Wired, the server is not behind a router within my room.
    In finders connect to server i am enter smb://<ip address>

    Your issue may be adressed by one of these threads:
    http://www.macwindows.com/tiger.html
    Good luck!

  • Problems saving to an SMB share using 10.8

    Issue happens in CS5 after Mountain Lion Upgrade 10.8
    when using CS5 to save files via a SMB connection to a Windows Server the following error is displayed "could not save filename due to a program error"
    however file save functionality in other programs / finder succeeds as expected with no issue.

    Branched this out to a new discussion.  Which Adobe application are you trying to save to the SMB share from?

  • Restore SMB Shares

    Hi All
    I have a problem with my Mac Mini creating a SMB share for my windows laptops to access files over the network.
    I have created shares in system preferences and selected share over SMB, included the correct user permissions.
    When I browse to \\ipaddress it shows up with 1 share only which is called films. I do not have any shares setup like this at all. If I try to get into this folder it fails.
    Is there a file or something which holds this information which I can restore? I really don't want to keep using FTP or have to reinstall the OS.
    Thanks
    Sam!

    Hi guys,
    I too am having a very similar issue - I have a Freecom Network Drive (that is the model name..) and I can't connect to it either from Snow Leopard. It worked fine in Leopard, but I guess Apple have broken something in Snow Leopard.
    However, I have some differences in my experience here.
    1) The Freecom drive that I have doesn't seem to support usernames and passwords so it is always free to connect to from any machine on the LAN. I've never specified a username and password to connect to it and its always worked - the wife's PC can still connect to it and so can my Linux Box running Xbox Media center.
    2) I can navigate around the disk in Finder and in Terminal, but when I do try to open a file, I get two error boxes, one on top of the other, the first being:
    'The application iTunes.app can't be opened. -36' for MP3 files
    'The application VLC.app can't be opened. -36' for AVI
    and so on depending on the type of file.
    The second message is:
    'The operation can't be completed - an unexpected error occurred (error code -36)'
    3) Another strange thing is I can copy the file directly to the Mac HD from the NAS ok, but I can't write anything there.
    I've also upgraded to 10.6.1 but no luck - I haven't tried hacking around in the smb.conf either.
    Hopefully Apple monitors this!!
    C

  • Search an smb share while logged into AD with OD managed prefs

    _*Hi,*_
    We have a set up here where i have enabled the indexing on smb share via mdutil, but when i search the share the only things i can see are things i have created, but if i log in as a standard local user, mount the smb share and enable indexing i can search the share perfectly well.
    The permissions to the various folders on the smb share (sbs 2003) all appear to be the same.
    Any ideas much appreciated

    I ended up (for other reasons) reinstalling Solaris 11 among other things, and at some point this strange problem went away. I don't know exactly why or what was causing it in the first place, unfortunately. At least it's gone.
    Cheers,
    Kevin

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

  • Finder gets stuck when reading contents of large folders on a SMB-share

    Hai thar, everyone. Recently I've found a sad bug in the world's most advanced OS. I wonder why it was left almost unnoticed as I was unable to find out some info on it so I created this topic in hope to turn attention to this issue when no solution is available right now by far. In short, bug consists in Finder's misbehaviour when it reads contents of big folders on a mounted SMB-shares like stated in the title. Number of files - somewhat around 11-12 thousands/folder. What't interesting, when one goes to the shared folder which contains not much files (below critical limit) - everything's just fine. When one opens a "bomb"-folder, Finder does nothing. It won't display folder's contents and moreover, it won't display contents of other folders on the share anymore, however, it's still able to show up contents of those folders you have visited just before opening "bomb"-folder. Probably it simply has  the contents of visited folders cached somewhere. The second consequence, connection to the SMB-share seems to degrade. Speed drops to miserable numbers and case you open some big file from the share theres a chance that it'll be loaded slowly. It's not that hot idea in fact, to load network by watching videos directly from the SMB-server =) but if you do open a movie, playback will be jerky as **** while it was perfect just before you poked the "bomb" and current traffic is very little - a few kbps/~100bps (according to Activity Monitor). As stated before, stuck Finder seemingly affects overall connection to the SMB-server in some strange manner. FS notifications get broken too, on the share.
    In general Finder proceeds functioning. It has no problems with local FS/other kinds of remote FS, but SMB. It looks like theres a stuck thread serving requests to for the file objects on the SMB-share which actually gets stuck or does extremelly slowly.
    The workaround is pretty simple and straight forward - you have to restructurize your "bomb"-folders by splitting them into several subfolders or such. Simply get rid of that huge heap of files stored in a single folder, fragment them and keep their number below 10k/folder. However, this is not a fix. It's only workaround. Fix should follow, as this issue is not only a "little inconvenience" but also a software flaw.
    This bug affects at least OS X 10.7.5 (11G63). Something similar was seen also on OS X 10.6.6
    WBR
    PS: sorry for my broken English.

    Reporting the same problem.
    1. Have Windows 7 MediaCenter with file sharing set up properly (LM+NTLM Authentication allowed and 128-bit encryption disabled in security policies).
    2. Test folder ("C:\income") and all the subfolders' owner is 'Guest', full access is granted for everyone.
    3. Connecting to MediaCenter from MacBook with Finder by pressing Cmd+K and typing smb://ip-addr/income
    4. Finder connects successfully, but some sub-folders and files are not being listed.
    Workaround:
    5. You can open a not-listed folder directly by pressing Cmd+K and typing smb://ip-addr/income/some-invisible-folder
    6. Voila! You're inside invisible folder.
    In the meantime, i can see all the sub-folders on a Windows XP client machine, so i can make a conclusion that all of these 'invisible' sub-folders are actually accessible by Finder, but in some reason are just not being listed on Mac.

  • Errors while copying form WIN XP SMB share

    Hello,
    I do have a really strange problem. I do have a XP box with a SMB share and I could use them from my iMac - means I see the mount, could create a file there and so on. I have some dir's at the XP share and there are files with long names (more than 8+3, two dots etc.). At both machines I used the same user and password, security seems not to be the problem.
    I can't copy the files from my iMac using the Finder nor using mucommander. I always get something like "file not found". Although I see the files and have permissions to copy them. Of course I could copy the files from XP-XP and it's working for some files with 8.3 filenames from OSX-XP. So I thought the problem are the unusal filenames.
    But the unusal filenames work if I copy form XP to OSX. So I think the problem is an OS X side because if I enable a SMB share at the iMAC and if I copy the same directories form XP to OSX, all is working fine. I also tried to increase the IPRSTACKSIZE - but this had no effect.
    Has anybody an idea? I thought I could the XP box standing around just sharing some directories without working on it Now I have to logon and initate the copy process from XP to OSX if I need some files at my iMac.
    best regards and thanks in advance!

    I updated the systems yesterday and that did absolutely no good.
    The only way that I can get a file copied over to the Win2k3 network share is to give that user 'Delete' privileges, and this is what I am trying to avoid. We don't want our users having the ability to delete files off of our server, only read and write.
    "Delete Files and Folders" and "Delete" are the two security privileges that I must enable before a connected user on a Mac can copy files to the network share.

  • Browsing SMB shares

    Hi there,
    I am seeing a strange problem with my new MacBook Pro. I have a windows machine on which I have a number of shares. With my older Macs I am able to enter smb://<machinename>/ in to the Connect to Server dialogue, and it shows me a list of the shares currently available on that machine, and then prompts me to log in to them.
    On my MacBook if I try the same thing (smb://<machinename>/) without specifiying a specific share, the whole machine just hangs and sits there with a spinning beach ball. However, if I specify the name of one of the shares on the machine (eg. smb://<machinename>/<share>) then it connects perfectly.
    Anyone else seeing this, or got any suggestions?
    Thanks

    got another samba update today but still same issue. Half the time it won't even open browse network itself (says something about it being mounted in another location)
    Last edited by bwat47 (2011-08-18 04:01:05)

Maybe you are looking for