Logo 
Search:

Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Wierd Sharepoint problem

  Asked By: Hiral    Date: Feb 09    Category: Sharepoint    Views: 591

my sharpoint servers

XXintranet01 (web server)
XXintranet02 (sql)
XXintranet03 (web server, search server) (use dedicated front end selected)

in the hosts file there is an entry among others that says:


172.22.17.47 bcvaintranet01 # Added by Office SharePoint Server Search
(12/12/2008 1:58 AM)



the problem is that bcvaintranet03's ip address is .47

does anyone know where sharepoint read's the list that it imprints in the hosts
file?

is it from alternate access mappings?

or is it from search. I know that this is a search thing cause if you use all
front ends the hosts file is not written.

Share: 

 

2 Answers Found

 
Answer #1    Answered By: Alice Chandler     Answered On: Feb 09

The host file  entry typically comes from having set a specific WFE for
crawling.

 
Answer #2    Answered By: Lynette Sawyer     Answered On: Feb 09

I'd bet big money on that. The best way to handle this is to tell your
Indexer to use all servers (it's pointing to XXintranet03 right now)
then manually edit hour Hosts file  to point bcvaintranet01 at the IP
address of the WFE you want to be crawled. If you change it without
setting your Indexer to "use all servers" then it will correct the Hosts
file after you change it.

Also beware that since this change is at the IP level, all IP
communications will get this change. If you have a machine named
'bcvaintranet01' then your Indexer will always use the IP address you
specify, not its actual IP address. I've seen this be a problem  for file
copying. On the indexer you type \\bcvaintranet01\sharename
<file:///\\bcvaintranet01\sharename> but you're actually going to the
WFE you specified in the Hosts file. Just something to be aware of when
your farm URL is not a FQDN.

 
Didn't find what you were looking for? Find more on Wierd Sharepoint problem Or get search suggestion and latest updates.




Tagged: