SharePoint Stack Exchange is a question and answer site for SharePoint enthusiasts. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I have a issue today with regards to Alternate access mappings.

My Intranet has two Access mappings as follow:

Internal URL              Zone       Public URL for Zone
http://servername         Default    http://servername    Intranet

The Intranet zone above is a DNS friendly name which routes to the server.

Everything seems to be working fine except Sharepiont logs on a daily basis a lot of Warnings which looks like this:

Alternate access mappings have not been configured. Users or services are accessing the site http://servername with the URL

Note the part is different every time.

Is this something to worry about? How do I get rid of it? I can't disable the internal mapping as I have a application which struggles with resolving DNS and needs to connect to the Internal serer name directly.

share|improve this question
We are glad you like our design, but please keep comments like that on our meta site to keep questions as straight forward and readable as possiblel thanx :-) – Anders Rask Sep 19 '11 at 8:00
No problems, thanks Anders – Fox Sep 19 '11 at 8:06
We have the same thing on our production machine but it turns out that this is due to a monitoring tool that is accessing URL's on the site that do not exist. So these URL's make it into the ULS log. – MichaelF Sep 19 '11 at 12:52
Are you by chance using Google Analytics on the environment? – webdes03 Sep 26 '11 at 19:26
@webdes03 Yes we are, but those URL's don't seem to be showing up in our logs. What we get are IP addresses that are from a monitoring tool the hosting environment set up, then removed. Although incompletely as I discovered. – MichaelF Mar 12 '12 at 14:36

It sounds like SharePoint is getting requests for other websites routed to its IIS server. Remember that an HTTP request has an IP and a host associated with it. The request has the server's IP so IIS dutifully processes it, but there's no host header mapped to the URL being sent, so SP just kinda stares at it and goes "HUH?!"

I may be WAY off the mark on this, but my gut reaction is that one or more of your machines has a proxy configured to point to that server. That would cause the affected client machines to try to use the SP server to relay traffic to Google, MSN, etc. through the SP server and result in the odd hostnames in the logs. This is just a guess, but it's the first thing that comes to mind to me.

share|improve this answer

There may also be a rogue/infected machine on your network. Your network team should be able to look at your IIS logs and tell you where those requests are originating and take the steps necessary to resolve it. For the short term, however, you can go into IIS on your SharePoint farm and simply have it only listen on the host-headers you are aware of rather than all of port 80.

This is not an ideal solution but it will limit any inbound requests to your SharePoint environment to only those URLs you are expecting.

share|improve this answer

Do you have configured bindings for your web application in IIS? It must contain information about all addresses from Alternate Access mapping.

share|improve this answer

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.