Change routing of website on a sharepoint server

Hello,

we have an internal sharepoint server website, which is reachable via public IP from outsite. The Sharepoint itself server has a private IP.

URL of website: https://server1.com/default.aspx.

So when I'm working on the machine and enter the above website on the local Sharepoint Server, I will be forwarded to extern first and then, because of the .com DNS resolution, I'm being routed back to our network again.

According to Microsoft technet articles how to upgrade Sharepoint 2010 to 2013, I created a virtualized environment with an internal network only with DC, SQL and Sharepoint Server - so no access to the internet.

Now I cannot enter the above website now, because due the webite has a .com in the URL, my DNS try forward this request to external - without success.

My question is now:
How can I adjust the routing on the local Sharepoint server in that way that I'm not being routed to the internet but directly to the local webserver and can open the website properly?

Regards

insi01
insi01Asked:
Who is Participating?

Improve company productivity with a Business Account.Sign Up

x
 
Justin SmithConnect With a Mentor Sr. System EngineerCommented:
You need an AAM to match the URL you are using, and you need an IIS Binding to match the URL you are using.
0
 
Justin SmithSr. System EngineerCommented:
Add a HOSTS file entry.  On the SharePoint server open C:\Windows\System32\Drivers\ETC.  Edit the HOSTS file and add an entry at the bottom that looks like:

127.0.0.1     server1.com


This tells your machine to stay local when visiting that domain.

If you get prompted several times for user/password and it won't accept, you'll need to disable loopback check by doing the following:

Click Start, click Run, type regedit, and then click OK.
In Registry Editor, locate and then click the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa
Right-click Lsa, point to New, and then click DWORD Value.
Type DisableLoopbackCheck, and then press ENTER.
Right-click DisableLoopbackCheck, and then click Modify.
In the Value data box, type 1, and then click OK.
0
 
Rainer JeschorConnect With a Mentor Commented:
Hi,
I agree with ACH1LLES for the hosts file update but I would never ever recommend to disable the DisableLoopbackCheck completely BUT instead setting a set of allowed names through the reg key BackConnectionHostnames.

See this solution: http://www.experts-exchange.com/OS/Microsoft_Operating_Systems/Server/MS-SharePoint/Q_27819495.html
(referencing both the MS KB entry http://support.microsoft.com/kb/896861
and this blog post:
http://blogs.technet.com/b/sharepoint_foxhole/archive/2010/06/21/disableloopbackcheck-lets-do-it-the-right-way.aspx)

HTH
Rainer
0
The 14th Annual Expert Award Winners

The results are in! Meet the top members of our 2017 Expert Awards. Congratulations to all who qualified!

 
Justin SmithSr. System EngineerCommented:
Disabling loopback entirely is quite appropriate in this situation, and 95% of all situations.
0
 
insi01Author Commented:
Hello,

I have tried, but doesn't work. Procedure is also valid for https sites?

The loopback check was already configured.
0
 
Justin SmithSr. System EngineerCommented:
Yes procedure is valid for https.  When you ping your URL, are you getting the 127 address?
0
 
insi01Author Commented:
I ping the url and get the 127 address.

Still cannot reach the website.

Any Idea? Do I have something to change within AAM or any binding settings?
0
 
insi01Author Commented:
Ok, will try tomorrow.
0
 
insi01Author Commented:
Sorry guys, but this all didn't help.
0
 
Justin SmithSr. System EngineerCommented:
Please send screenshots of IIS bindings and AAM.  If you don't want to post here you can email justinsmith317@Yahoo.com.
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.