Hi Tim,
Hmmm... Yeah the GSA I believe would need to be able to reach the DC
in order to complete the authentication. Regarding the 401 you are
seeing, the GSA does not use login credentials for the network
diagnostics and it is only meant to see if there is network
connectivity so the 401 would be expected. A couple things to try as a
test:
1. Disable integrated auth. I don't think this will make a difference
but it could be changing something.
2. Enable anonymous access temporarily and crawl again. This will at
least tell us that there is nothing inherently wrong and that the
problem is definitely with auth settings.
3. I am not sure what you have in Crawler Access at this point but for
sanity sake, try to broaden the URL pattern you have there. What I
mean is to only put the host there with the trailing slash or if you
only have this one protected site, just try putting a slash. That will
tell the GSA that each time it gets a 401 for anywhere to use those
credentials.
If none of that helps I would contact support with the above
information and see if they can maybe find something.
Brian
Regarding LDAP settings on the GSA, that is actually only used for
secure serving as opposed to crawling so probably wouldn't be of much
use.
On Nov 22, 12:43 am, Tim Stevens <
tstev...@advsol.com> wrote:
> Brian,
> Thanks for replying. the user we created is a member of the domain and i do have the domain populated in the settings.
>
> When i test the url pattern in administration --> network settings i get a 'returncode 401, should be 200'.
>
> this machine is not in our dmz so i'm wondering if the attempt is failing because it can't talk directly to the domain controller.
>
> Would setting up LDAP Directory Server Addresss settings be something i should pursue?
>
> ________________________________________
> From:
Google-Search-...@googlegroups.com [
Google-Search-...@googlegroups.com] On Behalf Of brianb [
brianj...@gmail.com]