Comments on: How can I publish my sharepoint site to be able to access it from the internet http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-publish-my-sharepoint-site-to-be-able-to-access-it-from-the-internet/ Sun, 26 May 2013 01:40:27 +0000 hourly 1 By: kingriggins http://itknowledgeexchange.techtarget.com/itanswers/how-can-i-publish-my-sharepoint-site-to-be-able-to-access-it-from-the-internet/#comment-66608 kingriggins Fri, 07 Aug 2009 13:31:13 +0000 #comment-66608 You did bring up a good point. I think I’ll have two different sharepoint sites. One for use by company employees that can access via VPN outside of the network, and the other site for customers and vendors to have access. Believe me, security is the main priority when setting this up. I’m in test mode right now.

Our router is a Linksys RV042. Here are a few more details:
204.xxx.xxx.xxx – Web Hosting
70.xxx.xxx.xxx – Wan IP for our Router
10.xxx.xxx.xxx – Internal Private Network Scheme

Inside our web hosting configuration we have setup mail.mycompany.com to be forwarded to the WAN IP of our router. Inside the router settings we have port forwarding setup for email ports 110,25, & 143 to point to our email server 10.xxx.xxx.3 (which is also our DNS server for our private network). This allows access to email over the internet.

My idea was to create an entry on our hosting configuration for sharepoint.mycompany.com to be forwarded to the WAN IP address of our router. The router already forwards all TCP traffic for port 80 to our DNS server 10.xxx.xxx.3. Inside the DNS settings of our DNS server on our private network I created a host entry for sharepoint.mycompany.com to point to the server that has our sharepoint site 10.xxx.xxx.7. When I try accessing sharepoint.mycompany.com from outside the network, I get an “under construction” default page.

I have tried extended the web application within sharepoint and using a different port number. Inside our router I set up port forwarding for the new port number to point directly to the sharepoint server 10.xxx.xxx.7. That hasn’t worked either.

I hope I have provided enough detail. It seems like it has to be something simple that I’m leaving out.

]]>