Finder Size Mismatch with SMB Share

I have 2 SMB Servers (NSLU2 and DNS-323). In Finder all file sizes get rounded up to the nearest 1MB - for example a 2968 Byte file is listed as 1MB, a 1.1MB file is size is listed as 2MB etc. I have checked via Terminal, and all the files are listed as their correct size. This true of both my iMac and MacBook, however only on the DNS-323. None of the PCs in the house exhibit this behavior, only the Macs.
Anyone have any thoughts?

How are you getting the size of the files on the Mac? Via Column Preview (in Column View) or via the Info Window (File->Get Info)? There are two types of file sizes. Logical and physical. Logical is how much space in blocks (1 block = 4k IMS) the file takes up on the hard drive. Physical is the actual number of bytes the file takes up on disk. Column Preview shows only logical size, while Info Window shows both.

Similar Messages

Mac in Windows server environment with SMB shares

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

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

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.

Finder Crash when accessing SMB share

iMac 2.16 GHz Intel Core Duo.
When opening a particular share on an SMB server, the Finder crashes and relaunches. Does not happen on other shares on the same server. Happens for all users on this Mac. Does not happen on other Macs.
Have tried deleting finder.plist and windowserver.plist, and cleaning caches with Onyx and Cocktail.
Note: also crashes on some DMGs.
Mac OS X (10.4.8)

I have also tried Techtool and Repair Permissions.

Finder fails to mount SMB share, while Terminal does

I'm trying to mount shared NTFS partition from my desktop running W2000 at work to my MB at home, and can't make Finder to see it (Error -36 and mount_smbfs: negotiate phase failed: syserr = Operation timed out in the console). Teminal can mount it 100 times ina row, my wife's XP notebook next to me can mount it, but Finder can't. And I feel like I tried everything...
What else could I try - workgroup renaming, all possible spelling combinations, passwd security disable...darn, I'm running VNC to that mashine just to be able to tweak the server if needed...again for no avail...it's a bug with Finder and I can't find way around it...
What would you suggest?
MB 2.0 Mac OS X (10.4.9)

Let me be more specific
W2000 SP4 server, MacBook client, trying to mount shared volume thru SMB
-on the same subnet (i.e. lappy next to the server on the same switch) both mount_smbfs and smbclient work OK
-from home smbclient is working, mount_smbfs does not (Err -36)
-from home my wife can mount the shared volume thru Network Neighbours on her XP notebook
-it does not seem to be TCP/IP related - all comp can make FTP or VNC to the server verywhere
-err log of mount_smbfs is "negotiate phase failed: syserr Operation timed out in the console", no idea is there a way to verbose mount_smbfs
-smb.conf looks basic...secure passwords=enable, no nsmb.conf
-W2000 SP4 sever is all default secure policies, running FTP server w/o any issues.
So is there a key on server...or the client which I have to tweak?
Thank you.
MB 2.0 Mac OS X (10.4.9)
MB 2.0 Mac OS X (10.4.9)

Mac OS X 10.5.7 Server - Problem with SMB-Share

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

Try the Server Products forums.

SMB share strangeness with OS X Lion

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

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

Active Directory, Windows 2003 SP2 Server and SMB shares

I have 10 new iMacs that will be returned and exchanged for 10 HP wintels if I can't resolve an issue with SMB shares in Mac OS X 10.4.9.
We had an old win 2000 server, and all the macs could mount their smb shares without problems.
Recently we upgraded to two new 2003 sp2 servers, one of them the domain controller, and we can't mount their SMB shares. I followed this http://weblog.bignerdranch.com/?p=6&page=3 and/or this http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x to allow AD authentication, but still, I can't mount the 2003 shares (but can with the 2000 ones!!!).
If I enable SFM (services for macintosh) then I can mount the shares, but:
1) the network is slower (I supouse is due to appletalk implementation)
2) and worse, names with more than 32 characters or with some special characters are not allowed. This renders 30% of our archives unavailable with the AFP solution.
I also used all the authentication methods (Plain text apple, plain text windows, etc.) but no one works.
I have now 10 days to find a solution, or all "my" macs will dissapear forever.
Please, some advice or point to documentation.
G4, G5, iMac Intel, Mac Book Pro, etc Mac OS X (10.4.9)

Do you just want to mount arbitrary share from the win servers or do you want the macs to be bound to AD?
The first requires the steps from your second link (allinthehead.com) but the latter (bind to AD) requires things like proper use of DNS, time synchronisation for kerberos to work and proper configuration as described in your first link (bignerdranch.com).
Here are some more links for the latter (AD intergration):
http://www.bombich.com/mactips/activedir.html
http://www.afp548.com/article.php?story=20051202151540574&query=ad-od
HTH
-Ralph

Windows rename on SMB share ignores ACLs

We're getting ready to put ACLs on our file server into production use, and I was checking to make sure that the file sharing experience for Windows users via SMB mounts would match what OS X users see via AFP mounts to the same shared folders and files.
I've discovered that when Windows users rename files and folders via SMB mounts, the permissions are controlled by the POSIX privileges of the enclosing folder, and ACLs privileges appear to be completely ignored. I have a simple test case where I prepare a shared test folder that grants a particular user full access via an ACL, but no access via POSIX (this is deliberate). Via AFP on an OS X system, the user can do whatever they want on the share, as you'd expect. They have no problems renaming or deleting items; their ACL privileges are properly observed. However, when the same user logs onto a Windows system and access the share via SMB, if they create a folder or file, they won't be able to rename it. The only way to get around that appears to be to grant them POSIX read/write privileges on the enclosing folder (not on the item itself). For this one operation, it would appear that POSIX privileges are observed, but ACLs are being ignored. [This has been submitted to Apple as a Bug Report (Problem ID 6143881).]
We're running OS X Server 10.5.2, but plan to upgrade to OS X Server 10.5.4 once our ACLs are running in a production setting. I wonder if other folks see the same problem with renaming files or folders in Windows with SMB shares in OS X Server 10.5.4.
On my server, on an AFP+SMB share, I create a test folder with the following privileges:
ls -led path/to/testfolder # Show POSIX settings & ACLs for test folder
drwx------+ 2 root wheel 68 Aug 12 11:25 testfolder
0: user:myuser allow list,addfile,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit
These privileges can be set via the following commands. Within an AFP+SMB share, create a test folder as follows:
sudo mkdir -p /path/to/testfolder
cd /path/to/testfolder
sudo chmod -R -N . # Remove any inherited ACLs from testfolder
sudo chmod u=rw+X,go= . # Set POSIX privileges to octal 700
sudo chown root:wheel . # Set POSIX owner & group
sudo chmod +a "user:myuser allow list,addfile,search,delete,add_subdirectory,delete_child,readattr,writeattr,readextattr, writeextattr,readsecurity,writesecurity,chown,file_inherit,directoryinherit"
From Windows, navigate to the testfolder on the SMB share. You can do this as a Network Place, Mapped Network Drive, or by explicitly navigating to
\\myserver\myshare\path\to\testfolder
Create a new folder in Windows Explorer. It will come up by default named "New Folder". Try to rename it and you'll get a Windows error: "Error Renaming File or Folder. Cannot rename New Folder: Access is denied. Make sure the disk is not full or write-protected and that the file is not currently in use."
Run the Note Pad accessory. Create a file in the testfolder named "Foo.txt". Try to rename it in Windows Explorer. Same problem.
If you perform equivalent operations on an OS X System via AFP mount to the same test folder, you won't have any problems; the ACL privileges will be correctly granted.
The only workaround I've been able to come up with to grant Windows users "rename" privileges on our SMB mounts is to do so by enabling read/write POSIX privileges on the enclosing folder ("testfolder"). You can either:
1) Make the user the POSIX owner of the enclosing folder, and grant the owner read/write access, or
2) Set the POSIX group to a group the user is a member in, grant that group read/write access, or
3) Enable POSIX world read/write access (careful!).
Without POSIX read/write privileges to the enclosing folder, it would appear that Windows users on SMB shares can't rename files or folders. Interestingly, they can upload folder hierarchies with arbitrarily named files and folders and won't run into problems; it's specifically when items are renamed when they already exist that you may run into problems.

Just an FYI: I received a response to my bug report. Apple reports that this problem has probably already been addressed in OS X Server 10.5.3, so it's likely this issue will disappear when I update my server from 10.5.2 to 10.5.4.
If you look at http://support.apple.com/kb/HT1142, there's this item:
File Services
The smb.conf file is updated to include the line "acl check permissions = no" in order to provide expected permissions behavior for Windows clients connecting to the SMB service.

SMB Shares and aliases break

Hi
I have installed SnowLeopard. We have have several machines running 10.5 (leopard). The have access to a windows server for some filesharing. There are aliases (created with the macs) on the server for easy access via smb.
However it turns out that SnowLeopard thinks the aliases are unix files. If I create an alias with snow leopard then original leopard (10.5) does not recognize it as an alias. It would appear that the two leopard versions treat aliases differently, at least over networks.

Snow Leopard is apparently having issues with SMB shares and login reliability. Seems to require a fresh login/restart as an example otherwise.

Using an "if not exists" command with a folder on an SMB share

I'm trying to use an "if not exists" command on a folder which is stored on a mounted smb share..
This part of my script is supposed to check if a folder exists and;
If it does - Skip to the next part of the script
If it doesn't - Create the folder.
At the moment it either errors saying that the folder doesn't exist or doesn't create the folder.
I can get this script to work fine using local folder paths but I want to do it on an SMB share..
Here's my script.
Many thanks in advance.
Martin
set username to (do shell script "whoami")
set Media to " Media Files"
mount volume "smb://172.22.8.23/macmedia$"
tell application "Finder"
if not (exists ("smb://172.22.8.23/macmedia$/" & username as text) & Media as text) then
make new folder at "macmedia$" with properties {name:(username as text) & Media as text}
end if
end tell
tell application "Finder"
set mnt to ("smb://172.22.8.23/macmedia$/" & username as text) & Media as text
try
mount volume mnt
end try
eject "macmedia$"
end tell

Hi Camelot,
Thanks a lot for that the script's working as it should now..
I'm still having intermittent problems on some clients where it will only map the root volume "macmedia$" and freeze there.. This is a problem as they can then see and access everyone elses folders from there.
Do you know of a better/cleaner way to do what I'm trying to acheive? All i'm after is mapping an additional drive for student's so they can save larger files to our media server within their own folders.
Is there a way of checking if a folder exisits within an smb share without mounting the volume? Just trying to think outside of the box a bit..
Here's my new script;
set username to (do shell script "whoami") & " Media" as text
mount volume "smb://172.22.8.23/macmedia$"
tell application "Finder"
          if not (exists folder username of disk "macmedia$") then
make new folder at disk "macmedia$" with properties {name:username as text}
          end if
end tell
tell application "Finder"
          set mnt to ("smb://172.22.8.23/macmedia$/" & username as text)
          try
mount volume mnt
          end try
          eject "macmedia$"
end tell
Many thanks,
Martin

Using single SMB share with multiple Hyper-V clusters

Hello,
I'm trying to find out if I can use a single SMB share with multiple Hyper-V Clusters. Looking at:
How to Assign SMB 3.0 File Shares to Hyper-V Hosts and Clusters in VMM
I think it's possible. Since the File Server is going to handle the file locking it shouldn't be a problem.
Has anyone tried that?
Thank you in advance!

Hello,
I'm not sure that's possible, I get this from this statement:"Assign the share—Assign
the share to a virtual machine host or cluster."
Even if it worked I wouldn't do that. Why don't you just create multiple shares?

Trouble with wireless n and smb shares

I have a bit of a per-plexer here.
I have a personal mac that up until a little while ago, ran 1.5.8 flawlessly for six months since i had it.
This included a lot of mounting my windows 7 file server and watching movies or listening to music over wireless G. Every night in fact I would fall asleep to a movie, then wake up and play some music from my music folder on the same server.
The battery would die nightly of course. Morning, charge it up with some music on.
I picked up a copy of snow leopard upgrade for 30 bucks when it was released or there about and installed it. Went fine and I continued happily using the machine for about 2 months.
Then I bought a belkin wireless N gigabit router, to replace my wrt54g. It worked alright and I continued my daily/nightly routine, watch a movie, sleep, listen to music.
However the first morning, and every morning subsequently there after I have run in to a pain-in-the-butt problem.
I awoke to find, like always, my server shares still mounted (or at least they appeared to be). But opening any of them would present a blank finder window, like no files were available.
Unmounting and re-mounting the shares would fail, with a message saying unable to connect to the PC.
So, what do you do next? I reboot. My programs close, the dock, finder, my background turns to the blue solid.
System stops re-booting... it sits here, with a plain cursor and I am unable to do anything but hard-power it off.
After a hard-reboot,everything functions normally until it hibernates or sleeps with the samba shares.
I took the router back and got a dlink n/gigabit router instead, cussing out belkin on my way to the store. No change!
So I reinstalled (I didn't even archive, i just blew it away) - installed 10.5.8 again, upgraded to SL, and connected to my wireless. I can still reproduce the issue.
So, i'm bummed, i've tried a lot of things I wont bother listing here but one more important detail i wanted to add is:
I work at a company that has blanket wireless b/g coverage using multiple access points and a controller to do load balancing and access point switching.
Recently, we got a few N access points from the provider and I set them up around the office in a new, isolated SSID on the subnet i do my work on. Using WPA2 Psk, like at home.
So, now to be fair I've got a slightly-newer mac at the office, same unibody but late 2009 instead of early 2009 (sd slot instead of express slot). I threw SL on it, and connected to the new SSID i setup and finally connected to our netapp and left for the night.
Come in in the morning and I can reproduce the issue on the work mac.
So, two different macs, 2 very different N wireless networks and 2 different file server platforms. But same prob, **** thing chokes overnight.
I have been able to reproduce this issue with a slough of late 2009 macs at the office now, as I handed out the SSID key to those with SL as my unwitting test subjects. Everyone's coming up with the same problem.
Has anyone out there run in to this? It's such a huge issue i'm surprised i can't find anymore information about it!
Thanks,
Josh

I took a look at the logs and copy and pasted a lot, these are a few before and many from AFTER the hibernation last night.
10-04-15 12:23:59 AM kernel hibernate image path: /var/vm/sleepimage
10-04-15 12:23:59 AM kernel sizeof(IOHibernateImageHeader) == 512
10-04-15 12:23:59 AM kernel Opened file /var/vm/sleepimage, size 2147483648, partition base 0xc805000, maxio 400000
10-04-15 12:23:59 AM kernel hibernate image major 14, minor 2, blocksize 512, pollers 5
10-04-15 12:23:59 AM kernel hibernateallocpages flags 00000000, gobbling 0 pages
10-04-15 12:23:59 AM kernel NVEthernet::setLinkStatus - Valid but not Active
10-04-15 12:23:59 AM kernel AirPort: Link Down on en1. Reason 8 (Disassociated because station leaving).
10-04-15 12:23:59 AM kernel System SafeSleep
10-04-15 6:52:18 AM kernel hibernatepage_listsetall start
10-04-15 6:52:18 AM kernel hibernatepage_listsetall time: 101 ms
10-04-15 6:52:18 AM kernel pages 270008, wire 57222, act 56136, inact 190, spec 78, zf 0, throt 0, could discard act 30534 inact 16602 purgeable 6519 spec 102727
10-04-15 6:52:18 AM kernel hibernatepage_listsetall found pageCount 113626
10-04-15 6:52:18 AM kernel IOHibernatePollerOpen, mlget_interruptsenabled 0
10-04-15 6:52:18 AM kernel IOHibernatePollerOpen(0)
10-04-15 6:52:18 AM kernel writing 111988 pages
10-04-15 6:52:18 AM kernel image1Size 126571008
10-04-15 6:52:18 AM kernel PMStats: Hibernate write took 3775 ms
10-04-15 6:52:18 AM kernel all time: 3775 ms, comp time: 767 ms, deco time: 0 ms,
10-04-15 6:52:18 AM kernel image 226658304, uncompressed 458993664 (112059), compressed 223746576 (48%), sum1 44b2f2dc, sum2 b54e1f71
10-04-15 6:52:18 AM kernel hibernatewriteimage done(0)
10-04-15 6:52:18 AM kernel sleep
10-04-15 6:52:18 AM kernel Wake reason = PWRB
10-04-15 6:52:18 AM kernel System Wake
10-04-15 6:52:18 AM kernel Previous Sleep Cause: 5
10-04-15 6:52:18 AM kernel en1: 802.11d country code set to 'X0'.
10-04-15 6:52:18 AM kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
10-04-15 6:52:18 AM configd[14] network configuration changed.
10-04-15 6:52:18 AM configd[14] setting hostname to "hostname.local"
10-04-15 6:52:19 AM kernel NVEthernet::setLinkStatus - Valid but not Active
10-04-15 6:52:19 AM kernel en1: 802.11d country code set to 'US'.
10-04-15 6:52:19 AM kernel en1: Supported channels 1 2 3 4 5 6 7 8 9 10 11 36 40 44 48 52 56 60 64 100 104 108 112 116 120 124 128 132 136 140 149 153 157 161 165
10-04-15 6:52:20 AM kernel Auth result for: 00:24:01:f3:01:5a MAC AUTH succeeded
10-04-15 6:52:20 AM kernel AirPort: Link Up on en1
10-04-15 6:52:20 AM kernel AirPort: RSN handshake complete on en1
10-04-15 6:52:22 AM configd[14] network configuration changed.
10-04-15 6:52:22 AM configd[14] setting hostname to "hostname.domain"
10-04-15 6:52:27 AM Firewall[407] krb5kdc is listening from :::88 proto=6
10-04-15 6:52:27 AM Firewall[407] krb5kdc is listening from 0.0.0.0:88 proto=6
10-04-15 6:52:40 AM ntpd[310] time reset +0.219956 s
10-04-15 6:53:36 AM [0x0-0x25025].org.mozilla.thunderbird[839] Warning: unrecognized command line flag -foreground
10-04-15 6:53:38 AM WindowServer[423] kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10-04-15 6:53:38 AM com.apple.WindowServer[423] Thu Apr 15 06:53:38 pluto.sunlab WindowServer[423] <Error>: kCGErrorFailure: Set a breakpoint @ CGErrorBreakpoint() to catch errors as they are logged.
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60
10-04-15 6:55:34 AM kernel smbfssmblookup: smbfssmbqpathinfo error = 60

Windows SMB shares not showing in finder

hi,
i'm using 10.5.8 on a powermac G5 in the office and recently experienced some difficulties regarding SMB shares. there are two Win XP 32bit machines in the office network, one Win 7 64bit machine and the powermac.
1) usually, the powermac could see and access all three windows machines via finder's sidebar. that stoped working some weeks ago. none of the three PCs shows up in the sidebar now. when i use finder's "connect to server" feature, the connection is established without problems. network printing to one of the XP machines also works fine. the mac's firewall settings where set to “Set access for specific services and applications” all the time, showing AFP and SMB shares enabled. just out of curiosity, i deactivated the firewall… and voila: my three PCs showed up in the finder sidebar again. changed it back… no PCs there
what's that? why did it work before, with the firewall enabled, and all of a sudden it doesn't work anymore and i have to shut down the firewall, to see my windows shares?
2) for some time it was sufficient that i could access the windows shares from my mac. now my colleagues needed to access the mac from their windows machines. as they do not need to have access to my entire home folder, i added the relevant (sub)folder from my documents folder via SMB guest sharing, setting the access rights to "read&write" for everyone, so that no password was needed for guests accessing that folder. however, all three windows machines could only see the standard public folder with its drop box, but not the newly added folder. experimented for over an hour or so, changing settings, trying to add other folders… until i found out, that the folder will only show up on the windows network, when it's located on the top level of my home folder, but not, if it's located in a subfolder (i.e. in documents, music, etc.)
is this meant to be that way? or am i doing something wrong?

If this is still driving you crazy...
I had the same problem and by figuring out which machine was the Master Browser I managed to fix it. I have a Windows 7 system and it had taken over as the Master Browser (probably because I had to rebuild my Mac). I disabled the Computer Browser service on the W7 computer and a 2003 server in my network automatically took over as the Master Browser. All of the Windows machines immediately appeared under Shared Items on my Mac sidebar.
I followed the instructions from:
http://robmulally.blogspot.com/2009/03/macbook-master-browser-and-my-mate.html
- on how to figure out which machine is the Master Browser in the network. The link came from a different discussion on the same issue (https://discussions.apple.com/thread/1877116?start=0&tstart=0). There are also instructions (although somewhat vague) on how to make your Mac the Master Browser.
I hope this is of some help.

SMB Share with Access Based Enumeration & Mac OSX 10.8/10.9

Hello,
I've been working on a bit of a problem related to some SMB Shares on Windows Server 2012 with Access Based Enumeration with Mac OSX 10.8 & 10.9.
Basically, we have one network share that mounts for all of our Students & Faculty on campus. Then, based on which security group the user is inside of in Active Directory, they gain access and visibility to different folders. (Basically, if they are members of the graphic design department, they get access to the Graphic Design's folder). All of that is working fine, no problems. From there we have 3 folders that branch off. We have a Distribution, an Open, and a Dropbox folder.
Distribution is setup as a spot for instructors to have full access, students have read access, They're able to drop files into this locations, to distribute them to their students. This folder is working fine, no problems.
Open is setup with everyone read/write access across the board. This folder is setup for students to share data to each other, work on projects, etc. This folder is working as intended, no problems.
Dropbox is the only folder we're having trouble with, i'm assuming because it's settings are the most complex out of the three. The purpose of the drop box is for students to have read/write control over their own content, but not others, and instructors to have read/write over this entire folder.
Now that I've laid out our Setup, the problem we've encountered, is ONLY occurring inside of the Dropbox folder. When I try to Drag/Drop OR Copy/Paste from another location on the computer into the Dropbox folder, I get a permission error. HOWEVER, if I have a file open, and I click "save as" browse to the dropbox folder, I can save the file into that location without any trouble. Also, on our windows computers, with the same exact users, drag/drop & Copy/Paste work normally.
Things I've Tried:
Disabling the .DS_Store - I figured in the drop box, the .DS_Store would be created by the first user who copied a file in, then subsequent users would not have access to the .DS_Store.
CIFS/SMB1 - I've read that SMB2 can cause some trouble while connecting to SMB Shares, so I tried both connecting via CIFS, and also by forcing back to SMB1, with no fix.
Am I missing something with this? I've read a lot about people having trouble connecting to SMB Shares, but for us it had not been a problem up until this point. Does anyone know what a possible fix might be for this? I'm sifting through internet searches right now, trying to find a solution, however MOST of the responses I see are regarding the two things I've already tried.
Any suggestions would be greatly appreciated.
Thanks!

hi everybody
I really need some help so here is a little up !
thanks !

Finder Size Mismatch with SMB Share

Similar Messages

Maybe you are looking for