Windows Forum

Ask something
Discussion Locked

Indexing Service with Network Drives

0 helpful
4 replies

by donalda-m 2 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I am using Windows 2000 Professional, and would like to use Indexing Service for more powerful searches. I cannot seem to get it to add a directory on a network drive to a catalog - only local drives. I have put in the correct UNC path to the folderand entered "domain/user" and the password but do not get anything indexed on the remote drive. I have started and stopped the service and chosen to do a full reindex of the directory/folder with no success. **As an alternative I would accept a free or low cost way of doing free text or structured (Boolean, etc.) searches of multiple format documents on a network (other than implementing an intranet). Ideal would be to be accessible to multiple users, but limited access is OK too. Thank you.

4 replies

by joseph moore

This brings to mind a few things:
1) I can't remember specifically, but don't the Index Server files to be indexed need to be on a NTFS partition? Might be something to check.
2) HTML files, text files, and Office files above a certain build level(Office 97 SR2, I think, but I could be wrong here) are what it can index, so make sure the right files are in your networked share.
3) This really has the feel of one of those account permission security issues. Index Server runs with the Local System machine account, and I bet that it is using this account to go across the network to try to access the files, eventhough you are setting the user account/password to gain access. I would try changing the Index Server service to use a valid network account (with Log On As A Service on the Index Server system). Start up the service and maybe it will work. I have gotten similar problems with IIS going across the network to grab HTML files.
Hope this helps.

by donalda-m

Although I can't use this right now (I have thankfully left my former employer) I do believe that number 3 (security) was the issue.

This discussion is closed to new replies.