Smb shares on servers inaccessible after OS X 10.8.2 (12C3104) update today?

I finally switched over from a W7 machine to a beautiful MBP Retina this afternoon. I was surprised at the ease of set up etc. It all worked flawlessly, and I could see and access all my network shares (some other W7 PC's, but most importantly my Synology NAS box with all our music and movies on it). My itunes saw the NAS box as shared, let me log on to it and could immediately play from it. GREAT.
Then I got an update later this evening to OS X 10.8.2 (12C3104). And now this no onger works... Finder and iTunes show the shared resources such as some PCs and the SAN box, but will no longer connect to them :-(. I have browsed many forums including this one, I read many others have issues, but have not been able to find a solution.
I am all new to Mac, and after a fabulous start this afternoon I am now rather down about my choice... Can anyone point me in the right direction?

BTW,
I usually roll my own. Six or eight Phillips screws and your finished. These are the three I currently have. The last is four years old:
Macally GS350SUAB2 Hi-Speed eSATA/1394A/1394B/USB2.0 Storage Enclosure for 3.5inch SATA HDD
w/Seagate 2TB ST32000542AS Barracuda® Green SATA 3Gb/s Hard Drive
Macally GS350SUAB Hi-Speed eSATA/1394A/1394B/USB2.0 Storage Enclosure for 3.5inch SATA HDD
w/Hitachi 1TB HD31000 IDK/7K Deskstar  SATA 7200 RPM 32 MB Cache Internal Hard Drive
Macally GS350SUA Hi-Speed eSATA/1394A/USB2.0 Storage Enclosure for 3.5inch SATA HDD
w/Seagate ST3750640AS Barracuda 750 GB SATA 3.0GB/s Internal Hard Drive
BTW, I never use USB 2.0, since it's slower than molasses, and WiFi is slower still and, but pollutes the airways with EMR/EMI.

Similar Messages

  • Wow!  No servers connecting after 10.5.1 upgrade through software update

    Just installed 10.5.1 update and cannot now connect to any smb/cifs or afp shares - after a delay after I select a server, or click the (connect as...) button, I get the spinning ball. Then the Finder restarts.
    I cannot connect to any shared services.
    I've been on 10.5 since day one and have had no networking problem (except AFP access to a third party AFP server through the GUI, CLI works ok though, don't understand this one yet either).
    I have no problems with SMB or AFP though the CLI that I can tell, including no problem to the third party server:
    William-White:~ admin$ mount_afp -i afp://[email protected]/NS2-iPod ns2
    Password:
    William-White:~ admin$ ls ns2
    HandBrake-0.8.5b1-MacOSUBGUI.dmg MediaForkCLI-batch.sh
    HandBrakeCLI-0.8.5b1-MacOS_UB.dmg Network Trash Folder
    MPEGs Temporary Items
    William-White:~ admin$ smbclient -NL 192.168.1.100
    Domain=[KENNEDY-SMB] OS=[Unix] Server=[Samba 3.0.10]
    Sharename Type Comment
    shared Disk shared
    DVDs Disk DVD Movie links
    MP4s Disk MP4 Movie links
    Music Disk MP3 Music links
    pc-installers Disk windows installers
    IPC$ IPC IPC Service (Kenwhite WINS server)
    ADMIN$ IPC IPC Service (Kenwhite WINS server)
    Domain=[KENNEDY-SMB] OS=[Unix] Server=[Samba 3.0.10]
    Server Comment
    Workgroup Master
    CRAY WHITEW-XP-D620
    KENWHITE KENNEDY-SMB
    WORKGROUP JESSICA-KENNEDY

    You have Leopard installed on a TiBook 500Mhz? Why? If so, then that could very well be the problem. Just because you were able to hack the installer to get it to install on the machine doesn't mean it will run properly. Speed is not the only reason that machine (and others like it) are incompatible with Leopard.
    Either way, whichever machine is the one that is crashing (the TiBook or the Mini), when the Finder restarted that means it crashed. There should be a crash log in Console.app for the Finder describing the crash. It might be able to give you some insight into what actually caused the crash. Good luck...

  • 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

  • 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

  • Mac Pro accessing SMB shares on a windows server. After being left on all night, the MP gets "file unavailable" messages when opening files on the share.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

    Windows Server 2003 accessed by several PCs and Macs without previous incident.  This one Mac Pro after it's been left on all night (running jobs, or just left idle), and a user tries to reconnect to an SMB share, can go to Finder, Go, Connect to Server, enter the Server info as normal, login as normal, view the directories and files as normal, but as soon as they try to open anything they are given one of the following messages:
    "Word cannot open this document. The document might be in use, the document might not be a valid Word document, or the file name might contain invalid characters (for example, \ /). (<filename>)" - when opening a word document
    "<filename> could not be found.  Check the spelling of the file name and verify that the file location is correct.  If you are trying to open the file from your list of most recently used files on the File menu, make sure that the file has not been renamed, moved, or deleted." - when opening an excel spreadsheet
    Note that these messages are popping up AFTER the user has double-clicked on them to open them.  So the files are certainly there and correctly named (and contain only letters, numbers and underscores).  After restarting the Mac Pro, the error messages are gone and the files can be accessed without problem. Would like it so that they can connect to the server without having to restart every day.

  • No connection from XI3.0 to smb share after lost of connection

    Hi Forum,
    we got issues with XI 3.0 after disconnection of
    a smb share.
    The smb share is located on a UNIX machine with the opensource fileserver SAMBA 3.x running on it. After a disconnect of the WAN link to the UNIX maschine XI has to be restarted to reconnect to the smb share.
    Question:
    - Is this problem of XI?
    - Could this be a problem of the SAMBA deamon?
    - anything else?
    This behavior isnt acceptable because we have do this manual . Are there any hints to solve this issue?
    thx
    Andre

    What does it mean? The smb share is a permanent mount?! Do I have to configure this in XI?
    thx
    Andre

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

  • Re-connecting SMB shares after sleep or standby?

    I have searched the forums for an answer but no real solution have been found yet, maybe you can help?
    Iäm currently using my Mac Mini in a Windows 2003 Server network. It's a workgroup and there is only one server. I have two shares on the Win2003 Server that I connect to from the Mac using the regular SMB "Connect to server" procedure. The shares mounts fine and everything is accessible, both read/write on NTFS.
    Now, I have set my Mac to go to sleep after 1 hour of inactivity. When I wake it up, the SMB share mounts are gone so I need to manually reconnect them. I have an Applescript that I doubleclick on that reconnects the shares, again all without errors. I ususally don't shutdown the Mini via Apple-Shutdown but rather just by quickly pressing the powerbutton on the back of the mini for standby, when waking up the shares are gone.
    Is it possible to "hard mount" the shares so they stay accessible after sleep, like they do in WinXP for instance?
    I´ve read about "automount" but it only seems to address auto-login scripts and I have no problem with mounting at login. Someone mentioned that it's possible to create an alias to the shares and place them in the right hand side of the dock and that should make the shares auto-mount when clicked, how is that done exactly?
    The simple solution would be to disable sleep and to always shutting down the Mini, but the instant wake-up is so useful that I really don´t want to wait for it to get ready.
    Any suggestions and tips are welcome, thanks!
    Mac Mini 1,33   Mac OS X (10.4.4)  

    Thanks for the reply.
    Regarding questions 1-3:
    1-2 Yes.
    3. Yes, and same error shows up directly after launching puNetDaemon.
    I didn't have the share's login stored in keychain because I was using a script that provided the login, thanks for pointing that out. I have made sure to connect to the share via Finder and to tick "store in keychain" and the share (E$) now connects automatically via Finder >> Go >> Connect to Server.
    But I still get the same error. I have posted my ch.pusoft.txt below:
    <?xml version="1.0" encoding="UTF-8"?>
    <!DOCTYPE plist PUBLIC "-//Apple Computer//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
    <plist version="1.0">
    <dict>
    <key>192.168.132.144</key>
    <string></string>
    <key>E$</key>
    <string></string>
    <key>WEBBER</key>
    <string></string>
    <key>theDrive2</key>
    <string></string>
    <key>theDrive3</key>
    <string></string>
    <key>theDrive4</key>
    <string></string>
    <key>theDrive5</key>
    <string></string>
    <key>theDrive6</key>
    <string></string>
    <key>theFinderDelay</key>
    <integer>3</integer>
    <key>theIdleReturn</key>
    <integer>30</integer>
    <key>theMACSource</key>
    <string></string>
    <key>theMACTarget</key>
    <string></string>
    <key>theStartupDelay</key>
    <integer>15</integer>
    </dict>
    </plist>
    I'm not familiar with Applescript or xcode so I'm pretty much at your mercy
    Thanks again.
    Mac Mini 1,33   Mac OS X (10.4.4)  

  • SMB share read-only after upgrade to 10.6.4

    since i upgraded my MBP to 10.6.4 i can access our samba shares only in read-only mode.
    i'm connecting with the following string:
    cifs://myUsername@servername/aFolder/anotherFolder/myFolder
    this connection used to work since 10.3 or 10.4 up to 10.6.3, but now i'm getting a read-only volume ("You can only read" in the finder's get info window).
    any hints what i could change to make things writeable again?

    maybe an important additional info:
    the SMB share is mounted under /Volumes using my local MBP user/group setting.
    on the unix box where this share is located, i'm using a different username ("myUsername"), hence the cifs://myUsername@... in the server address string.
    since this connection always worked until 10.6.3 i have no idea if this share used to be mounted for root/admin (or other) - i never checked those permissions/owner settings before.
    THIS IS /Volumes:
    drwxrwxrwt@ 5 root admin 170 14 Jul 12:55 .
    drwxrwxr-t@ 38 root admin 1360 23 Jun 08:38 ..
    lrwxr-xr-x 1 root admin 1 11 Jul 10:53 Macintosh HD -> /
    drwxrwxr-x@ 24 root admin 884 18 Jun 19:39 Users
    *dr-xr-xr-x 4 mbpuser mbpuser 16384 14 Jul 12:52 myFolder*
    loging in on the remote server (using Terminal.app and "myUsername" + password) i have full r/w access on myFolder and all subdirectories. it's only the mounted share on the MBP that is read-only.

  • Can't connect to SMB share after upgrade

    Just upgraded to 10.9 Mavericks and can no longer connect to our SMB file share on the network.  Several of us have tried connecting to it on this machine and all we get is
    There was a problem connecting to the server "xxxxxxx.domain.com".
    You do not have permission to access this server.
    Anyone else having this problem? 

    I have been searching high and low since yesterday afternoon for an answer to this.  My problem is not connecting to an SMB share (well, it was, as the old Cmd+K to connect to the SMB share would close quickly) but instead of the old Mac way of using Cmd+K and the IP address, I simply clicked on the available NAS SMB share under Shared and it is a massively fast connection.  The old SMB connection would take minutes to open the next folder. So, connecting as you would under Windows helped fix that problem, BUT...
    1.  The NAS SMB share times out regularly and you have to eject & reconnect.  Annoying.
    2.  Worse than this is I can not open any documents on the share, only navigate it.  I have to copy paste the documents to my local ssd, manipulate, copy back.  Any new file I copy on, or edit and copy on, the NAS SMB share I can navigate to and open.  But if I try to click a pre-Mavericks existing file, I get "Can not open 'excel/word/acrobat.app' with the -36" error.  Total BS. 
    3.  Even more weird, if I click spacebar on ANY file on the SMB Share it will pop up in preview.  Double click to open and error message.
    4.  If I copy a document attached to an email (Outlook 2011) to the server it is corrupt.  If I copy the file to local ssd, then to the NAS SMB, the same file works perfectly fine. 
    This is completely ridiculous and needs a fix immediately.  I'm going to try using Reinfire's link right now and see if that helps. 
    My NAS is a Netgear ReadyNAS 516 (linux/unix OS) I use in my office.  Computer is MBPr March 2013.    

  • Unable to mount SMB shares under Mac OS 10.6.5

    Help -
    *I can no longer mount any shares from my Seagate BlackArmor NAS-110*. I bought the device (a 1TB network drive with CIFS (aka SMB), NFS, and FTP capabilities (no AFP connectivity)) in June of 2010, and it was working fine until appx (18 Nov, 2010). My computer - MacPro 2x2.26GHz Quad-Core Intel Xeon (early 2009) with 12GB of 1066MHz DDR3 RAM and Mac OS 10.6.5. My home network is running on Apple's TimeCapsule router (version 7.4.2).
    Note: Problems began after installation of recent updates:
    11/10/2010 - Mac OS 10.6.5
    11/12/2010 - iTunes 10.1
    11/13/2010 - iLife '11
    11/13/2010 - iPhoto 9.1
    11/18/2010 - Safari 5.0.3
    I'm not sure which, if any, of these updates may have intrudced new code which impacted my ability to mount SMB/CIFS shares, or whether this problem is isolated to the NAS-110 (actually, reading numerous posts about connectivity issues (during/over the last month or so) shows similar issues with other external drives, servers, NAS devices). The issues may not have materialized until I rebooted the NAS or the Mac. FYI: The only firewall I'm using is the Mac's built in firewall, and I've got File Sharing (AFP, SMB) set to Allow Incoming.
    What happens? I can't mount the SMB shares. I can see the device in my finder. It shows up as "BA-22B9C2", and I can see the sharepoint folders (in Finder): Download, Public, and wiki. When I attempt to SMB mount the shares (by any of the following methods: Double-Click in Finder, use 'Go->Connect to Server' or using the 'BlackArmor Discovery' application) The share/folder icon does not appear on my desktop. It creates a mount-point in the /Volumes directory, but no folder appears on the desktop. I can 'cd' into the sharepoint, and I can see that Spotlight has attempted to index the sharepoint (a .Spotlight-V100 directory was created), but I cannot see the 'Our Music, Our Pictures, or Our Videos' folders inside the Public share/directory. Successive attempts to mount a share, using Finder results in additional mount points in the /Volumes directory (Public-1, Public-2, Public-3, etc), but no folder icons on my desktop.
    FYI: The 'Connected servers' setting (under 'Shared') is enabled in my Finder's Prefences (along with Bonjour and Back to My Mac), so connected shares should appear on the desktop.
    Attempts to mount shares using the Connect to Server method (smb://10.0.1.2/Public, smb://admin:[email protected]/Public) also fail. No folder appears on desktop. The password/login authenticates (connecting to server), and a mount point is created in the /Volumes directory, but no folder appears on the desktop.
    Attempts to mount shares using the BlackArmor Discovery application generate similar results. Shares are visible in the tool. I click on the 'Public' share (which has permissions set to 'read, write, execute' for all), then click the 'Mount Share' button. I am presented with an authentication/login dialog. I log in as a Registered user (name: admin password: admin) Once again, a mount point is created in the /Volumes directory, but no folder appears on the desktop.
    Notably, whenever I attempt to mount a share, Spotlight indexes the share, but then it dies on my computer. Spotlight stops indexing my primary drive (where the OS is installed for my Mac). I have to stop the mds process using Activity Monitor. mds restarts automatically, and it starts indexing my primary drive again. While this may not be critical to my troubleshooting efforts, it has caused some considerable consternation on my part.
    I initially (back around the 18th of Nov, 2010) attempted troubleshooting with the assistance of Seagate technicians, but they quickly gave up on the email support, insisted I had to continue over the phone, which costs ~$14.00 per 'incident' and isn't convenient for my schedule.
    I've already attempted to update the firmware on the NAS (from 1000.0361 to 1000.1081), but that won't work. The NAS indicates a firmware update (1000.1081) is available, but it reports: "Firmware is not found". I had a friend try this update using his Windows machine (and my NAS), with the same results. He tried with a a Vista box and a Windows-NT running through emulation. I also tried to manually update. I downloaded the firmware image file "sg1000-1000.1081.img" from the Seagate downloads page, and attempted a manual update on the NAS. That failed with error "Failed to upload new firmware image to system." Once again, my friend tried to perform a manual update to the NAS. He downloaded a new copy of the file (from the Seagate downloads page), and he got the same error.
    The Seagate techs recommended that I update the firmware. I explained my problems updating the firmware, and I have asked the Seagate techs (via email) for a known good copy of the firmware update, but they do not answer my requests for such.
    The Seagate techs recommended that I restore the NAS with a factory reset. That caused plenty of problems, as their is no mac software to recover the factory reset 'key' from the device (need device MAC, and I presume some sort of hashing key stored on the device). So, I had to cart the drive over to my friends house, and have him attempt the restore. After some initial confusion regarding the MAC address, we were able to successfully restore the device to it's factory settings.
    Note: Before attempting the factory reset, my friend attempted to mount the SMB shares (on the NAS), using his Mac running 10.6.5. He encountered the same problems I encountered. When he tried using his Windows-NT (through VMFusionWare emulation) *he WAS able to mount the shares*. O.k. This must be a Mac OS issue, and not a Seagate NAS issue. - Now that the drive has been restored to factory defaults, it's pretty much empty (some folders, but no data). Default admin/admin username/password are in place.
    I'm not sure which, if any of my most recent software updates may have introduced changes to smb/samba, so I tried mounting the device using other services. It's capable of FTP and NFS as well as CIFS/SMB.
    I tried to create an NFS mount. I tried using two different methods (an application called NFS Manager and the 'Connect to Server' method built into the Mac. Both methods failed to establish a nfs mount to the server. No login errors were noted, but no mount points were created in /Volumes, and no folders appeared on the desktop.
    I tried to connect via FTP, that didn't work either (using an my Transmit client). I'm certainly striking out with this drive. My Mac will not mount the shares/folders. I tried FTP (to 10.0.1.2 as admin) using Transmit application (on port 21). Transmit reported "Could not retrieve file listing for “/Public”. Server said: OOPS: Child died Error -162: Port failed". Connectivity protocols of CIFS, NFS and FTP (on port 21) are enabled on the NAS and the /Public share.
    *When I attempt to connect using the Connect to Server method (See Apple's 'Go' menu in the Finder), I met with sucess!* ftp://10.0.1.2/Public connect attempt resulted in two pop ups. One of them said 'connecting', the other said something about "'NetAuthAgent' (I didn't write it down) wants permission to access your confidential keychain data" Presumably, this was the authentication request. I said 'Always allow'. A folder appeared on my desktop and a finder window opened showing the contents of that folder. Unfortunately, the share is 'read only'; even when I attempt to authenticate as a specific user.
    Note: I don't think FTP attempts to index the mounted shares.
    Prior to the factory reset, I was able to connect to the shares using the Seagate's 'Global Access' web based ftp service. Now I cannot connect through the Global Access page.
    Below are 'Console' entries and a listing of my /Volumes directory. These may help resolve the issue. I deleted some entries (those I felt were unrelated to the issue). I left in stuff that's been bothering me.
    _*Can anyone help me reestablish SMB connectivity with my NAS-110?*_
    - Robert Vaessen
    'Console: All messages'
    12/16/10 00:11:15 BlackArmor Discovery[65267] Got netServiceBrowserWillSearch: event.
    12/16/10 00:11:15 mDNSResponder[23] Bad service type in .blackarmor4dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:15 mDNSResponder[23] Bad service type in .blackarmor4dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:15 BlackArmor Discovery[65267] Got netServiceBrowserWillSearch: event.
    12/16/10 00:11:15 mDNSResponder[23] Bad service type in .blackarmor2dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:15 mDNSResponder[23] Bad service type in .blackarmor2dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:15 BlackArmor Discovery[65267] Got netServiceBrowserWillSearch: event.
    12/16/10 00:11:16 mDNSResponder[23] Bad service type in .blackarmor1dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:16 mDNSResponder[23] Bad service type in .blackarmor1dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:16 BlackArmor Discovery[65267] Got netServiceBrowserWillSearch: event.
    12/16/10 00:11:16 mDNSResponder[23] Bad service type in .blackarmorNASinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:16 mDNSResponder[23] Bad service type in .blackarmorNASinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:16 BlackArmor Discovery[65267] Got netServiceBrowserWillSearch: event.
    12/16/10 00:11:16 BlackArmor Discovery[65267] got netServiceBrowser:didFindService:moreComing: event for <NSNetService 0x517a80> local. blackarmor1dinfo.udp. BA-22B9C2
    12/16/10 00:11:16 BlackArmor Discovery[65267] inserted new net service object for BA-22B9C2:
    "BA-22B9C2" = 1;
    12/16/10 00:11:16 mDNSResponder[23] Bad service type in BA-22B9C2.blackarmor1dinfo.udp.local. Application protocol name must be underscore plus 1-15 characters. See <http://www.dns-sd.org/ServiceTypes.html>
    12/16/10 00:11:16 BlackArmor Discovery[65267] Added 1 drive table objects to the servicesToInsertArray.
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Domain=[BA-22B9C2] OS=[Unix] Server=[Samba 3.0.34]
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Domain=[BA-22B9C2] OS=[Unix] Server=[Samba 3.0.34]
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] tree connect failed: NTSTATUS_ACCESSDENIED
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Domain=[BA-22B9C2] OS=[Unix] Server=[Samba 3.0.34]
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] tree connect failed: NTSTATUS_ACCESSDENIED
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Domain=[BA-22B9C2] OS=[Unix] Server=[Samba 3.0.34]
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] tree connect failed: NTSTATUS_ACCESSDENIED
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Domain=[BA-22B9C2] OS=[Unix] Server=[Samba 3.0.34]
    12/16/10 00:11:17 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] tree connect failed: NTSTATUS_ACCESSDENIED
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] PING 10.0.1.2 (10.0.1.2)
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=0
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=0 ttl=64 time=0.307 ms
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=1
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=1 ttl=64 time=0.216 ms
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=2
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=2 ttl=64 time=0.216 ms
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=3
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=3 ttl=64 time=0.286 ms
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] --- 10.0.1.2 ping statistics ---
    12/16/10 00:11:31 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] 4 packets transmitted, 4 packets received, 0% packet loss
    12/16/10 00:11:34 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Download', from '//%20;[email protected]/Download', dead
    12/16/10 00:11:34 mds[22627] (Error) DiskStore: Unable to create/find index location
    12/16/10 00:23:50 sandboxd[65414] awacsd(48) deny file-read-metadata /Library/Preferences/com.apple.security.plist
    12/16/10 00:23:50 sandboxd[65414] awacsd(48) deny file-read-data /Library/Preferences/com.apple.security.plist
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] PING 10.0.1.2 (10.0.1.2)
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=0
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=0 ttl=64 time=0.356 ms
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=1
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=1 ttl=64 time=0.209 ms
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=2
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=2 ttl=64 time=0.237 ms
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=3
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=3 ttl=64 time=0.209 ms
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] --- 10.0.1.2 ping statistics ---
    12/16/10 00:31:25 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] 4 packets transmitted, 4 packets received, 0% packet loss
    12/16/10 00:31:39 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public', from '//%20;%[email protected]/Public', dead
    12/16/10 00:31:39 mds[22627] (Error) DiskStore: Unable to create/find index location
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] PING 10.0.1.2 (10.0.1.2)
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=0
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=0 ttl=64 time=0.271 ms
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=1
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=1 ttl=64 time=0.257 ms
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=2
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=2 ttl=64 time=0.197 ms
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=3
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=3 ttl=64 time=0.205 ms
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] --- 10.0.1.2 ping statistics ---
    12/16/10 00:47:36 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] 4 packets transmitted, 4 packets received, 0% packet loss
    12/16/10 00:48:41 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public', from '//%20;%[email protected]/Public', dead
    12/16/10 00:48:41 mds[22627] (Error) DiskStore: Unable to create/find index location
    12/16/10 00:51:17 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public', from '//[email protected]/Public', dead
    12/16/10 00:51:18 mds[22627] (Error) DiskStore: Unable to create/find index location
    12/16/10 00:53:51 sandboxd[65922] awacsd(48) deny file-read-metadata /Library/Preferences/com.apple.security.plist
    12/16/10 00:53:51 sandboxd[65922] awacsd(48) deny file-read-data /Library/Preferences/com.apple.security.plist
    12/16/10 00:54:24 cupsd[65930] sandbox cache error: database is locked
    12/16/10 01:00:56 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
    12/16/10 01:01:06 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
    12/16/10 01:02:02 _lp[66035] audit warning: expired /var/audit/20101215210444.20101215231614
    12/16/10 01:02:02 _lp[66034] audit warning: closefile /var/audit/20101216055051.20101216080202
    12/16/10 01:09:56 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public', from '//[email protected]/Public', dead
    12/16/10 01:09:56 mds[22627] (Error) DiskStore: Unable to create/find index location
    12/16/10 01:10:15 com.apple.Finder[208] NFS Portmap: RPC: Program not registered
    12/16/10 01:11:15 com.apple.Finder[208] NFS Portmap: RPC: Program not registered
    12/16/10 01:11:15 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:12:09 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:12:13 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:12:29 com.apple.Finder[208] mount_nfs: can't access /: Permission denied
    12/16/10 01:12:44 com.apple.Finder[208] mount_nfs: can't access /: Permission denied
    12/16/10 01:15:05 /System/Library/CoreServices/CCacheServer.app/Contents/MacOS/CCacheServer[66174 ] No valid tickets, timing out
    12/16/10 01:15:53 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:15:54 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:15:55 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:15:55 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:15:56 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:17:05 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:19:13 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-1', from '//[email protected]/Public', dead
    12/16/10 01:22:38 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-2', from '//[email protected]/Public', dead
    12/16/10 01:23:21 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:25 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:25 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:26 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:27 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:27 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:23:50 sandboxd[66426] awacsd(48) deny file-read-metadata /Library/Preferences/com.apple.security.plist
    12/16/10 01:23:50 sandboxd[66426] awacsd(48) deny file-read-data /Library/Preferences/com.apple.security.plist
    12/16/10 01:24:03 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:47:13 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-3', from '//[email protected]/Public', dead
    12/16/10 01:47:13 mds[22627] (Normal) DiskStore: Creating index for /Volumes/Public-3
    12/16/10 01:50:38 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:51:45 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
    12/16/10 01:51:56 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
    12/16/10 01:52:03 authexec[67020] executing /usr/sbin/automount
    12/16/10 01:52:39 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:52:47 com.apple.launchd.peruser.505[150] (com.apple.AddressBook.abd) The following job tried to hijack the service "com.apple.AddressBook.abd" from this job: [0x0-0x1284283].com.apple.AddressBook.abd
    12/16/10 01:53:10 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 01:53:50 sandboxd[67042] awacsd(48) deny file-read-metadata /Library/Preferences/com.apple.security.plist
    12/16/10 01:53:50 sandboxd[67042] awacsd(48) deny file-read-data /Library/Preferences/com.apple.security.plist
    12/16/10 02:00:50 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 02:00:55 com.apple.Finder[208] mount_nfs: can't access /Public: Permission denied
    12/16/10 02:01:01 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-4', from '//[email protected]/Public', dead
    12/16/10 02:11:28 GrowlHelperApp[328] Transmit registered
    12/16/10 02:12:07 Firewall[101] Transmit is listening from 10.0.1.3:59918 proto=6
    12/16/10 02:12:17 Firewall[101] Transmit is listening from 10.0.1.3:59929 proto=6
    12/16/10 02:12:17 Firewall[101] Transmit is listening from 10.0.1.3:59930 proto=6
    12/16/10 02:12:25 Firewall[101] Transmit is listening from 10.0.1.3:59937 proto=6
    12/16/10 02:12:25 Firewall[101] Transmit is listening from 10.0.1.3:59938 proto=6
    12/16/10 02:12:33 servernotifyd[402] token expired
    12/16/10 02:12:35 Firewall[101] Transmit is listening from 10.0.1.3:59947 proto=6
    12/16/10 02:12:35 Firewall[101] Transmit is listening from 10.0.1.3:59948 proto=6
    12/16/10 02:12:45 Firewall[101] Transmit is listening from 10.0.1.3:59961 proto=6
    12/16/10 02:12:48 servernotifyd[402] Fetching new token
    12/16/10 02:12:48 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-5', from '//[email protected]/Public', dead
    12/16/10 02:12:49 servernotifyd[402] Completed token request
    12/16/10 02:12:49 servernotifyd[402] Subscription request completed
    12/16/10 02:15:20 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-6', from '//[email protected]/Public', dead
    12/16/10 02:15:20 mds[22627] (Normal) DiskStore: Creating index for /Volumes/Public-6
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] PING 10.0.1.2 (10.0.1.2)
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=0
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=0 ttl=64 time=0.347 ms
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=1
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=1 ttl=64 time=0.264 ms
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=2
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=2 ttl=64 time=0.232 ms
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] *Pinging host 10.0.1.2: icmp_seq=3
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] Response from 10.0.1.2: icmp_seq=3 ttl=64 time=0.236 ms
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] --- 10.0.1.2 ping statistics ---
    12/16/10 02:19:28 [0x0-0x1266265].com.seagate.blackarmordiscovery[65267] 4 packets transmitted, 4 packets received, 0% packet loss
    12/16/10 02:20:39 KernelEventAgent[64] tid 00000000 type 'smbfs', mounted on '/Volumes/Public-7', from '//%20;%[email protected]/Public', dead
    12/16/10 03:07:28 Firewall[101] Transmit is listening from 10.0.1.3:60607 proto=6
    12/16/10 03:07:37 Firewall[101] Transmit is listening from 10.0.1.3:60611 proto=6
    12/16/10 03:07:37 Firewall[101] Transmit is listening from 10.0.1.3:60612 proto=6
    12/16/10 03:07:46 Firewall[101] Transmit is listening from 10.0.1.3:60614 proto=6
    12/16/10 03:07:46 Firewall[101] Transmit is listening from 10.0.1.3:60615 proto=6
    12/16/10 03:07:55 Firewall[101] Transmit is listening from 10.0.1.3:60619 proto=6
    12/16/10 03:07:55 Firewall[101] Transmit is listening from 10.0.1.3:60620 proto=6
    12/16/10 03:08:04 Firewall[101] Transmit is listening from 10.0.1.3:60622 proto=6
    12/16/10 03:11:26 Firewall[101] Transmit is listening from 10.0.1.3:60649 proto=6
    12/16/10 03:11:35 Firewall[101] Transmit is listening from 10.0.1.3:60651 proto=6
    12/16/10 03:11:35 Firewall[101] Transmit is listening from 10.0.1.3:60652 proto=6
    12/16/10 03:11:45 Firewall[101] Transmit is listening from 10.0.1.3:60654 proto=6
    12/16/10 03:11:45 Firewall[101] Transmit is listening from 10.0.1.3:60655 proto=6
    12/16/10 03:11:53 Firewall[101] Transmit is listening from 10.0.1.3:60661 proto=6
    12/16/10 03:11:53 Firewall[101] Transmit is listening from 10.0.1.3:60662 proto=6
    12/16/10 03:12:02 Firewall[101] Transmit is listening from 10.0.1.3:60667 proto=6
    12/16/10 03:12:02 sysadmin[69677] audit warning: expired /var/audit/20101215231614.20101216012742
    12/16/10 03:12:02 sysadmin[69675] audit warning: closefile /var/audit/20101216080202.20101216101202
    12/16/10 03:18:40 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 10 seconds
    12/16/10 03:18:48 Firewall[101] ftpfs_agent is listening from 10.0.1.3:60739 proto=6
    12/16/10 03:18:48 Firewall[101] Allow ftpfs_agent connecting from 10.0.1.2:43968 to port 60739 proto=6
    12/16/10 03:18:48 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 2 seconds
    12/16/10 03:18:48 com.apple.launchd.peruser.505[150] (com.apple.pbs) Throttling respawn: Will start in 2 seconds
    12/16/10 03:18:48 Firewall[101] ftpfs_agent is listening from 10.0.1.3:60741 proto=6
    12/16/10 03:18:48 Firewall[101] Allow ftpfs_agent connecting from 10.0.1.2:34565 to port 60741 proto=6
    12/16/10 03:19:05 Firewall[101] ftpfs_agent is listening from 10.0.1.3:60745 proto=6
    12/16/10 03:19:05 Firewall[101] Allow ftpfs_agent connecting from 10.0.1.2:36662 to port 60745 proto=6
    12/16/10 03:21:59 Firewall[101] ftpfs_agent is listening from 10.0.1.3:60785 proto=6
    12/16/10 03:21:59 Firewall[101] Allow ftpfs_agent connecting from 10.0.1.2:49839 to port 60785 proto=6
    12/16/10 03:21:59 Firewall[101] ftpfs_agent is listening from 10.0.1.3:60787 proto=6
    12/16/10 03:21:59 Firewall[101] Allow ftpfs_agent connecting from 10.0.1.2:47180 to port 60787 proto=6
    12/16/10 03:23:51 sandboxd[70960] awacsd(48) deny file-read-metadata /Library/Preferences/com.apple.security.plist
    12/16/10 03:23:51 sandboxd[70960] awacsd(48) deny file-read-data /Library/Preferences/com.apple.security.plist
    'Cosole: samba log.nmbd' (Same entry repeated numerous times)
    [2010/12/16 04:22:10, 1, pid=118] /SourceCache/samba/samba-235.5/samba/source/nmbd/nmbdincomingdgrams.c:process_resetbrowser(735)
    processresetbrowser: received diagnostic browser reset request from BA-22B9C2<00> IP 10.0.1.2 state=0x2
    'Console: samba log.sndb' (note the dates)
    [2010/11/11 18:33:43, 0] /SourceCache/samba/samba-235.4/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/11/11 18:33:43, 0, pid=90063] /SourceCache/samba/samba-235.4/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/11/11 18:33:43, 0, pid=90063] /SourceCache/samba/samba-235.4/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    [2010/11/24 04:11:15, 0] /SourceCache/samba/samba-235.5/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/11/24 04:11:15, 0, pid=1507] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/11/24 04:11:15, 0, pid=1507] /SourceCache/samba/samba-235.5/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    [2010/11/24 10:47:01, 0] /SourceCache/samba/samba-235.5/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/11/24 10:47:02, 0, pid=1339] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/11/24 10:47:02, 0, pid=1339] /SourceCache/samba/samba-235.5/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    [2010/11/29 10:48:44, 0] /SourceCache/samba/samba-235.5/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/11/29 10:48:44, 0, pid=43299] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/11/29 10:48:44, 0, pid=43299] /SourceCache/samba/samba-235.5/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    [2010/12/08 12:29:58, 0] /SourceCache/samba/samba-235.5/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/12/08 12:29:58, 0, pid=7246] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/12/08 12:29:58, 0, pid=7246] /SourceCache/samba/samba-235.5/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    [2010/12/08 12:30:04, 0, pid=7248] /SourceCache/samba/samba-235.5/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1576)
    opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Users record for account 'admin'
    [2010/12/08 12:30:04, 0, pid=7248] /SourceCache/samba/samba-235.5/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1576)
    opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Users record for account 'admin'
    [2010/12/08 12:30:06, 0, pid=7252] /SourceCache/samba/samba-235.5/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1576)
    opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Users record for account 'admin'
    [2010/12/08 12:30:06, 0, pid=7252] /SourceCache/samba/samba-235.5/samba/source/passdb/pdbodsam.c:odssamgetsampwnam(1576)
    opendirectorysamsearchname gave -14136 [eDSRecordNotFound]: no dsRecTypeStandard:Users record for account 'admin'
    [2010/12/09 09:59:02, 0] /SourceCache/samba/samba-235.5/samba/source/smbd/server.c:main(925)
    smbd version 3.0.28a-apple started.
    Copyright Andrew Tridgell and the Samba Team 1992-2008
    [2010/12/09 09:59:03, 0, pid=19816] /SourceCache/samba/samba-235.5/samba/source/lib/opendirectory.c:opendirectoryfill_domain_sidcache(1985)
    opendirectorysamsearchname[/Config/CIFSServer] gave -14136 [eDSRecordNotFound]
    [2010/12/09 09:59:03, 0, pid=19816] /SourceCache/samba/samba-235.5/samba/source/passdb/secrets.c:secretsfetch_domainsid(150)
    secretsfetch_domain_sid:opendirectory_query_domainsid gave -14136 [eDSRecordNotFound]
    'Listing of the /Volumes directory'
    drwxrwxrwt@ 20 root admin 680 Dec 16 03:29 .
    drwxrwxr-x 44 root admin 1564 Nov 27 12:19 ..
    drwxrwxr-x 44 root admin 1564 Nov 27 12:19 Clone
    lrwxr-xr-x 1 root admin 1 Dec 8 04:35 Macintosh HD -> /
    drwx------ 1 rvaessen rvaessen 16384 Jan 1 1980 NO NAME
    dr-xr-xr-x 2 root rvaessen 1 Dec 16 01:15 Public
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 01:19 Public-1
    dr-xr-xr-x 1 rvaessen rvaessen 512 Dec 16 03:30 Public-10
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 01:22 Public-2
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 01:47 Public-3
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 02:01 Public-4
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 02:12 Public-5
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 02:15 Public-6
    drwxr-xr-x+ 3 rvaessen admin 102 Dec 16 02:20 Public-7
    dr-xr-xr-x 1 rvaessen rvaessen 512 Dec 16 03:30 Public-8
    dr-xr-xr-x 1 rvaessen rvaessen 512 Dec 16 03:30 Public-9
    drwxr-xr-x@ 17 rvaessen rvaessen 646 Nov 11 18:12 Robert Vaessen’s iPod
    drwxrwxr-x 15 sysadmin staff 578 Nov 6 2009 Time Machine Prime
    drwxrwxrwx 1 rvaessen rvaessen 4096 Dec 7 17:31 nuvi
    drwx------ 1 rvaessen rvaessen 2048 Aug 16 14:52 rvaessen

    O.k. Thanks for the clarification. I poked around in my TimeCapsule router's settings (TimeCapsule is an Apple Airport Extreme router with attached hard drive for wireless backup/storage). Unfortunately, it doesn't look like I can disable multicasting with the TimeCapsule. I can change the multicasting 'rate'. Settings are Low, Medium, High. It's currently set to Low.
    I did a few web searches, and found an Apple.com article: <http://support.apple.com/kb/HT3789?viewlocale=en_US> which explained how to disable Bonjour Service Advertisements. I believe this is the same thing as 'Multicasting'. The process is a modification of "/System/Library/LaunchDaemons/com.apple.mDNSResponder.plist", and a restart of the Mac is required afterwards.
    I'm a bit concerned that disabling multicasting will interfere with my AppleTVs and iTunes music sharing, but I may try it next time I'm up for a computer workout. This task will require editing of system preference files, could require multiple restarts, might interfere with my AppleTVs, could interfere with my iTunes file sharing, doesn't have a documented relationship to my problem.
    This is way to difficult for something that should just work. Did you say you had read something about a relationship between this bonjour multicasting and smb connectivity? If it was online could you post the link?
    I'm currently able to connect to the drive using NFS, but I have to manually configure that connection each time I reboot (can't get the 'Disk Utility' configured to do it automatically). While it's working with NFS, it's not my preferred connect method (for various reasons).

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

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

  • Confusing SMB Share Behavior

    I have some SMB shares on my OS X server that are configured with ACLs to allow one group of users read access and another group write access. When a user with read access attempts to delete a file from a windows machine, the file appears to delete -- but subsequently "reappears" on refresh. My desired behavior is to display an access-denied error. I have not had this issue when connecting to other samba servers on Linux or NAS hardware. Has anyone run into this issue, or does anyone have any thoughts on why it may be occuring and what I can do to resolve it ?
    Thank you

    thank you very much for your answer.
    But my problem is not the listing of available shares of an serving system.
    My exactly problem is to find out which PCs are offering SMB services. After I know which PCs are offering SMB services, I could find out with you command what exactly shares this PCs are offering.
    Any ideas?!?
    Thank You.

  • Creating a folder on an SMB share using a Mac

    Hi everyone,
    This is more of a question than a problem I'm trying to solve, really. Though the answer might help me better explain the issue to our security team.
    Our environment has multiple Windows file servers, both 2003 and 2008. If one of these SMB shares is accessed from a Mac and the user creates a folder, will the ACLs on the share that are set to cascade actually cascade to this newly created folder? We've had issues in the past where ACLs that are supposedly set to cascade on a shared folder are not present on sub-folders created from Macs.
    Next question: if the share resides on a netapp device, do the same rules apply? The Macs are still connecting to these shared folders using the SMB protocol.
    All Macs are bound to our 2008 AD domain and use network accounts with local homefolders. The issue seems to happen when one or both of the following things happen:
    1. A Mac user copies/creates a folder on a Netapp share and for some reason it doesn’t inherit rights correctly
    2. We move the folder from one share on an actual Windows server to the Netapp and it doesn’t take permissions correctly.
    Please let me know if you need any other information.

    Let's put it this way: I'm asking on a Mac site because the people on non-windows support sites are WAAAAY more interested in talking about problems and solutions involving things other than Windows.
    I'm fairly certain that the windows servers ARE respecting their own inheritance rules, barring any major bugs and the like which someone may know about...
    The isue isn't with Macs moving shares to a netapp, it's with a share being moved to a NetApp that has folders created by a Mac. Talking with our security team further, it seems the problem may be limited to shares resident on a NetApp or moved from a Windows server to a NetApp.
    I was primarily asking to see if anyone knew of any issues with these particular situations or had experienced something similar and had dug into it any deeper with F5 (NetApp vendor).

Maybe you are looking for