asked on Windows indexing network folder problem
Hi,
on my workstation with Windows Server 2012R2 I have fast SSD drives in RAID1 for the system and two network locations for documents and working files:
- On LAN I have NAS server for Documents, Music etc...
- Via IPSec VPN I have mapped folders from server in datacenter with some important data
As I am on OC-3 155 Mbps internet connection with 2ms lag to datacenter, this works perfectly.
Now, both locations are mapped to drive names on my workstation, for example:
L:\ is \\LocalShare
R:\ is \\RemoteShare
Both mapped drives are included in my SEARCH INDEXING LOCATIONS.
PROBLEM?
While \\LocalShare gets indexed without a problem, the \\RemoteShare gets interrupted every week or so, because I connect from my workstation to remote router as my home router is not compatible with remote one for IPSec VPN.
So, connection with \\RemoteShare drops every week for as long as I need to notice. Then I reconnect and sharing works fine...
...BUT INDEXING gets totally lost!
Not only indexing of \\RemoteShare, but ALL indexing for everything on my workstation renders unusable. Searching in Outlook 2013 does not work anymore, searching for local files finds nothing etc...
I have to rebuild whole index to get it working again, but this takes 2 days as there are gozillion of files and items to index.
Any idea how to optimize indexing of \\RemoteShare?
Maybe to tell Windows it is remote, so indexing will not stuck when it is unavailable, but simply skip it and retry after some 15 minutes or so?
on my workstation with Windows Server 2012R2 I have fast SSD drives in RAID1 for the system and two network locations for documents and working files:
- On LAN I have NAS server for Documents, Music etc...
- Via IPSec VPN I have mapped folders from server in datacenter with some important data
As I am on OC-3 155 Mbps internet connection with 2ms lag to datacenter, this works perfectly.
Now, both locations are mapped to drive names on my workstation, for example:
L:\ is \\LocalShare
R:\ is \\RemoteShare
Both mapped drives are included in my SEARCH INDEXING LOCATIONS.
PROBLEM?
While \\LocalShare gets indexed without a problem, the \\RemoteShare gets interrupted every week or so, because I connect from my workstation to remote router as my home router is not compatible with remote one for IPSec VPN.
So, connection with \\RemoteShare drops every week for as long as I need to notice. Then I reconnect and sharing works fine...
...BUT INDEXING gets totally lost!
Not only indexing of \\RemoteShare, but ALL indexing for everything on my workstation renders unusable. Searching in Outlook 2013 does not work anymore, searching for local files finds nothing etc...
I have to rebuild whole index to get it working again, but this takes 2 days as there are gozillion of files and items to index.
Any idea how to optimize indexing of \\RemoteShare?
Maybe to tell Windows it is remote, so indexing will not stuck when it is unavailable, but simply skip it and retry after some 15 minutes or so?
Microsoft OfficeOutlookWindows OS
Last Comment
Andrej Pirman
ASKER CERTIFIED SOLUTION
THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
ASKER
No solution given for some time.
Closing the question.
Closing the question.
I had no end of problems with searching and indexing on remote data from my client when indexing wasn't enabled on the remote server for the share data I needed to search.