• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 206
  • Last Modified:

Search not working

Hello All,

I recently started to face a problem where in search is not working on one of the site collection for cross domain users. But they can perform search on other site collections on the same web application properly. The users belonging to the same domain can also view the search results on the problematic site collection. Crawling account has necessary permissions.

Eg: http://www.contoso.com/ - Search is working for cross domain users
      http://www.contoso.com/sites/teams - Not working  

There is no error on the page. It just says no search results were found ?
Mohit Nair
Mohit Nair
  • 4
1 Solution
Jamie McAllister MVPSharePoint ConsultantCommented:
Do the users definitely have permissions with their domain credentials to view the problematic site collection where the search results reside?

Is there anything in the architecture that might stop the search service querying their credentials? (Is Cross Domain authentication setup correctly?)

Some food for thought;



Mohit NairSenior AssociateAuthor Commented:
As far as authentication is concerned,  users have access to the problematic site collection and also to the root site collection. To check the cross domain authentication I dont have access to the DNS server so cant check that for the time being. I have already come across the first 2 articles that you provided. Checked AAM settings.
My settings is as below
Default: https://www.contoso.com/
Intranet : http://www.contoso.com/
In content source I have both the url added. Initially the search wasnt working on the problematic web application on our end too. So I added a crawl rule on it and search started to work. But at their end its still not working. Need immediate help. Thanks.
Minesh ShahSharePoint & all about itCommented:

1. Compare URL (added into the search content source) with entry in AAM Zone for working & non-working site collections.
There should be a difference. make up that difference & you are done if you are lucky.

2. I would add a host entry in one of user machine (from whom search is not working) to point to search / index server & see the behaviour.

3. Cross check AAM, Host header entries and IIS bindings on front ends, index servers.
Keep up with what's happening at Experts Exchange!

Sign up to receive Decoded, a new monthly digest with product updates, feature release info, continuing education opportunities, and more.

Mohit NairSenior AssociateAuthor Commented:
Now the search is not working at the root level too. AAM settings,host header and bindings all seems to be correct. If any of those are changed then either the site becomes inaccessible or search stop functioning. Please help..
Mohit NairSenior AssociateAuthor Commented:
This issue has been fixed now.Problem was that the cross domain users belong to Win 2003 functional level. So Search service account need to be added on the following group
Windows Authorization Access group and PreWindows 2000 group.
Mohit NairSenior AssociateAuthor Commented:
This is the only way if there is a two way trust and still search doesnt work for cross domain users.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now