Searching SMB Mounts

I'm having problems with one of my machines searching SMB shares. We have several Mac Pros that can search these shares fine (all on 10.5.5) and we have one Power Mac that can't search these shares (also on 10.5.5). I've tried rebuilding the spotlight index but I don't think that matters because it's not a spotlight search, but rather searching through a finder window and selecting the mounted share. Any suggestions? I'd even be happy with a third party app that would allow me to do this but can't seem to find anything.

anyone???

Similar Messages

Does anyone know of an app or solution to searching SMB mounted Windows network volumes?

Are there any solutions out there for searching Windows volumes? Our file server runs on a Windows box and trying to search for files from my department's Macs is extremely hit and miss, mostly miss. I've done some searching but am coming up empty for an app or other solution to getting results when searching the file server.

You could try reading this: http://support.apple.com/kb/HT4199
and
this: http://support.apple.com/kb/TS3727

10.4, active directory and smb mounts

I am having a problem mounting windows shares using smb mounts. I am getting the dreaded data could not be read or written error -36 problem. I have tracked it down to the number of groups an account is a member of. If I login with an account that is a member of roughly 6 groups, I can connect to shares just fine. But if I connect to shares with an account that is a member of roughly 30+ groups, I get this error. I get the error about Socket is not connected when I try to connect through the terminal. I have tried the nsmb.conf file. This is a fresh install of 10.4.1 with the 10.4.4 patch applied. I am also using the Active Directory plugin (Windows 2003 domain, shares are located on 2003 also).

all security groups. They have the network set up for every share there is a group setting permission. Te accounts I am having trouble with is the student accounts. They have a default set of groyup membership that allows them access to all related student activity. This has lead to some very large number of groups that they are members of.

Finder Content not updating with files on SMB mount

I have Mountain Lion 10.8.2 on a Mac Mini. I work in Adobe Lightroom 4 and Photshop CS6 with files hosted on a PC running Windows 7 Ultimate, and access these files via an SMB mount on the Mac. Both machines are up-to-date on their respective updates.
This worked fine up til recently, when I started noticing Finder contents don't necessarily update when the files change on the SMB-mounted filesystem. For example, if I create a new file, say, using Photoshop, and save the file, then try to see the file in Finder (so I can copy it to another location), the file doesn't show up. Force-quitting Finder & restarting it causes the new file to appear, but this is a temporary fix, as the problem sometimes recurs again when I create more new files.
It seems like this problem appeared after the 10.8.2 update, as I never noticed it with earlier releases. Have any of you seen this? I do my SMB mounts via the "Connect to Server (CMD-K)" dialog. Would I be better off mounting it from the command line with some specific options?
Thanks in advance...

Try deleting this file: com.apple.sidebarlists.plist
/Users/YourName/Library/Preferences. Drag that file from the Preferences folder to the Trash, empty the Trash and reboot. See if that helps...
Seems to me that Adobe is very picky about where the files are kept on the hard drive. You might not want them in the Sidebar. Whenever you do an Adobe software update, the installer needs the path to where those files go. If it's missing in action, it can wreak havoc.
Make sure when you do Adobe updates, if there is a link included or a Read Me file, check that out first before installing anything.
Run Disk Utility and Repair Disk Permissions BEFORE and AFTER any software updates:
Launch Disk Utility. Select MacintoshHD in the panel on the left, select FirstAid, then click: Repair Disk Permissions. Quit DU when it's finished and reboot.
Carolyn

NFS/SMB mount solution, Netware to Linkstation

We have a remote office with small backups to do on a daily/weekly basis and they are using a Buffalo Linkstation live to do them. They do this from an XP/Pro workstation. Essentially they have the Netware volume they wish to back up mounted as a share on the workstation. The Buffalo Linkstation drive is connected to the local switch with a static IP. They mount (windows, e.g. \\linkstation\backup) the drive and then use xcopy to back up the files of interest.
I would like to be able to do this on the server as a scheduled task. Is there a practical way to initiate an NFS or SMB mount and then use bash scripting to backup?
We are talking Netware 6.5 SP6. (OES Linux soon, but not quite soon enough.)

If Linkstation 'exports' its drive as an NFS volume, then you could use
NFS Gateway
(http://www.novell.com/products/netwa...quicklook.html) to mount
it so it appears as a local volume; this is my impression from the way
your question was worded but I don't think this is what you really want?
I think
http://www.novell.com/documentation/...s.html#unx-nfs is
what you're looking for instead: exporting a NetWare volume as NFS/SAMBA?
Peter
eDirectory Rules!

Wrong or negative disk space in large SMB mounts, "not enough free space"

Hi,
MacOS 10.4 and perhaps earlier sees large SMB mounts as having incorrect or, which is crazier, negative disk space. It's an obvious signed integer overflow. E.g.:
$ df -h .
Filesystem Size Used Avail Capacity Mounted on
//XXX;xxx@xxx/xxx 973G -1.9T -1.2T 225% /Volumes/xxx
It doesn't seem to be an inherent problem of the SMB protocol as MacOS X 10.5 can correctly recognize and report the terabytes for the same SMB share:
$ df -h .
Filesystem Size Used Avail Capacity Mounted on
//XXX;xxx@xxx/xxx 5.0Ti 2.1Ti 2.8Ti 44% /Volumes/xxx
Windows XP has no problems with the share either as verified with Explorer and "dir".
The server s/w in my case is Samba but it shouldn't really matter.
The most annoying consequence from the bug is that Finder refuses to copy files to the share as it tries to check if there is enough free space in the destination volume beforehand.
Are there any immediate workarounds known for the issue, at least to make Finder copy work?
Thanks!
Yar

Sorry, but can you guys tell a client from a server and a protocol from its implementation? Camelot keeps telling his favorite tale about inherent 2TB limitation in the SMB protocol while it is clearly the MacOS client that had been broken until 10.5 came out.
Answering my own question, as usual:
Fortunately, Samba (the server-side thing) can compensate for broken clients with this handy option <[http://us1.samba.org/samba/docs/man/manpages-3/smb.conf.5.html]>:
max disk size (G)
This option allows you to put an upper limit on the apparent size of disks. If you set this option to 100 then all shares will appear to be not larger than 100 MB in size.
Note that this option does not limit the amount of data you can put on the disk. In the above case you could still store much more than 100 MB on the disk, but if a client ever asks for the amount of free disk space or the total disk size then the result will be bounded by the amount specified in max disk size.
This option is primarily useful to work around bugs in some pieces of software that can't handle very large disks, particularly disks over 1GB in size.
A max disk size of 0 means no limit.
Default: max disk size = 0
Example: max disk size = 1000

Tricky SMB mount...

We're running approximately 35 of our 500 clients as mobile, managed - non-syncing accounts.
They're bound to OD to be able to be managed from WorkGroup manager and bound to AD to use single login authentication and to have access to AD network resources.
All of our accounts have their own private folder on their respective domain's DC. What I need is that when they're authenticated on the OD server to have a SMB mount for that specific user - using their login name, something like this:
SMB://ourdomaincontroller/username$ (with the $ because it's a hidden share)
I have written a script that can do this for me using ${USER} from env, but you cannot manage scripts for a group in workgroup manager. And when adding an SMB mount via workgroup manager you're only prompted with a browser dialog, and can't edit it once selected.
I cannot add the script as part of the loginhook on the local machine because if they login off property (they're mobile) they'll be hit with an error - that and we're planning on adding more mobile units in the future - and will be turning them over to the user after a set period - at which point I just want to be able to unbind them - not be deleting login hooks, etc...
So from what I can see there's 2 options:
1) find some way to enable scripts for a managed group
2) find a way to add an SMB mount for a managed group that accepts an environmental variable
Neither of these I know how to do (if at all possible). Is there a way to do one of those - or another way
Thanks

I have the exact same issue. I'm hoping someone will shed light on this

Smb mount Windows share 10.6.8 vs 10.8.4

We have the following setup:
a windows file share
an iMac with 10.6.8 connected to active directory
a MBpro with 10.8.4 connected to active directory
logged into each machine w/ the same user
The 10.6.8 smb mounts (via Finder->Connect to server) to the file share as one would expect.
The 10.8.4 smb mount fails with an error message:
Error mesage: The foler "foldername" can't be opened because you don't have permission to see it's contents.
Here's what I've done:
checked the smb mount path and they are the same on both machines
mounted the folder on a windows machine
So, it seems that user permission is OK because it works on the 10.6.8 and windows machines.
Any ideas why it's failing on the 10.8.4?
Thanks!!!

Welcome to Apple Communities
1. Open Disk Utility and repair permissions
2. Open Finder, go to your user's folder > Library > Caches and delete everything
3. Verify disk
4. See if your apps are compatible with OS X 10.8 > http://www.roaringapps.com
You can also do a backup and create a DVD or USB drive to install OS X > http://arstechnica.com/apple/2012/07/how-to-create-a-bootable-backup-mountain-li on-install-disk/ When you start in 10.8 installer, open Disk Utility, select your volume and erase the drive, and install

Spotlight search HTML pages SMB mount

Hey everyone,
I have been having some trouble getting spotlight to show results for certain searches. I have several machines connected with SMB that I would love to search through. I tried to search for the string “founded in 1975” in one of these volumes (HTML pages) but I get nothing. If spotlight does not have a drive indexed can’t it just conduct a plain text search through the volume? I have a PC with the same computers mounted where right click -> search works just fine.
In the system prefs, I don’t see HTML pages listed in the Spotlight categories, is this included in Documents?

Maybe I misunderstood you. Are you wanting to search for and find the html files for the site inside the domain file or the jpg, mov, mp3 and other media files that you have added to the site?
The text for each page is located inside an xml file that has been compressed into a .gz file. These are located inside folders named "site-page-plus a bunch of letters and numbers" (one for each page of the site) and these are located inside a folder titled "domain-and some combination of letters and numbers". I don't know if spotlight can cread the contents of a .gz compressed file. That's what would have to be done.
It's highly unlikely that Spotlight will be able to index those files but miracles do happen (if you believe in miracles).
OT
Message was edited by: Old Toad

Errors when saving to SMB mounts (a thorough examination)

Several of the users I support have reported the following issue when trying to save files to the network from Photoshop. I have found several threads about this on both the Adobe forums and the Mac forums. However, in most of the threads the information provided is incomplete or does not control for enough variables. And the result is that Adobe seems to blame Apple, and Apple seems to blame Adobe. So blame aside, here is information that I hope helps Adobe solve the issue at hand.
When saving to a mounted SMB point, users report one of two errors:
Could not save <filename> because of a program error
Could not save <filename> because write access was not granted
I can replicate the issue on:
Lion 10.7.X with Photoshop CS 5
Lion 10.7.X with Photoshop CS 5.1
Snow Leopard 10.6.X with Photoshop CS 5
Snow Leopard 10.6.X with Photoshop CS 5.1
Details:
We have only seen this error in Photoshop. << Adobe has seen the same problems in several other applications >>
I have not tested out whether the issue applies to any other products in the CS suite.
At first I thought the issue might have to do with permissions, but it does not. I have reapplied permissions and the issue persists. And it affects all users, including Domain Admins, such as me, who have no R/W restrictions at any level.
The issue only occurs when Finder is in a view that shows a thumbnail/preview of the image.
Switching Finder to list mode resolves the error in all scenarios
So far I can replicate this with any file on any mount on any of our servers
It only occurs on mounted network points (ie - if I move the files locally, no errors are encountered)
For the following tests, presume the following:
Source folder: smb://example/source/folder
Target folder: smb://example/source/folder
Target sub-folder: smb://example/source/folder/sub
Here are the steps I tested:
Opened the file problem_file.psd.
A warning pops up prompting me to resolve a font vector issue, I chose "Update"
Note: that this error does not pop up for every file, just the original file I worked with, but this warning has nothing to do with the errors being received
Moved a layer so that there would be a change to save
Clicked save
Received the error: "Could not save <filename> because of a program error" << probably related to the known MacOS bug on SMB, or a known Finder/thumbnailing bug >>
The original file, problem_file.psd, is *DELETED* (very problematic) << Known MacOS bug in SMB service, Apple is working on it >>
Then I tested with multiple variations of the following to conrol for things such as layers or font issues:
To eliminate the source file being the issue, I used a .png file that I had created locally with the OS-X screen shot keyboard command. This eliminated layers and fonts as issues.
In step 2 I chose to not update the font vector issue
In step 4 I tried saving as different file types (.jpg, .png, .gif)
Prior to step 6 I flattend the image to eliminate fonts and layers. This eliminated layers and fonts as issues.
Prior to step 6 I flattened the image, duplicate the image, closed the original (without saving), and attempted to save the new duplicate. This eliminated layers and fonts as issues.
Each variation still resulted in "Could not save <filename> because of a program error" and resulted in the deletion of the source file.
Next I controlled for saving image previews:
Photoshop -> Preferences -> File Handling
Under File Saving Options -> Image Previews, I set it to "Never Save" previews
Now when I repeated the tests from aobve, I receved the error "Could not save <filename> because write access was not granted".
Next I controlled for .DS_store files:
Disabled .DS_Store file creation on remotely mounted points.
Deleted the .DS_Store file for the source folder
Verified that .ds_store files were not being created on remotely mounted points
Ran the tests above, and the issue persisted: "Could not save <filename> because write access was not granted"
Now I decided to test sub-folders:
Created a target sub-folder.
Repeated the test above, and its variations, but saving the problem_file.psd to the target sub-folder.
Still received one of the two errors, depending on the variation, but the source file is no longer deleted. This make sense because saving in another directory is really a "save as", and one would not expect safe saving (talked about more later) to affect source files in this scenario.
Sort of a Solution:
Open the file from Finder
Depending on the Finder view, Finder shows a thumnail of the image
Go back to Finder and select a different file
Make changes to the file
Save the file
No error is received
This is when I discovered that the error only occurs when Finder is in a view that shows a thumbnail/preview of the image. Further testing of Finder show that in Cover Flow the error only occurs for the selected image. For example:
Cover flow shows thumbnails/previews of files: A, B, C, D, E
Open A
In Cover Flow select file B
The thumnails of of files A, B, C, D, E are still visible
Make a change to the open file
Save the change
No error is received
This shows that Finder is treating the thumbnails/previews of unselected files different than selected files.
An Interesting Twist:
If from the last scenario with Cover Flow...
Open file A
Go back to Finder and select a different file
Then make a change and attempt to save to the target sub-folder
Receive the error "Could not save <filename>" because of a program error.
Discussion:
Photoshop does something called safe saving.
Photoshop saves the current document to a temporary file with a unique name
Photoshop deletes the original file << this is incorrect >>
Photoshop moves the temporary file to a file with the name of the original file that was deleted in step 2 << incorrect: the temp file replaces the original with an OS call to a function that is supposed to be an atomic operation >>
However, you can see that "safe saving" is misnamed, because while the original is deleted, Photoshop does not appear to be correctly ensuring that permissions exist to allow the temporary file to be ranemd or that the temporary file was renamed without error. Photoshop is either:
Not checking for the error << yes, it is >>
Checking for the permissions and not catching the error << incorrect >>
Checking for the permissions and giving an error to generic to discern the exact problem from. << also incorrect >>
Somewhere there is a conflict (perhaps a race condition) between:
Photoshop creating the temporary file
The server applying permission to the newly created temporary file
OS-X reporting the file has been created
Photoshop deleting the original file
Photoshop saving the new file
Finder updating the thumbnail of the file
As I've shown here, the problem doesn't seem to reside fully with Apple or fully with Adobe. Hopefully this post provides enough information for some clever engineer to create a fix.
My information about safe saving is from an Adobe mod on a previous thread regarding this issue << and copied incorrectly, plus added bad assumptions>>. He detailed the process and also explained that Photoshop uses OS APIs to create and delete the files during safe saving. If his details are accurate, it seems that a temporary fix would at least change the safe saving process to the following:
Photoshop saves the current document to a temporary file with a unique name
Photoshop moves the original file to a temporary backup file (original-file-name.original-extension.bak)
Photoshop moves the temporary file to a file with the name of the original file moved in step 3
Photoshop checks to make sure that the temporary file has been succesfully renamed
If the temporary file has successfully been renamed, it deletes the backup file from step 2 OR if the temporary file has failed to be renamed, the backup is returned to its original file name
The appropriate error message, if any, is displayed
A Few Sources:
http://adobe.hosted.jivesoftware.com/message/4016324
http://forums.adobe.com/thread/732422
https://discussions.apple.com/thread/3380971?start=0&tstart=0

You got several details wrong.
And it sounds like you are describing 2 known MacOS bugs:
1) The OS fails when creating or swapping files on SMB servers, and this happens more often on files that have a resource fork.
2) The Finder/QuickLook/Thumbnailing holds a file busy when it should not, causing program errors or file is busy errors.
We did as much as we could to work around these issues in Photoshop CS6 - after spending a lot of time debugging the OS issues and working with Apple.
Apple is still working on proper fixes within the OS.

Error -36 while trying to move files on SMB mounted NAS

Hey,
I have been experiencing an error -36 while trying to move files around on my NAS.
I have the feeling it has something to do with insufficient privileges that are being acquired.
When mounting in windows explorer no problems arise.
When using the mac mounted disk in Parallels same problem.
Mounting disk in mac as following:
smb://login:password@ip-address/NAS-mount
or
smb://ip-address/NAS-mount (after which login details are prompted)
Any help or suggestions are welcome,
Jan

Hey,
I tried CIFS but that is giving me the same error -36.
I think it must have something to do with finder permissions as windows explorer is handeling it just fine.
Any more suggestions?
Tried:
cifs://login:password@ipaddress/share
cifs://ipaddress/share

Save to smb-mounted file = kernel panic

I use a shared network fileserver, with most of my files on a device mounted on smb:
Three times now I've encountered kernel panics while saving to a file on that device from BBEdit. Their technical support note (quite rightly I'm sure) that this can't be their fault.
Any tips would be welcome!
Mon Dec 3 17:23:54 2007
panic(cpu 2 caller 0x001A7BED): Kernel trap at 0x5cac5137, type 14=page fault, registers:
CR0: 0x8001003b, CR2: 0x00000010, CR3: 0x012ca000, CR4: 0x00000660
EAX: 0x00000800, EBX: 0x00000800, ECX: 0x00000f80, EDX: 0x00000000
CR2: 0x00000010, EBP: 0x5cbfb558, ESI: 0x00000000, EDI: 0x5cbfb780
EFL: 0x00010206, EIP: 0x5cac5137, CS: 0x00000008, DS: 0x5cbf0010
Error code: 0x00000000
Backtrace, Format - Frame : Return Address (4 potential args on stack)
0x5cbfb2a8 : 0x12b0e1 (0x455670 0x5cbfb2dc 0x133238 0x0)
0x5cbfb2f8 : 0x1a7bed (0x45ea20 0x5cac5137 0xe 0x45e1d4)
0x5cbfb3d8 : 0x19e517 (0x5cbfb3f0 0x5cbfb458 0x5cbfb558 0x5cac5137)
0x5cbfb3e8 : 0x5cac5137 (0xe 0x48 0x5cbf0070 0x1a0010)
0x5cbfb558 : 0x5cac6f23 (0x1219d3f0 0x1 0x0 0x0)
0x5cbfb578 : 0x1f0534 (0x5cbfb59c 0x1 0x5cbfb5a8 0x7276440)
0x5cbfb5c8 : 0x1f300a (0x1219d3f0 0x5cbfb780 0x92c19e4 0x383bd4)
0x5cbfb628 : 0x1da240 (0x1219d3f0 0x5cbfb780 0x92c19e4 0x0)
0x5cbfb8c8 : 0x355869 (0x7276440 0x0 0x80000008 0x92c19e4)
0x5cbfb908 : 0x1d6784 (0x72afb04 0x7276440 0x80000008 0x92c19e4)
0x5cbfb958 : 0x1c3c97 (0x1219d3f0 0x0 0x80000008 0x92c19e4)
0x5cbfbf78 : 0x3da847 (0x7a766f0 0x92c18e0 0x92c1924 0x0)
0x5cbfbfc8 : 0x19ea34 (0x91d1b00 0x0 0x10 0x0)
No mapping exists for frame pointer
Backtrace terminated-invalid frame pointer 0xb02522c8
Kernel loadable modules in backtrace (with dependencies):
com.apple.filesystems.smbfs(1.4.1)@0x5caaf000->0x5cadefff
BSD process name corresponding to current thread: BBEdit
Mac OS version:
9B18
Kernel version:
Darwin Kernel Version 9.1.0: Wed Oct 31 17:46:22 PDT 2007; root:xnu-1228.0.2~1/RELEASE_I386
System model name: MacPro1,1 (Mac-F4208DC8)

We have the exact same problem throughout our company. Apple was unwilling, as usual, to admit that leopard has a problem (despite that this issue didn't exist in 10.4) they wanted us to call Microsoft and said their solution would be to "downgrade to tiger". That is an upsetting response after dropping the cash to upgrade over 10 macs to Leopard; that are now all randomly panicking because of this issue. Way to treat your business customers and expand your influence in the corporate world Apple.
Maybe an ambitious soul out there will take the smbfs 1.4.4 from freeBSD and compile it into a patch for us and hope that works.

SMB mount error

I am trying to mount a Windows share either through Finder or from the command line. Finder gives me an error message:
Sorry the operation cound not be completed because an unexpected error occurred (Error code -50).
Finder connects to the server, asks for my password, but then give the error message. From the command line trying to mount using mount_smbfs, I get the password prompt and then a mount error message:
syserr = Invalid argument
I checked dmesg and the following line appeared after trying to mount either way:
mount version mismatch: kernel=103200, mount=103600
Anyone know what this means and how to fix it? I am running a PB 1.5 with OSX 10.4.6 with all the updates applied.

try using
mount smb: //ip.addr.of.svr/sharename
If you are trying to connect to an Active Directory share or a windows network that has security set to LSA 3 or higher, you will not be able to connect without 3rd party software, as OS X does not supprt LSA 3 or higher.

OSX client automatic afp/smb mounting

We have a osx 10.8 server and osx 10.7.-10.9 clients.
Recently I've been having prblems with an osx workstation that for some reason wants to mount the server file share with smb instead of afp (and for some reason with wrong username) – and can't save to the share in Word, Excel or ArchiCAD.
The thing is I don't have a clue why the workstation mounts the server as server.local – smb I've understood – instead of afp. Where ar ethe automatic mount settings stored so I can reset them?

There are several ways to mount a share automatically.
Easiest and most common way is to have it in the Login Items of the Users PreferencePane. Check there and if listed then remove it. Next open Keychain Access, and look for the smb share and delete the entry.
Once this is deleted then you can remount the share as AFP, and set it up to automount in the Login Items.

Smb mounted volume eject fails - in use by finder

Recently (Maybe starting with 10.8?) it seems if I "Map a drive" from my server,
(Using the Finder -> Go menu -> Connect to Server... Then entering smb://appserv1.home.local/g$)
It seems if I double click the drive in the finder it just spins and I am not able to eject the volume.
Last night this happened, and I left the machine running overnight - this morning the fans were spinning louder than normal and I noticed one core of my 4 core CPU was at 100% with the Finder as the process.
Oddly, if I use a 3rd party tool like Pathfinder, I can view the contents of the remote volume.
Has anyone else run into this?
(the shared volume is on Windows 2008 R2 server)

That's a toughy because there could be an alias or symbolic link or an application-specific item that's causing the problem. Restart and see if that'll do it. If not, boot with your install disk, select a language (Tiger), and, when the menu bar pops up, select Utilties/Disk Utility and repair disk and permissions (if it contains a bootable installation). Restart and see if that fixes things.
Alternatively, use the Terminal command lsof to list all open files. Type this into a Terminal window to read about its options: man lsof. If you know the /dev/disk id for that HD (use df -h, then use this:
lsof /dev/diskXsY
substituting the appropriate X and Y values.

Searching SMB Mounts

Similar Messages

Maybe you are looking for