Windows machines unable to access smb shares

I know many people are having problems with smb on osx server, but my issues seems very basic, so I will try to ask for help here.
Basically, I have set up a single folder for sharing on a Mac Mini running OSX Mountain Lion Server. Directory services are provided by a WIndows 2003 server, and I have joined OSX Server to that, and am able to see all AD users and groups correctly. I have checked the boxes specifying I wish to share as afp, smb and webdav and also made shares accessible to guests.
Now, if I use a mac client, I can correctly browse the afp and smb shares, and the latter work via finder and smbutil as expected, including access via AD users, connection and file transfer.
If, instead, I use a windows client (I tried both Win7Pro and WinXP), while being able to ping the osx server machine, if I try to "explore" (entering \\hostname in explorer) the shares I get a "Network error: impossible to access ..." (approximate translation, sorry ). I tried both using the hostname and the ip address, always getting the same result.
If I try via prompt with "net view \\hostname" I get a System Error 53 (Unable to find network path).
Does anyone know if I am doing anything wrong?
Thanks
Christian

I have done some further testing, and I can report that occasionally, I am able to connect from a windows 7 professional machine by issuing the following command:
net use z:\\hostname\share /user:DOMAIN\username
mostly this command returns a 53 system error, but sometimes I am asked for the user's password and am then able to access the shared folder for a brief time.

Similar Messages

Windows computers can not access smb-shares in Lion

I have updated von SL to Lion Server. Now, I don't gave Access to my Windows shares from any Windows Computers. If I connect a Windows share u.e. froom Windows 7 Workstation I will see a window with username and password for the share. But the username und password from lion for this share will not work. It was no problem in SL. Any idea?

To get this to work on windows 7 I...:
Start > Computer
Disconnected my mapped netowrk drive that would not connect
Selected the Map network drive button in the toolbar at the top
Typed in the folder location manually (if you try the browse it will fail)
Selected Connect using different credentials
Selected Finish
On the credentials screen that pops up:
User name: <SERVER\username>I found that my server name had to be in capitals (/private/var/log/krb5kdc/kdc.log helps you know exactly what it is)
Password: <your password>
Select Remember my credentials
Select OK
After this i found no issues access any of the shares on the server and everything came back to life

Domain machine Can't access administrative shares c$ admin$ on windows 7 x64 network path was not found

Hello,
I'm unable to access admin shares on a windows 7 pro x64 domain machine, i've tried the following:
. Disable IPV6
. LocalAccountTokenPolicy (32 and 64 bits set to 1 or zero with restart)
. Disable UAC
. Disable firewall
. LmCompatibilityLevel set to 1
I can ping the machine, remote desktop and everything BUT access any shares on it, i've created additional shares for testing and still can't access it, by name or ip, even using the 127.0.0.1. Please help as this issue is driving me nuts.
PS: Windows 7 Enterprise doesn't have this problem

Believe it or not, it's UAC causing the blockage of accessing any hidden $ drive share in Windows 7. At least, for me.
For a new PC built here I tried everything I could find. Disable antivirus, firewall, defender... changing network share settings.. nothing worked.
Thing is, its been working on multiple old PCs so I tracked down network profile and other differences between new and old, only one I found was that I'd disabled UAC on the old PCs (all win7 pro). Disabled UAC on the new PC, rebooted as required to completely
turn it off, bam! can now access root drive shares via the hidden $ as always.
More advanced admins could probably track down the specific registry settings changed by UAC and isolate the one blocking LAN connecting to hidden drive $ shares. I'm not delving any deeper.
Oh, btw, turned firewall, antivirus etc back on and it still allows access over a LAN.
(UAC - User Account Control for those not familiar with the acronym)

Windows 7 unable to access ReadyNAS

Hi,
I'm having a lot of trouble getting access to my NAS from my Windows desktop computer. I use the NAS to backup my DVD-collection to use it with my media center, and it used to work perfectly without any problems. I have no idea when the problem started,
as I have not used or accessed the NAS since around christmas, but between then and now my Windows 7 computer will no longer access the NAS-shares. I'm unable to map the share through Explorer, and it won't show up on my network. I've been googling this problem
for days now, and I've tried a lot of different "solutions" without any luck, but I figured I should ask here.
I'm running Windows 7 Ultimate 64bit - I'm unable to see the SMB-share under Network, although it does show up as a media device if I enable DLNA, but clicking it will just attempt to open the NAS' admin GUI in my browser. XBMC is also unable to map SMB-shares,
which is where my problem turns really annoying. It does respond when I ping the IP. I've also made sure that Network Sharing is enabled in my homegroup settings.
The NAS is a Netgear ReadyNAS Duo V2 - I've made sure it's on the same Workgroup as my computer. The sharing option is SMB, but it has enabled ReadyDLNA, UPNP, HTTP, HTTPS and genie (I don't know what the last one is...).
Again, I used to be able to see it in Windows Explorer and it mapped beautifully before. I have two laptops running Ubuntu (12.10 and 13.04), and my desktop also dualboots Ubuntu 14.04. While running Linux, I can access the Samba-shares again and navigate
the NAS without any problems. Everything is accessible, and I can both read and write to both disks in the NAS. The problem is only there while I'm running Windows, and as this is the OS I prefer, it's starting to bother me a lot. I have no idea what changes
I've done lately, but something has obviously changed on my Windows 7-partition which has removed the option of mapping samba-shares in Windows.
I hope someone here can give me a tip that finally helps me with this issue before my hair turns grey.

in your ReadyNAS there should be some user or folder rights settings.
Double check the user or folder rights settings.
or check out this link: ReadyNAS Share Access
Every second counts..make use of it. Disclaimer: This posting is provided AS IS with no warranties or guarantees and confers no rights.
IT Stuff Quick Bytes

Windows Machines No Longer connecting to Shares

Has anyone experienced issues with their Windows machines no longer connecting to Shares on the server. I have a Windows 7 machine and a Windows XP machine that were connecting to the Shares without any issue. Then this morning they just stopped connecting. I can ping the server both through its name and through its IP address from those computers but when trying to map a network drive all I am told they cannot find the server to connect. I have set all the appropriate security settings on both machines as suggested in numerous articles. SMB is turned on for the server.
I have made no changes to the server in the last 24 hours other than to turn off file-sharing and turn it back on to address an issue with Time Machine backups not occuring due to image being locked in use.

i have a vaguely similar issue, where my server is a member of the domain(workgroup on mac) - suddenly no users from the domain show in users panel,
and connections are not accepted... 10.8.3/server 2.2.1

Window 8.1 system unable to access network shares via VPN connection

Is there something inherent to Windows 8.1 that prevents it from accessing shares on a domain?
I know that it cannot join a domain, but does that also mean that it cannot access shares which are on a domain?
My problem is that I have several user that are running windows 8.1 that are connecting to our network via a VPN.
The users have domain accounts but their computers as windows 8.1 cannot joined to the domain.
So to access network shares they have to use their domain credentials to create a VPN connection.
Once connected the user can RDP to systems on the domain using their domain accounts, so I know that their user names/passwords and permissions are correct. They can access these systems using the computer name, so I don't feel that I have a DNS issue.
They can see the shares on our file server, but when they try to access their departments shared file, they receive an access denied message. There are a few shares that are completely wide open, shared to all users and all departments but they cannot access
those shares either.
You can ping the file server, from the the client when they are connected to the VPN but you just cannot access any of the shares.
So...
I am thinking that it has something to do with windows 8.1 and not being able to join a domain, but I cannot find anything to explicitly support this thought.
Other users running a variety different OS (windows 7, OSX, Linux) can all access the shares without any problems via the VPN, so I am a little stumped.

I have done some more testing and oddly enough I can map a drive if I use the IPaddress, but not the computer name, when checking the check box "connect using different credentials"and providing they users domain credentials.
This seems to point to a DNS issue, one would think, but I can hit the file share server by name \\fileserver.dev.lan
I can see all the shares, so dns seems to be fine right?
So I don't understand why I can map a drive using do the IPaddress and not the machine name, but yet I can see and ping the server by name?
When I try to create a mapped drive by machine name I receive the following message:
Windows cannot access \\fileserver.dev.lan\all
You do not have permissions to access \\fileserver.dev.lan. contact your network administrator to request access.
But if I use the \\x.x.x.x\all using the very same user and password I get connected with no problem.
This only seems to happen on windows 8.1, which leads me to think that has something to do with OS.
I am thinking about upgrading to windows 8.1 pro, but I don't want to go though the hassle and expanse is the OS is not the problem.

Windows 7 machine can't see smb share or any macs

We have 7 render boxes set up on our network, all link to our smb share on our mac server accept one! We run SMBUp on the mac server due to well documented issues with smb and it works fine with 6 of the 7 machines...
I have gone through all settings and checked they match the settings on the other machines. As far as I can tell it matches.
What's strange is the pc used to connect fine, but when we moved offices it just decided to stop seeing any macs on the network!!! It can see the other pc's on the network just not any mac or smb shares.
Somebody please help before I smash this pc into a thousand pieces!!!!
10.9.1 is installed on the mac server.
Cheers
Martin

My guess is that Win7 "recognized" the device as a Realtek and substituted the Realtek drivers for it. Did your Zonet come with an installation CD ... or provides a web support site? If either, I would strongly suggest, that you use their drivers instead ... and this is a good reason you're only getting access with the 802.11g mode.

Trying to access SMB share, can read but not write, I use the domain account to autenticate and domain account has access to the share. its a samba domain and im a Windows Admin by trade.

I have two I Mac's Intel i7 models.
I have some problems getting them to write files to SMB shares.
The domain user account I use when requested to enter when i first try to connect to the share seems to go though without a problem and it presents me with a list of mounts (shares) I select one and the folder opens, I can read files and copy them but I cant write to any of the folders.
I have also mounted the network locatiosn to a folder from the terminal while also specifying a user name and password to use but this also doesnt allow the specified user account to write data to the share.
I have confirmed the user account can write to the share by having the user do so from a windows box.
any help from any of you mac guys would be great!!!!
Im a windows fan boy / Windows Server based Network Administrator and am slowly becomming a fan of your macs (mainly due to the Unix terminal access letting me realise there is more control to be had than most haters would lead you to believe).
Peace Out

I should add that I originally formatted the problematic drive for FAT32 from the Mac, but then the WinXP computer couldn't see the drive when I plugged it in directly via USB. That's why I went with Seagate's utility to format it.

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.

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>

Cannot access SMB shares from Windows boxes in AD domain

Hey folks
I've needed to tackel this for sometime, but Santa is bringing me a dual core G5 and the urgency just increased.
I have an Active Directory domain and all of my macs are successfully joined and get Kerberos tickets upon login. I can access any shares I need from OS X -> windows but NOT the other way around.
I did finally noticed that only local user accounts seem to appear in the accounts list in the sharing pref pane. So I have figured out that I can access any users folder with that one account- OUCH! What I need is access control based on the user.
For instance if I want to share ~jdoe and jdoe is a mobile account and an AD user then if I am logged into windows as [email protected] then I should be able to access the share on the mac. Conversly I should not be able to access ~jdoe with the mac's local admin account and pass.
Do I need to change my smb.conf to reflect AD and if so, where/what?
Also, do I need to map UIDs to anything? And, is that a security risk?
Thanks!
-N

Hi SpaceBass, have you looked into sharepoints or into Netinfo manager. I have been playing around with sharepoints and it does let me enter non local users into the sharing prefs- albeit manually. Only thing is , depending on the number of macs you have, it could be a long and tedious job entering it all by hand. Netinfo may have an easier way, I'll do some more digging and post back.
Cheers.

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

Windows clients unable to access File Sharing since upgrading to Mavericks Server

This summer, I have been tasked to upgrade all the Macs on campus to Mavericks. Including upgrading to Server 3.1.2. Previously, we had an Xserve that ran 10.6.8 Server and two Mac mini servers that ran 10.8 Servers. We have a new Mac mini to replace the Xserve and, initially, everything was pretty smooth. I built the server from scratch, with the intention of using the 10.6.8 server as reference, only adapting to Profile Manager, instead of using Workgroup Manager.
The only problem I had when I started was that I couldn't get Active Directory to create home folders on my Mac Server "NetUsers" volume when adding a Home Folder path. After playing around with it, I completely hosed the Server and decided to start over. Now, after a clean install, I can't get any Windows users to connect to the share on the Mac Server. It declares: "\\MacServer is not accessible. You might not have permission to use this network resource. Contact the administrator of this server to find out if you have access permissions. Account restrictions are preventing this user from signing in. For example: blank passwords aren't allowed, sign-in times are limited, or a policy restriction has been enforced." What's more (that I may not have noticed two weeks ago or it just started, I don't know), the 10.8 server that I upgraded to 10.9 also is not accessible and gives the same error. However, I can access all these file shares from Macs using either smb or afp.
I'm suspicious that this issue is related to SMB1 vs. SMB2 that was implemented differently in Mavericks.
Please, any help on this would be a life-saver. School starts too soon and I need this running on day one!!!

Had the same issue and spent 4 solid days tracking it down (looking in all the wrong places.)
For us, it turned out to be a problem in DHCP services configuration.
For the subnet under the WINS tab, the NetBIOS Scope had a '1' inserted into the field. Apple's tag when hovering the mouse over the field indicated a domain be insterted.
This prevented the Windows XP machines from successfully registering with SAMBA. Once the field was blanked out and saved, the (one machine) needing to be joined found the PDC and successfully bound to the directory.
Blank out the NetBIOS Scope field in DHCP (assuming a simple LAN environment) and you may be in good shape.

Unable to access DFS shares when server 1 goes down

Hello all,
I have a test domain I am building in order to prepare for a new domain we are going to create. We currently have an SBS 2003 that is reaching the end of its' life. We are going to start fresh. I have setup domain-based DFS along with DFS folder replication
for each of the folders. So far, all is working ok, up to this point.
Replication is occurring as it should and my Hyper-V test machines can connect to the mapped drives via the DFS namespace.
\\domain\namespace\target folder
However, once I shut down the primary server (SRV01) I am no longer able to access the shares. The namespace servers tab on the center window of the namespace MMC, has both SRV01 and 02 listed. I receive no errors except "Unable to connect to \\domain\namespace\target
folder because it is unavailable". It is not "failing over" to the secondary available server.
Once I power SRV01 back up, connectivity is then restored to the folders and mapped drives. Is there something I should check for, or am missing?
Any and all insight is appreciated.
Dario Garcia

Hi,
1. Run DFSUTIL /pktinfo to see if the referral target is still the primary server when it is actually down.
If so, run DFSUTIL /pktflush to flush the cached information and try to access the namespace again.
2. If 1 cannot help, whether DNS is also configged on primary server? If so, as it is down,
\\domain may not be recognized.
TechNet Subscriber Support in forum |If you have any feedback on our support, please contact [email protected]

All of the sudden our Mac OS X 10.7.4 operating systems are very slow to access SMB shares on our MS2008 file server

Monday all of our OS X Lion Macs can access SMB file shares on our file server and we come in Tuesday morning and now they take at least 1 minute to pull up the file share and sometimes longer. Windows PC's are immediate when connecting to the same shares. I've seen where others with different versions of OS Xhave this issue but what gets me is it happend all at once to machines that were working perfectly the day before.
I've also looked into changes on our servers and as far as I can tell there have been none.
Does anyone have any ideas? Thanks....

This solution worked for me!
I had a MobileMe account with iDisk configured on my MBP even though I never actually used it. The night they officially shutdown MobileMe the next morning I could no longer connect to my work's SMB file shares (Windows server shares). I found a work around based on some other support threads. If in the "Connect to Server" address field in Finder I specified my crendentials (i.e. smb://username:password@server/) then it worked perfectly fine. This told me it was a crendential issue. Simply deleting the saved server crendentials in KeyChain Access did not resolve the issue. No matter what I would did it would not prompt for login crendentials. Since my Mac login is different than my work domain login I was dead in the water without manually specifiying (not a permenant solution).
After finding this thread I did the following steps and it resolved the issue 100%.
1. Open Terminal
2. cd ~/Library/Preferences
3. ls .GlobalPreferences.plist to verify file exists in that directory
4. rm .GlobalPreferences.plist to delete file
5. ls .GlobalPreferences.plist to verify file no longer exists
4. Go to Force quit to relaunch Finder
5. Lauch "Connect to Server" within Finder and all was good, server connects perfectly
Thank you very much DavidRSewell!!!!

Windows machines unable to access smb shares

Similar Messages

Maybe you are looking for