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

Thanks for the info, very interesting.

I'm not really bothered who's fault it is, I just want it to work, like it did before I upgraded to installed Lion.

I couldn't agree more. I just want it to work as well.

The point is, however, Apple won't do anything about it until MS moves. So we might just stop telling Apple to do something.

Like I said before, when MS bends....

A very poor business decision if this is true.  Apple should remain focused on ensuring that its customers are satisfied with the products that it makes available to them. 

This includes providing systems that integrate, communicate and operate with the vast number of platforms being used by those customers. Computers (unlike phones and music players) cannot operate in a microcosm, they need to interact diversely with other peripherals, technologies and systems.

Searching is a basic OS function, and as such, should remain operational and backwards compatible with systems that were previously supported.    If Easyfind can do it, why not Spotlight?

Dropping support on the assumption that communication was provided (in advance) to other vendors - who for whatever reason, have not adapted the new protocols (if true), demonstrates an arrogance and a lack of concern for its own customers - who just want our OS to play nicely with the other technology we use and own.

It does not make sense to break your own OS functionality and upset your customers just for the sake of advancement (if that's what you call it).

The biggest disappointment, despite the numerous posts here, many calls to tech support (my own included), and ongoing cries for help and assistance; is the lack of official communication nor appropriate levels of response to this incident. My Applecare ticket was reported, escalated and then fell into a black hole. Poor customer service and wasted time and money from my perspective.  Result = unhappy customer dissatisfied with product and subsequent support.

I for one, having owned and worked with macs right back to their beginning, will consider very seriously before purchasing another one or spending money on Applecare.  I have been communicating my own feedback on my experience to my friends and colleagues in the IT industry, so that they can make informed decisions about whether  Apple hardware (along with its Lion OS), and Applecare is the best choice for them.

If my systems cannot work together and provide the basics then they have no place in my future set-up.

Well put.

And yes, if easy find can pull this off then it's hard to believe that this isn't just a tweak away.

When I called Applecare, I used exactly the same logic and arguments:

- SMB is a basic feature

- Exchange is out there, I cannot keep bothering my IT department

- Backwards compatibility

- Customer care & satisfaction

- Informing the users correctly

- 3rd party software works (Easy Find, Foxtrot, ...)

- Don't be so stubborn.

They disagreed in ALL points in regards to "Apple needs to fix it".

I work as well in a corporate environment and this is becoming unacceptable.

The issue surrounding SMB shares isn't entirely within Apple's Control. There is a big reason things worked one way with Snow Leopard and don't work the same way with Lion. The SAMBA development team switched from using GPLv2 to GPLv3 for their licensing. Unfortunately this action by the SAMBA team makes integrating SAMBA into Mac OS a non starter. Luckily, Apple was already internally developing their own SMB code to work with SMB shares. It is their code, rather than SAMBA that has been implemented into Lion. Overall, this is a very good thing as much of the SAMBA work isn't staying current with many of the changes that Microsoft has made to the SMB protocol and the surrounding architecture in their more recent releases.

That may be so, but that doesn't mean that omitting network searching by design is good thing. If only Apple would say something like: "we haven't gotten around to implementing network searching on SMB, WebDAV (yes it is not just SMB), and other network volumes but we are working on it for a future update of 10.7."

Unfortunately they are just saying something like "we know it doesn't work and it is by design, thank you and have good day."

Apple really has to get to back to its senses in the coming updates, because currently I'm not sure my next laptop will be a Mac.

@Cetuma:

This SMB issue is completely under Apple's control. The OS browses through the remote filesystem to build the Finder's tree view. So it "knows" each file's location. Every file is readalbe without any problems through SMB. The only missing link is between the SMB browser and Spotlight. Indexing doesn't work anymore.

So they cannot claim it is an SMB issue.

@ahenket:

Would be nice if someone from Apple would say anything. Or did they ?

@Apple:

Pleeeassse fix this ! This is a productivity show stopper.

-- Harald

hschneider wrote:

 

 

@Apple:

Pleeeassse fix this ! This is a productivity show stopper.

 

And you have of cause reported this issue to Apple since this is a userforum right ?

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

/Dennis

here is how our IT department will be attempting to fix this...

We use software on our windows server called extremeZ-IP for file access and resources to all the mac users.   A new version extremeZ-IP2 is out and that is what we are upgrading to.
 

hope this helps. Notice its not an Apple fix, nor a Microsoft fix...

Hello, is extremeZ-IP really good? does it make network faster?

I will let you know. I am on the user side of things, not the admin or IT

I am saying my prayers

Some of my iCal issues could be resolved on the Exchange Server side....  But the smb and spotlight issue remains.... So apparently they were unrelated. In the end the Apple support was right. It was not a Mac problem. As for the Spotlight/SMB issues, the admins say it is not their Exchange server, but yet another NAS server....  So the journey continues ;-)

I have the same problem. When i use the terminal and the find command osx 10.7 find all the files on the smb volume.

find command:

 

find /Volumes/Server -name "*put_in_your_search*"

Server means the volume name of the mounted server