Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Sharepoint 2003 indexing service

Status
Not open for further replies.

kholio

Technical User
Aug 1, 2004
1
QA

I have a problem with the index server in this
sharepoint deployment scenario :

I have 5 servers :

2 web front end servers
1 index server
2 sql servers

the database servers are in a DMZ ( different network )
all servers are using a corporate internal DNS server on
active directory server .

but when i try to crawl the portal site and index the
information in database the crawling stops after only 2
seconds like it cant access any information on the
database server .

what is possible to be wrong in the deployment .

im using a pix firewall between two networks .

looking to hear from any body soon .

bye ,
khalil .
 
I am by far no expert, but what you may want to try to do is instead of going against the DNS name try and go against a single server. You will find that SharePoint indexes this. This problem is what actually brings me to these forums. I have tried to get sharepoint to crawl using the DNS but it can't because it is denied access. It seems as though SharePoint cannot authenticate to my load balancer. Any solution to this would be appreciated.

If you do index 1 server your index will work even if that server goes down, however all of your links still reference 1 server. We were looking at creating a code which will change the index results to the DNS name so that if that particular web server goes down then we will still be OK, but this is no solution, Microsoft should look into this.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top