16.01.2013 Views

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

Microsoft Sharepoint Products and Technologies Resource Kit eBook

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Chapter 25: Firewall Considerations for SharePoint Portal Server Deployments 685<br />

Testing SSL Bridging Configuration<br />

Before you go any further, you need to test your SSL bridging configuration. On an<br />

external computer that is not connected to your network, start Internet Explorer <strong>and</strong><br />

type in https://. In our example, we would open https://external.contoso.com.<br />

A security alert might appear because the certificate of the root<br />

CA that issued the portal site certificate is not installed on the external client’s<br />

machine. If the security alert appears, click Yes to proceed. Because the SharePoint<br />

site is set up to support Basic authentication, you should see the credentials dialog<br />

box. Enter your credentials, <strong>and</strong> you should be able to see the portal site’s home<br />

page.<br />

If an error message—specifically, “500 Internal Server Error”—is returned to<br />

the browser, you might need to reconfigure the Web publishing rule. The reason this<br />

error might occur is the difference between the common name in the certificate <strong>and</strong><br />

the name of the server in the Web publishing rule where the requests are redirected.<br />

The common name in the certificate is the external FQDN, whereas the name of the<br />

server in the Web publishing rule is the server internal name. In our example, the<br />

common name is external.contoso.com <strong>and</strong> the internal name is internal. The<br />

workaround is to use the external FQDN for the name of the server the requests are<br />

redirected to.<br />

To change the name, go to the Web publishing rule Properties, click the Action<br />

tab, <strong>and</strong> in the Redirect The Request To This Internal Web Server (Name Or IP<br />

Address) box, type external FQDN. However, for this configuration to work, ISA<br />

Server must be able to resolve the external FQDN to the internal IP address of the<br />

SharePoint site—in our example, 192.168.1.1. To enable this name resolution, you<br />

can create a hosts file entry that maps the FQDN to an internal IP address. The solution<br />

is either to set up a split DNS or to add an entry to the hosts file on the ISA<br />

Server computer. For instructions on how to set up a split DNS, refer to Chapter13.<br />

If you want to use the hosts file, add a line to it with an external FQDN <strong>and</strong> an internal<br />

IP address—for example: 192.168.1.1 external.contoso.com<br />

Note The hosts file is located in the %SystemRoot%\System32\Drivers\Etc<br />

folder on the ISA Server computer.<br />

Configuring Link Translation<br />

Using link translation on an ISA Server addresses several problems that external<br />

users might encounter when connecting to an internal SharePoint site through a firewall.<br />

Link translation is implemented as a Web application filter that is installed in<br />

Feature Pack 1 for ISA Server 2000. By default, this filter is disabled.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!