Unable to load SharePoint web application on port 80 in a dev domain without internet access

  • Article

While working in a dev domain that does not have access to the internet, I ran into the following issue with loading SharePoint web application hosted on port 80:

  • After creating a new web application on port 80 and a new root site collection, I was unable to access the site. When the users hit the site, they are presented with credential prompts. Because the users are in a domain that does not have internet access, users cannot access the site.
  • From event viewer, you may also see the following warning:

Alternate access mappings have not been configured. Users or services are accessing the site https://abc with the URL https://crl.microsoft.com. This may cause incorrect links to be stored or returned to users. If this is expected, add the URL https://crl.microsoft.com as an AAM response URL.

  • After searching online, here are a few things I tried to make it work:
    • add the following to the machine.config as follows: 
      • C:\Windows\Microsoft.NET\Framework64\v2.0.50727\CONFIG\machine.config
      • <configuration>
         <runtime>
          <generatePublisherEvidence enabled="false"/>
         </runtime>
        </configuration>
    • add the following to the hosts file:
      • 127.0.0.1     crl.microsoft.com

Comments

  • Anonymous
    March 01, 2012
    I am not sure that advice is correct.  We have a dev domain with no internet access but I have not experienced that particular problem. You can disable the "check for publisher’s certificate revocation" in Internet Explorer under Internet Options | Advanced | Security.  I would also add the Sharepoint URL to the Local Intranet Zone. Thoughts?

  • Anonymous
    March 06, 2012
    Thanks Wes! Unfortunately, the IE security option is not available in the Dev environment as it is locked down by GPO. This behavior only occurs on the web app on port 80, as other web apps are fine. I have not been able to find the root cause, but the above steps seem to have fixed the issue.

  • Anonymous
    July 25, 2012
    would you please help indicate where to add the content below? any column of the machine.config file? <configuration> <runtime>  <generatePublisherEvidence enabled="false"/> </runtime> </configuration