1

Hello everyone. I just installed Sharepoint 2013 (SQL Server 2012 SP1) on a Server 2008 R2 VM. I have created a new web app and new site collection linked to the web app. Both are associated with http://sharepoint . I cannot access the site from the http://sharepoint address on anything. I’ve tried the local server (SV2), the DC (and VM host), or a workstation on the domain. I have the firewall ports open for SQL and Sharepoint, but I even went as far a making sure :80 was completely open. Looking in IIS, the website is started. The weird thing is I’m able to access the Sharepoint Central Admin from all computers.

To claify, when accessing the webpage, it cannot be found/viewed, it does not appear to be an access issue.

What could be causing this issue? Is there a setting I’ve missed somewhere?

4 Spice ups
2

Have you tried the hostname or IP ?

3

For reference, have you seen this guide on TechNet?

4

I’ve tried both. Browsing to just the IP address will bring up the IIS default page. Disabling that will just bring up “not found”. I tried http://sharepoint.domain with the same unable to view issue. I’ve tried editing the IIS website configs in pretty much every possible config and haven’t found any change. What really confuses me is that I’m able to access the Central Admin, even from another system, which tells me it should be configured fine. I’ve even tried deleting the web app and site and re-creating.

I haven’t seen that guide, but I used a very similar one with the installation/first config.

5

From your original post you listed the SharePoint server as SV2 which I assume has a DNS entry in your local network. You have created a website (the SharePoint app) as sharepoint but probably have no DNS resolution for that host name in you local DNS. If you ping sharepoint is will assume you get no response.

Create another A record (not a cname or alias) in DNS with sharepoint as the host name and the IP address of the SV2 server. The reason you can get to CA is that the CA host name is probably SV2:xxxxx (some port number) which has a DNS entry.

Hope that helps.

1 Spice up
6

Sorry, I should have also put that. I did have a DNS entry for http://sharepoint going to the SV2 IP. Afterwards, it would act the same as navigating directly to the IP, showing either the default IIS7 page, or “not found”.

7

Could you post a link to the guide you are using?

8

http://consultingblogs.emc.com/randyrempel/archive/2013/03/17/installing-and-configuring-sharepoint-2013-part-4-of-4.aspx

9

The default IIS web site should be stopped. Also check the SharePoint web app you created is pointing to port 80.

If you are trying to connect as the farm admin on the SP Server you might also check the loopback check per this excerpt from an MSDN post. Although this will not explain other stations no connecting.

Method 2: Disable the authentication loopback check
Re-enable the behavior that exists in Windows Server 2003 by setting the DisableLoopbackCheck registry entry in the
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa registry
subkey to 1. To set the DisableLoopbackCheck registry entry to 1, follow these steps on the client computer: 1.Click Start, click Run, type regedit, and then click OK.
2.Locate and then click the following registry subkey: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
3.Right-click Lsa, point to New, and then click DWORD Value.
4.Type DisableLoopbackCheck, and then press ENTER.
5.Right-click DisableLoopbackCheck, and then click Modify.
6.In the Value data box, type 1, and then click OK.
7.Exit Registry Editor.
8.Restart the computer.

1 Spice up
10

The default IIS is stopped. I even went as far as deleting it with no change. The sharepoint site config is pointing to port 80. I’ve tried using “sharepoint” as the host, I’ve tried using the IP address with a blank host. No change. The actual error is as if the page didn’t exist. “Page cannot be found”, “Something has happened”, “not found”. It doesn’t prompt for a login at all. I am logged into the Server as SP_admin, which has local admin rights.

11

Could you please post a link to the instructions you referenced you were using earlier?

Edit, now I am seeing the link you posted, did not see the link at the time ^ was said.

12

Just to give an update, I got the issue resolved. Here’s what I did:

I deleted the web app (and site collection), and all newly created App Pools
Re-made the Web App using the Sharepoint Central Administration, made new App Pool
Re-made site collection
Went into IIS settings and verified the new site was in there and active
Went into the Application pools and the app pool was NOT started, started app pool
The other sharepoint site wasn’t started either (not the Central Admin), so I started that, though I’m not sure if that had anything to do with it.

That seemed to fix it… so I’m not sure if it was an original config setting, or if it was an IIS site not enabled, but everything is working now.