SharePoint 2013 Fondation Frustration

Hello Experts,

I have a vanilla installation of SharePoint 2013 Foundation on a Windows Server 2012 VM.  I'm not an IIS expert or a SharePoint expert but I can't imagine it is this difficult to bring up a team site.  The server is only doing SharePoint and has one IP address, no other web sites so I didn't mess with the bindings in IIS  - everything is vanilla.

I'm using a second server for the databases. It's a 2012 machine with MS SQL 2012.  I was also able to create a site collection (team site).

It isn't possible to connect to the site either locally or remotely using the host name or the IP address.  The host name resolves in DNS okay so I don't think that's the issue.

Any ideas are very welcome....and please don't be afraid to make me feel stupid.
LVL 1
cambo84Asked:
Who is Participating?
 
Rainer JeschorConnect With a Mentor Commented:
Hi,
what result do you get?

How does Central Administration for this web app look alike?
What is the configured default/standard address for the web application?
How does IIS look alike?
What type/kind of authentication did you select?
Anything in the IIS logs for this web app/site?
Does the site shows up in IIS manager as "Running"?
Any error in the Windows Event log?
Any error in the SharePoint ULS log?

Thanks
Rainer
0
 
cambo84Author Commented:
Hi Rainer,

It turned out to be alternate access mappings but since your questions forced me to dig into the IIS logs a little deeper, I'll give you full credit here.

Thanks very much.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.