Re: Search not working

Thanks for the suggestion but, Central Administration>Application
Management>Authentication Providers>Edit Authentication, does not provide the
ability to indicate whether the web application is using SSL or not.

I’ve played around a bit and got search working again.

This is what happened.

Previously, my remote users were having an issue. The domain name was
automatically being populated before the user name, after a failed login
attempt. In an attempt to fix that, in IIS, I changed IIS Authentication for
the web site to Basic authentication. I was not terribly concerned using
clear text authentication over SSL. And it did solve that problem.

Here’s what I did.

In IIS, I changed IIS Authentication for the web site back to Integrated
Windows authentication.

In WSS Central Administration>Application Management>Authentication
Providers>Edit Authentication, I made sure Integrated Windows authentication
and NTLM was checked.

Search works fine now.

However, the issue with the domain name automatically being populated before
the user name, after a failed login attempt is back. Is there another way to
fix that in a way that does not break the search feature? Should I start
another post for this issue?

--
Jackson5403



"callahan" wrote:

I have seen situations where Search does not work if you are using Kerberos
on the default address for a web application (it prefers NTLM). I have also
read articles that stated that SSL on the default address for a web
application will also mess up Search-- however, I have never had it happen.

Before I tell you to extend your web application and put SSL on the extended
web app instead-- tell me- did you go into Central Administration after
adding the SSL certificate in IIS, and indicate in Authentication Provider
that that web application was using SSL? You might want to change that
setting, then do an IISRESET, to see if that helps before doing anything
else.

-callahan
"jackson5403" <jackson5403@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:897EFF67-D449-4893-A7EE-644EAD446051@xxxxxxxxxxxxxxxx
I am running WSS 3.0 (domain creation mode) with SQL2005 backended on
another
server.

I created a WSS site that originally wasn't set up to use SSL during
creation.

Subsequently, I have installed an SSL certificate and required SSL
communication in order to access the site.

I changed the alternative access mappings on the site and almost
everything
is working ok. What isn't working is Search.

I'm getting the following errors in the event viewer,

The start address
<sts3://domainname/contentdbid={c146f633-f577-480b-a01f-c556296e2cc3}>
cannot
be crawled.

Context: Application 'Search index file on the search server', Catalog
'Search'
Details:

Access is denied. Check that the Default Content Access Account has access
to this content, or add a crawl rule to crawl this content. (0x80041205)

I've implemented the recommended least privileged account recommendations.
Don't want to circumvent security but have looked at this as possible
problem
area. Everything seems okay. I have multiple sites and Search is working
on
all other WSS sites.

This appears to be limited to and related to installing the certificate
and
changed the url from http - https.

Can you give me a clue how to fix this?


--
Jaskson5403




.

Relevant Pages

  • Re: Mixed Mode Authentication in .net 2.0
    ... There are two parts to SSL, which is why this can be confusing. ... encryption and authentication of the server. ... ADFS supports a component called the federation service proxy which is ...
    (microsoft.public.dotnet.framework.aspnet.security)
  • Re: Search not working
    ... Oops, you're right, there is no SSL under authentication providers-- that'll ... I know that search prefers NTLM ... I changed IIS Authentication for the web site back to Integrated ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: Can SSL sessions be compromised?
    ... the proxy machine -- if I enable local cookies for authentication this ... your "SSL server" machine may be trying to catch some simple types of ... information carried by the digital certificates was ... clicking on any RFC number, brings up that RFC in the lower RFC summary ...
    (comp.security.misc)
  • Re: Postfix + Auth + SSL + pop3s/imaps
    ... >> to use for authentication. ... Or I would still need SASL for smtp? ... >> if it's Plain or Login because I'm going to use SSL and that would ... >> encrypt both Login and the data channel. ...
    (freebsd-questions)
  • Re: SSL/https - How to configure Tomcat?
    ... One aspect of SSL is authentication. ... > You mean it's right to say that SSL is an authentication method? ... is authentic (=> could be the bad guy's server). ...
    (comp.lang.java.help)