Windows indexing service: how do I make it so network shares can be searched?

Question

I have a bunch of folders on a network share with thousands of files in them (application logfiles). I would like to be able to search these by filename quickly and eventually programmatically (perhaps via MSIDXS).

The problem is that I can't seem to add network shares to the indexing service. When I try to add a new catalog to the indexing service, the only thing I can add are folders that are under the C:\ drive. Anything with \\share\whatever\ is "invalid". Nor can I add drives that have been mapped to a network share. When I try it says the "catalog name or location is invalid."

Is there a way to index a network share for indexed search? What are my options for searching network shares efficiently?

FWIW, I am dealing with Windows XP.

I also tried installing Add-in for Files on Microsoft Networks-- still same problem.

Here is what happens:

I get this error whenever I try a UNC filepath:

Solution 1

There's simply no way to index non-Windows network drives on a 64-bit Win 7/8, with Windows itself. Other desktop search apps can do it, like Archivarius.

Solution 2

Use network share names instead of the network drive P:\foldername.

I just had the same issue, and solved it by using \\computername\foldersharename$. You'll have to enter a user account and password for server authentication.

Solution 3

You're looking for this Microsoft add-in. (More information)

Comments

[Lorenzo Von Matterhorn]

please do not use links as answers; Copy the relevant data from the link and paste it on your answer. Only then use the link as reference instead. if the link ever gets broken so does your whole answer.

[Evengard]

Any way to make them actually INDEXED?

[Astara]

Only if one find a program that builds a file-database to answer queries over HTML (using SOAP). There is one in MS's SharePoint services on their Server OS's. The protocol is documentedl: interoperability.blob.core.windows.net/files/MS-SEARCH/…. Then your client machine can query the remote file server to get responses from the remote indexing service. AFAIK, no one has written an open-source client for MS-Search, but the protocol is published for purposes of interoperability (like other OS's).