Sharepoint 2010 Public access
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
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
Justin Smith
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.
ASKER
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.
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.
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?
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?
ASKER
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.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
That did it! :)