I did the following on Windows 2008 IIS.
- Install SharePoint to port 80 (in my case as the non-default website)
- Open Manage network connections (ncpa.cpl from run)
- For your network connection go into properties
- Go into IPv4 properties
- Assumtion is that you already have it set to Static IP address
- Click Advanced
- Click add and add in another unused IP address (ex: 192.168.1.100 for main and add in 192.168.1.101)
- Ok out
- In IIS click the default website
- On the right side click Bindings
- Edit and change the IP address from * to the main IP address (192.168.1.100 in our example)
- Okay out
- Click the new Sharepoint site (Default name is SharePoint - 80)
- Click Bindings and change IP address to the secondary IP (ex 192.168.1.101)
From here you can access the original website normally and the Sharepoint site via the new IP address. This brings up some new issues though...
DNS Entry to make the site "friendly"
- Open your domain DNS and add a new Host (A). Make the Name what you want your users to type in to reach the site, then enter the second ip address (SharePoint site address)
- Try to ping the name you just entered. It should pingback as the ip address you just set.
- Try to navigate to the site (ex: http://example/)
Next issue... Authentication loopback check doesn't like this setup much. At this point you'll find that credentials fail. After a lot of searching I found the solution here: http://blogs.bluethreadinc.com/thellebuyck/archive/2008/10/30/401.1-error-when-accessing-sharepoint-from-server.aspx
- Click Start, click Run, type regedit, and then click OK
- Locate and then click the following registry subkey: 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
- Exit Registry Editor
- Restart the computer.
Note that the auther includes the following: "The security is reduced when you disable the authentication loopback check, and you open the Windows Server 2003 server for man-in-the-middle (MITM) attacks on NTLM."
No comments:
Post a Comment