Q: Unable to search network drives with Lion...

I don't have anything new to add but am adding to the post count to hopefully escalate the issue.

I can't believe there isn't a fix for this!  Imagine the uproar if this was an issue in a new release of windows!! 

This destroys workflow for assembling catalogues from network files in indesign.  Everyone else is on windows in my office and you should see the looks I get when I say I can no longer search the network drive with the NEW mac OS.  Booooo apple, GET ON THIS!!!!!!!!!!!!!

please fix this! It goes without saying that we want spotlight searches to work on anything we connect the mac to.. it doesn't even work with apples own time captule. rediculous!! 

just so you know Apple Inc....for one line of code you removed, my whole office....30+ potential lion users...are NOT upgrading

so if you want to drop money by the thousands...I know you dont care as you have more than...exxon was it...keep up this crap

I am having the same issue.  I called Apple Care was on the phone for about half an hour, and looks like they are working on this, but we need this.  I hate when in my office people can search Windows Explorer (Parallels) to find stuff and can't use Finder. Please Apple fix this and don't wait for 10.7.3

I agree, shouldn't be an issue in the "world's most advanced operating system.  Well said

Same issue here. I was hoping 10.7.2 would fix this. This is VERY inconvenient... to say the least.

You all might want to drop a line here, the official OS X Lion Feedback page:

http://www.apple.com/feedback/macosx.html

Please request for help on the feedback page with the following Subject: "Lion CIFS search not working"

Here's the request form as macobs30 kindly suggested: http://www.apple.com/feedback/macosx.html

Let's make it as massive as possible.

easy find works....albeit slow, it works...

Please fix this soon Apple.

Same thing

I wish i could downgrade.

Snow Leopard was perfect.... worst money i've ever spent on apple's products.

I don't know about THAT. It really has some nice features and stability. They just choose to not work with something, like they did with flash. Once Microsoft caves in to apple, things will get better.

You sir...I'm not even going to say it.  "Once Microsoft caves...: ummm, sorry but CIFS and in general searching via SMB on connected network drives and/or NAS devices should be a STANDARD and not the exception...UNIX/Linux support these natively.

LOL. I am just adding a little zing to this mummuring post....I totlaly agree with you, just being crass

I'm a professional user who mostly works on location. If it wasn't for EasyFind I'd be royally screwed. Why is this taking so long? It's been months already!

Hi Everyone,

Finally, I learned from someone, who knows OS X and Apple deep down, the origin of this and related issues (iCal invitations, smb volume access/mounting, Spotlight indexing, etc...). It is a real deep-down problem and not just something than can be solved with some tweeks on the Lion systems settings.

Apparently, the problem is NOT on the Apple side. But rather on the (MS) Server side, which the Mac has to connect to by SMB.

Already since a few years Apple has been working on their own SMB client and has been notifying the other OS and Server developers.  Since the "others" ignored the enhanced security of Apple's own SMB, the communication between OS X Lion and especially MS Exchange 2010 Servers is strongly "affected",  or better screwed up..

This has a severe impact on ALL applications, which need to communicate with the MS Exchange 2010 Servers such as iCal, Spotlight & Finder, Mail, even keychain when trying to save credentials for smb volumes.  I have all these problems on my Macs and it is an Exchange 2010 Server issue - according to Apple, since they have been informing MS for a long time.

Now, the only thing Apple can - and will - do about it is to nicely keep asking MS to integrate support for the new and more secure Apple SMB client.

So I guess we all gotta wait... or try to rely on 3rd-party software... This is why Windows went down the hill.