Maybe you are running into a loopback authentication issue. This will happen if content is accessed from a server to the same server using an alternate DNS name. For example:
- Server name: srvSP2010wfe
- Portal URL pointing to server (1.): http://portal
- DNS config: portal A IP.OF.Server.1
The resolution is described here:
The article is mentioning two methods:
Method 1 is setting the Key to disable the LoopBackCheck in general. This is considered less secure, but in real life it is easier during debugging the problem.
Maybe you can disable it and if the solution works i would suggest to use the back connections host method to fix the problem.
Method 2 is setting a multi-string value. The string must contain all url's + FQDN (portal and portal.domain.local) that are not the machines hostname. Using this method is more secure because only selected url's are excluded from the loopback check. During debugging in a complicated setup this is harder to get right if you hit this for the first time.
After configuring the needed method to successfully run through the loopback check the index on the local machine should be able to access the content if the content access account has the needed privileges.
More info's on configuring the default access account are here: