From: John Beckett 

"Geo"  wrote in message
news::
> Is there any way to make it work with index server running on a remote
> machine?

Yes. Here is half the story (Rich might like to tell us the other half, or
probably just a few experiments would clarify the situation).

If you run my Search program, then right-click the window and select 'Open
Settings File' from the menu, you can change the Catalog entry near the
bottom. Change it to something like:

Catalog=query://Server/System

Replace 'Server' with the name of the remote computer. Replace 'System'
with the name of the catalog on 'Server'.

After saving the change and clicking Yes to read the new settings, you can
run a query. The search will use the catalog (System in above) on the
remote computer (Server in above). The name Server obviously has to be
resolvable. Also, you need to be logged on as someone who is accepted at
the remote server.

The puzzling half of the story is how you control the result. If you were
to do the above and run a search, you might see 100 files listed. Say the
list includes:

C:\Docs\April.txt
\\Server\Data\May.txt

You are sitting at some workstation, and you are looking at a list of files
on Server. If you open the first file above, it obviously will not work
because your workstation will look on its C: drive, but the file is on
Server.

However, opening the second file will work (if you have suitable
permissions) because you are accessing the file via the share Data.

The setting 'Add Network Share Alias Automatically' in the Indexing Service
is on by default. Apparently it causes the result list to include UNC paths
when appropriate.

I guess that you would configure the catalog on Server so it only included
directories in shares accessible by users. Then, presumably, the result
list would only include UNC paths, and users could do searches and open
files from the resulting list.

John

--- BBBS/NT v4.01 Flag-5