Deployment Tasks

The chapter organizes this procedure into multiple sections according to the tasks in the following list. Optional tasks are labeled as such.

• Configure proxy settings on the server. Configure the proxy setting on the SharePoint Portal Server computer.
• DNS entry creation. Create a Domain Name System (DNS) entry.
• Web Site creation. Create a new Web site in Internet Information Services (IIS).
• Enable Web discussions. Enable discussions on the new Web site.
• Modify security settings. Modify the security settings on the new Web site.
• Configure proxy server settings. Configure the proxy server settings.
• Extranet testing from the Intranet. Test the extranet from the intranet.
• Extranet testing from the Internet. Test the extranet from the Internet.
• E-mail notifications. Specify the server URL to use in e-mail notifications.
• Secure Sockets Layer. Optionally, enable Secure Sockets Layer (SSL).
• Internal FQDN mapping. Optionally, specify an internal Fully Qualified Domain Name (FQDN) for the SharePoint Portal Server computer.
• Settings for crawling Web sites on the Internet. Optionally, enable SharePoint Portal Server to crawl sites on the Internet.
• Settings for crawling another SharePoint Portal Server site on the Internet. Optionally, enable SharePoint Portal Server to crawl another SharePoint Portal Server computer across the Internet.

In addition to the tasks specified previously, the following sections are provided:

• Troubleshooting. Includes information to assist you in diagnosing any configuration problems.
• Extranet features. Describes SharePoint Portal Server featuresavailable when you deploy the server across an extranet.

Understanding Key Terms

This chapter uses following terms:

• NetBIOS name. The network basic input/output system (NetBIOS) name is the computer name of your server. You can find the computer name on the Properties page of My Computer. Right-click My Computer, and then click Properties. On the Network Identification tab, click Properties. You can view the computer name of the server in Computer name. In this chapter, examples use a NetBIOS name of AdvWks.
• Internal domain name. The internal domain name is the domain name you use on your intranet. It can be the same as the external domain name, or it can be different. In this chapter, examples use an internal domain name of corp.adventure-works.com.
• Internal Fully Qualified Domain Name (FQDN). The internal FQDN is the name you want to use for the server on your intranet. It is in the form NetBIOS_name.internal_domain_name. Users must use the internal FQDN to access the server if you do not enable your network for Microsoft Windows^® Internet Name Service (WINS) resolution, or if you do not configure the Domain Name System (DNS) to support NetBIOS throughout the domain. In this chapter, examples use an intranet FQDN of AdvWks.corp.adventure-works.com.
• External server name. The external server name (host name) is the name you use for the server on the extranet. If your internal and external domain names are the same, the external server name must be different from the NetBIOS name. Add this name to the external domain name to form the external FQDN. In this chapter, examples use an external server name of AdventureWorks.
• External domain name. The external domain name is the domain name you use on the extranet. It can be the same as the internal domain name, or it can be different. In this chapter, examples use an external domain name of adventure-works.com.
• External FQDN. The external FQDN is in the form external_server_name.external_domain_name. In this chapter, examples use an external FQDN of AdventureWorks.adventure-works.com.

Internal and external FQDNs must be unique, as described here:

• If the internal and external domain names are the same, for example, adventure-works.com, the external server name must differ from the NetBIOS name. For example, you could have AdventureWorks.adventure-works.com and AdvWks.adventure-works.com as the external and internal FQDNs, respectively.
• If the internal and external domain names are different, the external server name can be the same as the NetBIOS name. For example, you could have AdvWks.adventure-works.com and AdvWks.corp.adventure-works.com as the external and internal FQDNs, respectively.

Accessing SharePoint Portal Server

The following table shows different ways to access a workspace on your SharePoint Portal Server computer. Examples use a workspace name of Marketing.

Workspace Access Points

To access by	Use
NetBIOS (computer name for the server)	http://server_name/workspace_name This is the way that you access SharePoint Portal Server out of the box.Example http://AdvWks/Marketing to access the workspace
Internal FQDN	http://NetBIOS_name.internal_domain_name/workspace_name Example http://AdvWks.corp.adventure-works.com/Marketing
External FQDN	http://external_server_name.external_domain_name/ workspace_nameExample http://AdventureWorks.adventure- works.com/Marketing
Internet Protocol (IP) address and port	Important You cannot access the SharePoint Portal Server computer by typing its Internet Protocol (IP) address and port number. For example, you cannot use http://10.0.0.X/workspace_name or http://10.0.0.X:8080/workspace_name.