The URL of a Web request received by Internet Information Services (IIS) is not the same as the URL that was typed by an end user.

Internal URL refers to the URL of a Web Request as it is received by Windows SharePoint Services 3.0.

Public URL refers to the URL of an externally accessible Web Site.

IP Address:191.121.2.104

Kerio Firewall:

Port Translation from 9000 to 80.

When you access http://moodle.vanarts.com:9000/, it returns an error. Please pay attention to address: moodle.vanarts.com/default.aspx.

Because of the firewall configuration, the received URL of SharePoint is http://moodle.vanarts.com.

Solution:

Define an Alternate Access Mapping

Add an Internal URLs to Zone:Internet

How about to access the SharePoint by Firewall's IP Address 96.53.44.214:9000?

Add another Internal URL to the Internet zone

localhost

If you want the http://localhost to reach the sharepoint application, you have to add Internal URL http://localhost to one of the five zones.

In this special case, you cannot define the Internal URL http://localhost to Internet zone because of the Public URL http://moodle.vanarts.com:9000. When you access http://localhost, the SharePoint returns http://moodle.vanarts.com:9000.

If host file includes entry:

127.0.0.1 server2003.vanarts.com

you can define a Public URL in Intranet zone.

Accessing SharePoint application by http://share.vanarts.com both internally and externally

We can have maximum of five public URLs because there are five zones (default, Intranet, Internet, Custom, and Extranet). Each zone can have many Internal URLs.

Host-named site collections cannot use alternate access mappings. Host-named site collections are automatically considered to be in the Default zone, and the URL of the request must not be modified between the end user and the server.

If you want both me.com and www.me.com accessible, you must set up host headers in IIS as shown below:

Extend Web Application

When you manually add an alternate access mapping, you must manually modify the host header bindings in the IIS Web Site from the IIS Manager. It is not recommended. Any changes in IIS manager will not be recorded in the configuration database of the farm. If you want to create a new zone with an alternate access mapping, it is best to EXTEND WEB APPLICATION. However, to add an additional internal URL, for example, http://localhost, http://127.0.0.1, or http://192.168.0.1, etc. you have to manually add it through Alternate Access Mapping interface.

When Extending "SharePoint - 80" web application with a host header http://k2.carteasy.com, the IIS Web Site is automatically created with the host header http://k2.carteasy.com.

When you extend a Web Application, don't choose the existing IIS site. It is better to create a new IIS site. There is no side effect to remove the extended web application.

When accessing the Web Site through http://k2.carteasy.com, "Anonymous Access" will apply.

http://k2/

If you manually add an Alternate Access Mapping for http://k2.carteasy.com/, the Anonymous Access feature cannot be achieved.

If you create the Web Application with Claims Based Authentication, each zone can have a different authentication provider. The Default Zone uses "Windows"; the Intranet zone uses Forms Based; the Internet zone uses SAML Provider. The best solution for Claims Based Authentication is to set up the Default zone with Windows, Forms Based, and SAML Provider.

Title Graphic

The default Title Graphic is

C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\images\titlegraphic.gif

Change the site logo:

copy vanarts.jpg to C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\12\template\images\

http://server2003/default.aspx

Site Actions--Site Settings

Look and Feel

Title, description, and icon

Title:Vancouver Institute of Media Arts
URL: /_layouts/images/vanarts.jpg