K
ker_01
Win XP sp2, IBM/Lenovo laptop(s)
I use a laptop at work and have several network drives mapped. When I am
hooked directly into the network at our site, I can use the search function
and search the drives (normal, expected search behavior). However, when
trying to search from other locations (VPN via broadband in the same city,
or internal company network from another state) the search doesn't seem to
"see" subdirectories or files- there is a several-second pause before the
search starts, then it almost immediately stops and indicates no files
found. I can still navigate these directories manually, so I do have access
permission- this issue is specific to the search function only.
This has happened with two different laptops, two different users, and two
different "away" locations, so that helps eliminate some potential root
causes like corrupt profile, bad network card, etc. Now I'm trying to figure
out what else it could be.
1) It might be a timeout issue, where anything coming in from "outside" the
home site just takes too long to get a response from the server(s). I'd like
to test this, but I don't know if the standard search timeout is 'exposed'
somewhere (like the registry) where I could increase the value and see if
that makes a difference. Does anyone know if this timeout value can be
edited, and where it is?
2) This is a wild guess because I don't know anything about server side
stuff, but are there any settings that could specifically cause delays for
IPs outside of the 'accepted' local hardwire connected IP addresses? My
brain goes to hacker-prevention technology, but I'm not sure why that would
only affect the search while still allowing normal folder access for
legitimate users.
I'd appreciate any and all ideas-
Thanks,
Keith
I use a laptop at work and have several network drives mapped. When I am
hooked directly into the network at our site, I can use the search function
and search the drives (normal, expected search behavior). However, when
trying to search from other locations (VPN via broadband in the same city,
or internal company network from another state) the search doesn't seem to
"see" subdirectories or files- there is a several-second pause before the
search starts, then it almost immediately stops and indicates no files
found. I can still navigate these directories manually, so I do have access
permission- this issue is specific to the search function only.
This has happened with two different laptops, two different users, and two
different "away" locations, so that helps eliminate some potential root
causes like corrupt profile, bad network card, etc. Now I'm trying to figure
out what else it could be.
1) It might be a timeout issue, where anything coming in from "outside" the
home site just takes too long to get a response from the server(s). I'd like
to test this, but I don't know if the standard search timeout is 'exposed'
somewhere (like the registry) where I could increase the value and see if
that makes a difference. Does anyone know if this timeout value can be
edited, and where it is?
2) This is a wild guess because I don't know anything about server side
stuff, but are there any settings that could specifically cause delays for
IPs outside of the 'accepted' local hardwire connected IP addresses? My
brain goes to hacker-prevention technology, but I'm not sure why that would
only affect the search while still allowing normal folder access for
legitimate users.
I'd appreciate any and all ideas-
Thanks,
Keith