[Last Call] Learn about multicloud storage options and how to improve your company's cloud strategy. Register Now

x
?
Solved

Sharepoint 2010 Public access

Posted on 2014-01-09
6
Medium Priority
?
510 Views
Last Modified: 2014-01-10
The main question:

How do I make my Sharepoint 2010 website available publicly through an established sub-domain using port 80?

Ok, some of the basic info first:

The site is up and running on a custom port (41472). When I go to http://sub.domain.com:41472, I can successfully see the site, log in and work on it, no issues there. DNS is pointing in the right direction and all, but when I've attempted to configure Sharepoint 2010 and IIS to listen on port 80, I can't get in from the Internet. However, Internally, port 80 works fine, I can type the server name and the Sharepoint site loads, so my suspicion is that the problem lies on the IIS side.

Here's what I've done:

* I've extended the Sharepoint site in the Internet zone and chosen port 80, creating a new IIS site in the process.
* I've added the public URL in the "Edit Public URLs" section of Sharepoint 2010 Application Management
* I've added port 80 bindings in IIS for the new IIS website created by Sharepoint's extension.

Suggestions would be greatly appreciated!

Thanks,

ArgTech
0
Comment
Question by:ArgTech
[X]
Welcome to Experts Exchange

Add your voice to the tech community where 5M+ people just like you are talking about what matters.

  • Help others & share knowledge
  • Earn cash & points
  • Learn & ask questions
  • 3
  • 3
6 Comments
 
LVL 38

Expert Comment

by:Justin Smith
ID: 39769963
Sounds like a DNS issue.  You need to add an entry to your PUBLIC DNS to point your URL to your router.  Your other steps sound correct.
0
 

Author Comment

by:ArgTech
ID: 39770939
The DNS record is created. I can access the site by using the public IP and subdomain through the custom port, but not 80. In other words:

Externally:

http://sub.domain.com:41472  -  Successful
http://99.99.99.99:41472  -  Successful
http://sub.domain.com  -  Unsuccessful
http://99.99.99.99  -  Unsuccessful

Internally:

http://servername:41472 - Successful
http://servername - Successful

That leads me to believe it's an IIS issue. Port 80 is working internally, but not externally. DNS is properly forwarding the subdomain to the right IP, but only works when specifying the port.
0
 
LVL 38

Expert Comment

by:Justin Smith
ID: 39770972
SharePoint and IIS doesn't care whether the user is coming "internally" or "externally".  As long as a request is made on the port for a binded URL, the content will be served.

From your list of URL's above it doesn't look like you are trying the exact same thing.  Externally you are trying to use sub.domain.com.  Internally you are using servername.  Is this correct?

Can you verify your extended site in IIS has the binding on port 80 for sub.domain.com?
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 

Author Comment

by:ArgTech
ID: 39771006
That's correct. I tried the server name internally just to test the functionality of port 80. I could use the subdomain address as well if needed, and ideally will use it exclusively once I can get it to respond. I just had another suggestion to forward port 80 on the firewall, and it makes a lot of sense. I'll try that and get back to you. Thanks for the help so far.
0
 
LVL 38

Accepted Solution

by:
Justin Smith earned 2000 total points
ID: 39771022
Yes friend, port 80 traffic needs to get to the server or its never going to work.
0
 

Author Comment

by:ArgTech
ID: 39771075
That did it! :)
0

Featured Post

New feature and membership benefit!

New feature! Upgrade and increase expert visibility of your issues with Priority Questions.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Running classic asp applications under Windows Server 2008 R2 (x64) and IIS 7 is not as easy as one may think. It took me a while to figure it out while getting error 8002801d a few times. After you install the OS you will need to install the fol…
A recent project that involved parsing Tableau Desktop and Server log files to extract reusable user queries for use in other systems. I chose to use PowerShell to gather the data, and SharePoint to present it...
Video by: ITPro.TV
In this episode Don builds upon the troubleshooting techniques by demonstrating how to properly monitor a vSphere deployment to detect problems before they occur. He begins the show using tools found within the vSphere suite as ends the show demonst…
In this video you will find out how to export Office 365 mailboxes using the built in eDiscovery tool. Bear in mind that although this method might be useful in some cases, using PST files as Office 365 backup is troublesome in a long run (more on t…

650 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question