Installing IIS on Windows XP

Installing IIS on Windows XP Pro

If you are running Windows XP Professional on your computer you can install Microsoft's web server, Internet Information Server 5.1 (IIS) for free from the Windows XP Pro installation CD and configure it to run on your system by following the instructions below: -

1. Place the Windows XP Professional CD-Rom into your CD-Rom Drive.

2. Open 'Add/Remove Windows Components' found in 'Add/Remove Programs' in the 'Control Panel'.

3. Place a tick in the check box for 'Internet Information Services (IIS)' leaving all the default installation settings intact.

4. Once IIS is installed on your machine you can view your home page in a web browser by typing 'http://localhost' (you can substitute 'localhost' for the name of your computer) into the address bar of your web browser. If you have not placed your website into the default directory you should now be looking at the IIS documentation.

5. If you are not sure of the name of your computer right-click on the 'My Computer' icon on your desktop, select 'Properties' from the shortcut menu, and click on the 'Computer Name' tab.

6. Your default web directory to place your website in is 'C:\Inetpub\wwwroot', but if you don't want to over write the IIS documentation found in this directory you can set up your own virtual directory through the 'Internet Information Services' console.

7. The 'Internet Information Services' console can be found in the 'Administration Tools' in the 'Control Panel' under 'Performance and Maintenance', if you do not have the control panel in Classic View.

8. Double-click on the 'Internet Information Services' icon.

8. Once the 'Internet Information Services' console is open you will see any IIS web services you have running on your machine including the SMTP server and FTP server, if you chose to install them with IIS.

9. To add a new virtual directory right click on 'Default Website' and select 'New', followed by 'Virtual Directory', from the drop down list.

7. Next you will see the 'Virtual Directory Creation Wizard' from the first screen click the 'next' button.

9. You will then be asked to type in an 'Alias' by which you will access the virtual directory from your web browser (this is the name you will type into your web browser after 'localhost' to view any web pages you place in the directory).

10. Next you will see a 'Browse...' button, click on this to select the directory your website pages are in on your computer, after which click on the 'next' button to continue.

11. On the final part of the wizard you will see a series of boxes, if you are not worried about security then select them all, if you are and want to run ASP scripts then check the first two, followed by the 'next' button.

12. Once the virtual directory is created you can view the web pages in the folder by typing 'http://localhost/aliasName' (where 'aliasName' is, place the alias you called the virtual directory) into the address bar of your web browser (you can substitute 'localhost' for the name of your computer if you wish).

Free Web Apps for Windows XP IIS

Now that you have installed IIS on your Windows XP computer you may want to try running some Free Web Applications on it.

Here at Web Wiz we have a number of free Web Apps for IIS available for you to run, including Forums, Blogs, eNewsletter, Rich Text Editor and others. Have a look at the links below for more information.

ISA Server 2006, ISA Server 2004 & client connections from Outlook 2003 to Exchange Server 2003

How to configure ISA Server 2006, ISA Server 2004, or Microsoft Forefront Threat Management Gateway, Medium Business Edition, to allow for RPC over HTTP client connections from Outlook 2003 to Exchange Server 2003

This step-by-step article describes how to configure Microsoft Internet Security and Acceleration (ISA) Server 2006, ISA Server 2004, or Microsoft Forefront Threat Management Gateway, Medium Business Edition, so that Remote Procedure Call (RPC) over HTTP client connections can pass from Microsoft Office Outlook 2003 to Microsoft Exchange Server 2003. The RPC over HTTP feature makes it possible for remote client computers that are running Microsoft Windows Server 2003, Microsoft Windows XP Service Pack 1, or later versions of Microsoft Windows, to connect to an Exchange server without the need for a virtual private network (VPN) connection. You can configure the RPC over HTTP traffic to be sent through an ISA Server-based or Forefront Threat Management Gateway-based computer on your network by creating a Secure Sockets Layer (SSL) Web Publishing rule on the ISA Server-based computer.

Note You must confirm that RPC over HTTP traffic is functioning correctly on the Exchange server before you configure RPC over HTTP traffic to pass through the ISA Server-based computer. For more information about how to deploy Exchange Server 2003 RPC over HTTP, click the following article numbers to view the articles in the Microsoft Knowledge Base:

840255  (http://support.microsoft.com/kb/840255/ ) The "Exchange Server 2003 RPC over HTTP deployment scenarios" guide is available

833401  (http://support.microsoft.com/kb/833401/ ) How to configure RPC over HTTP in Exchange Server 2003

827330  (http://support.microsoft.com/kb/827330/ ) How to troubleshoot client RPC over HTTP connection issues in Office Outlook 2003

For more information about Exchange Server 2003 RPC over HTTP, visit the following Microsoft Web sites:

• Exchange Server 2003 RPC over HTTP Deployment Scenarios
  http://www.microsoft.com/downloads/details.aspx?FamilyID=f7d2d6e5-579f-4779-a6b8-7ef931ec02a5&DisplayLang=en (http://www.microsoft.com/downloads/details.aspx?FamilyID=f7d2d6e5-579f-4779-a6b8-7ef931ec02a5&DisplayLang=en)
• Remote Procedure Calls Using RPC over HTTP
  http://msdn2.microsoft.com/en-us/library/aa375384.aspx (http://msdn2.microsoft.com/en-us/library/aa375384.aspx)
• Configuring Outlook 2003 for RPC Over HTTP
  http://office.microsoft.com/en-us/ork2003/HA011402731033.aspx (http://office.microsoft.com/en-us/ork2003/HA011402731033.aspx)

Back to the top

Export a Web server certificate from the IIS-based computer that hosts the RPC proxy site

1. On the Web server computer, start Microsoft Internet Information Services (IIS) Manager. To do this, click Start, point to Administrative Tools, and then click Internet Information Services (IIS) Manager.
2. Expand the computer node, expand Web Sites, right-click the Web site that you want to export the certificate from, and then click Properties.
3. Click the Directory Security tab, and then click View Certificate.
4. In the properties of the certificate, make sure that the certificate says "You have a private key that corresponds to this certificate."
5. Click the Details tab, click Issuer, and then click Copy to File.
6. Click Next, click Yes, export the private key, and then click Next.
7. In the Export File Format dialog box, click Personal Information Exchange – PKCS #12 (.PFX).
8. Click to select the Include all certificate in the certification path if possible check box.
9. Make sure that the Enable strong protection (requires IE 5.0, NT 4.0 SP4 or above) check box and the Delete the private key if the export is successful check box are cleared.
10. On the Password page, type a password, and then confirm the password.
11. On the File to Export page, type the location where you want to save the exported certificate, and then click Next. For example, type c:\webcert.pfx, and then click Next.
12. On the Completing the Certificate Export Wizard page, click Finish.
13. When the Certificate Export Wizard dialog box informs you that the export was successful, click OK
14. Click OK to close the Default Web Site Properties dialog box.

Back to the top

On the ISA Server or Forefront Threat Management Gateway computer, import the Web server certificate from the IIS-based computer that hosts the RPC proxy site, and then install the certificate

1. On the ISA Server computer, click Start, click Run, type mmc in the Open box, and then click OK.
2. On the File menu, click Add/Remove Snap-in, click Add, and then click Certificates.
3. Click Add, click Computer account, click Next, click Finish, click Close, and then click OK.
4. Expand Certificates (Local Computer), right-click Personal, point to All Tasks, and then click Import.
5. Click Next, click the certificate file that you want to import, and then click Next.
6. In the Password box, type the password to decrypt the private key, click to select the Mark this key as exportable check box, and then click Next.
7. Leave the Place all certificates in the following store option selected, make sure that Personal is selected in the Certificate store box, click Next, and then click Finish.
8. When you receive the following message, click OK:
   The import was successful.
9. Expand Personal, and then click Certificates.
10. Make sure that the certificate with the name of the Web server computer appears in the right pane. You might have to update the display before this certificate appears.
11. Right-click the Web server certificate, and then click Properties.
12. If the Enable all purposes for this certificate option is selected, click Enable only the following purposes, click Apply, and then click OK.

Back to the top

Create a new Web publishing rule on the ISA Server computer

Note If you already have a Microsoft Outlook Web Access (OWA) Web publishing rule and the OWA server is also the RPC proxy server, you can add /RPC/* to the path instead of creating a new rule.

ISA Server 2006

1. Start the ISA Server/Threat Management Gateway Management tool.
2. Expand name of ISA Server 2006 or Threat Management Gateway computer.
3. Right-click Firewall Policy, point to New, and then click Exchange Web Client Access Publishing Rule.
4. In the Exchange Publishing rule name box of the New Exchange Publishing Rule Wizard, type a descriptive name for the new publishing rule, and then click Next.
5. In the Exchange version list, click Exchange Server 2003, click to select the Outlook RPC/HTTP(s) check box, and then click to clear the following check boxes:
   • Outlook Web Access
   • Outlook Mobile Access
   • Exchange ActiveSync
   Click Next.
6. Leave the default Publish a single Web site or load balancer option selected, and then click Next.
7. Click Use SSL to connect to the published Web server or server farm, and then click Next.
8. In the Internal site name box, type the DNS name that internal users use to access the Web site. For example, type alias.example.com.
   
   Note The internal name must match the name that appears on the server certificate that is installed on the internal Web server.
9. Click to select the Use a computer name or IP address to connect to the published server check box, type the name of the computer or the IP address of the computer that hosts the RPC Proxy in the Computer name or IP address box, and then click Next.
10. In the Accept requests for list, click This domain name (type below), type the DNS name that external users must use to access the Web server. For example, type mail.example.com. In this domain name, replace mail with the publicly-accessible alias that you use for the Web site.
11. Click Next.
12. On the Select Web Listener page, click New.
13. On the Welcome to the New Web Listener Wizard page, type a descriptive name in the Web listener name box, and then click Next.
14. Leave the default Require SSL secured connections with clients option selected, and then click Next.
15. On the Web Listener IP Addresses page, click to select the External check box, and then click Next.
16. Click Select Certificate, click the server certificate that you previously imported, and then click Select.
    
    Note Make sure that the name on the certificate matches the name that is used by Office Outlook 2003 clients to connect. If the certificate does not match, the Office Outlook 2003 connection does not work, the Office Outlook 2003 user does not receive a warning, and the user cannot continue.
17. Click Next.
18. In the Select how clients will provide credentials to ISA Server/Threat Management Gateway list, click HTTP Form Authentication, and then click Next.
    
    Note For more information about the authentication methods that are available, click the authentication settings link.
19. If you want to enable the Single Sign On functionality, click to select the Enable SSO for Web sites published with this Web listener check box, and then type the Single Sign On domain in the SSO domain name box. For example. type .example.com..
    
    Note In this example, note the period (dot) that appears before "example.com."
20. Click Next. Review the settings on the Completing the New Web Listener Wizard page, and then click Finish.
21. If you configured a different authentication method in step 18, examine the value of the Require all users to authenticate check box for this Web listener. To do this, follow these steps:
    • On the Select Web Listener page, click Edit.
    • Click the Authentication tab, and then click Advanced.
    • If the Require all users to authenticate check box is selected on the Web listener, you must reconfigure the Web listener to use basic authentication.
    • Click OK two times.
22. On the Select Web Listener page, click Next.
23. In the Select the method used by ISA Server/Threat Management Gateway to authenticate to the published Web server list, click Basic authentication, and then click Next.
24. On the User Sets page, leave the All Authenticated Users user set in the This rule applies to requests from the following user sets box, click Next, and then click Finish. For more information about what to do if you are not using the default settings in the HTTP filter configuration, click the following article number to view the article in the Microsoft Knowledge Base:
    823175  (http://support.microsoft.com/kb/823175/ ) Fine-tuning and known issues when you use the Urlscan utility in an Exchange 2003 environment
    For more information about HTTP filtering, visit the following Microsoft Web site:
    http://technet.microsoft.com/en-us/library/cc302627.aspx (http://technet.microsoft.com/en-us/library/cc302627.aspx)
25. Click Apply to apply the changes to the firewall policy, and then click OK.

ISA Server 2004

1. Start the ISA Server Management tool.
2. Expand name of your ISA Server 2004-based computer.
3. Right-click Firewall Policy, point to New, and then click Web Server Publishing Rule.
4. Type a descriptive name for the new server publishing rule, and then click Next.
5. If the Allow option is not selected, click Allow, and then click Next.
6. Under Computer name or IP address, type the name of the computer or the IP address of the computer that hosts the RPC Proxy, type the path of the file or folder you want to publish in the Path box, and then click Next.
7. Under Accept requests for, you can configure the rule to accept all requests, or only to accept requests for a specific domain name.
8. Type the domain name in the Public name box, and then click Next. For example, type host header name that you assigned to the Web site.domain name.com, and then click Next.
9. On the Select Web Listener page, click New.
10. On the Welcome to New Web Listener Wizard page, type a descriptive name in the Web listener name box, and then click Next.
11. On the IP Addresses page, click to select the External check box, and then click Next.
12. On the Port Specification page, click to select the Enable SSL check box, and then click Select.
13. Click the server certificate that you previously created, and then click OK.
    
    Note Make sure that the name on the certificate matches the name that is used by Office Outlook 2003 clients to connect. If the certificate does not match, the Office Outlook 2003 connection does not work, the Office Outlook 2003 user does not receive a warning, and the user cannot continue.
14. Click Next, and then click Finish.
15. On the Select Web listener name page, click Edit.
16. Click the Preferences tab, and then click Authentication.
17. If the Require all users to authenticate check box is selected on the Web listener, you must reconfigure the Web listener to use basic authentication.
18. Click OK two times.
19. On the Select Web Listener page, click Next.
20. On the User Sets page, click All Users, click Next, and then click Finish. For more information about what to do if you are not using the default settings in the HTTP filter configuration, click the following article number to view the article in the Microsoft Knowledge Base:
    823175  (http://support.microsoft.com/kb/823175/ ) Fine-tuning and known issues when you use the Urlscan utility in an Exchange 2003 environment
    For more information about HTTP filtering, visit the following Microsoft Web site:
    http://technet.microsoft.com/en-us/library/cc302627.aspx (http://technet.microsoft.com/en-us/library/cc302627.aspx)

Back to the top

Troubleshooting

• Make sure that RPC over HTTP traffic is functioning correctly internally. You must allow access from ISA Server or from Threat Management Gateway to the Web server that hosts the RPC proxy before you can test traffic from ISA Server or from Threat Management Gateway. If ISA Server or Threat Management Gateway is configured as an Edge Firewall and the RPC proxy is located on the internal network, you must have either of the following rules:
  • A rule that allows SSL from the Localhost object to the Internal network.
  • A rule that allows all IP traffic from the Localhost object to the Internal network.
  To test the RPC over HTTP traffic, type https://domain name/rpc in a Web browser, and then press ENTER. If you receive the following warning message, click OK:
  You are about to view pages over a secure connection.
  
  Any information you exchange with this site cannot be viewed by anyone else on the Web.
  If you receive a message that states that the certificate was issued by a company that you have not chosen to trust, make sure that the client computer trusts the root certification authority (CA) that issued the certificate. Typically, you receive this message when you do not configure the server to use a third-party certificate.
  
  When you are prompted for your credentials, type your user name in the Universal Naming Convention (UNC) format, type your password, and then click OK. For example, type your user name in the domain\user name format , and then click OK.
  
  The following error message is the expected behavior and indicates that both the server and the client are correctly configured:
  The page cannot be displayed HTTP Error 403.2 - Forbidden: Read access is denied. Internet Information Services (IIS)
• If you have Windows Server 2003 Service Pack 1 (SP1) installed, you are prompted to enter your credentials three times instead of one time. After you enter your credentials for the third time and then click OK, you receive the following error message:
  You are not authorized to view this page
  You do not have permission to view this directory or page due to the access control list (ACL) that is configured for this resource on the Web server.
  
  HTTP Error 401.3 - Unauthorized: Access is denied due to an ACL set on the requested resource.
  Internet Information Services (IIS)
  This error message is the expected behavior. The error message indicates that the RPC virtual directory on the server is correctly configured.
  
  Alternatively, you can use the Web browser to locate the Rpcproxy.dll file that is hosted in the RPC virtual directory. To do this, follow these steps:
  1. On the client computer, start Microsoft Internet Explorer, type the URL of the Rpcproxy.dll file that is hosted in the RPC virtual directory in the Address list, and then click Go.
     
     For example, type https://mail.contoso.com/rpc/rpcproxy.dll, and then click Go.
  2. When you are prompted for credentials, type a user name in the UNC format (domain\user_name), type a password, and then click OK.
  You see a blank page in the Web browser together with a lock icon in the Internet Explorer status bar. The lock icon signifies that you have successfully established a secured (SSL) connection to the server. This behavior indicates that the RPC virtual directory is configured correctly on the server.
• If you use Web publishing and the domain name is the same on the internal network and the external network, it is a good idea to confirm that the ISA Server or Threat Management Gateway computer can successfully resolve all the names that are used in the publishing rule to the RPC proxy server. If all the names are not resolved successfully, you can change the hosts file on the ISA Server or Threat Management Gateway computer.
• If a remote user is prompted for logon credentials multiple times, the remote user may be typing credentials in the wrong format. Remote users must use the domain name\user name format.
• You can verify the RPC over HTTP connection to the computer that is running Exchange. To do this, follow these steps:
  1. Click Start, click Run, type outlook /rpcdiag in the Open box, and then click OK.
  2. Type your credentials in the User name box and in the Password box, and then click OK. If HTTPS appears in the Conn column in the Exchange Server Connection Status dialog box, a service is connected by using RPC over HTTP.
     
     Note The Exchange Server Connection Status window may appear directly behind the Outlook program window.

How to Install ISA Server 2006 Enterprise Edition?

Install ISA Server 2006 Enterprise Edition

Once you’ve performed those actions, you’ll be ready to install ISA Server 2006 Enterprise Edition on your unihomed computer.
Perform the following steps to install ISA Server 2006 Enterprise Edition:

1. Copy the installation files for ISA Server 2006 Enterprise Edition to the unihomed ISA firewall device. Then double click on the isaautorun.exe to bring up the installation dialog box.
2. In the Microsoft ISA Server 2006 beta installation dialog box, click the Install ISA Server 2006 link.
3. Click Next on the Welcome to the Installation Wizard for Microsoft ISA Server 2006 Beta page.
4. On the License Agreement page, select the I accept the terms in the license agreement option and click Next.
5. On the Customer Information page, enter your User Name, Organization and Product Serial Number and click Next.
6. On the Setup Scenarios page, select the Install both ISA Server services and Configuration Storage server option. Note that this option implies that you can install both ISA Server firewall services and the CSS at the same time, and then later install additional array members once you have this installed. This is not true. Use this option only if you plan to deploy a single member ISA Server 2006 Enterprise Edition array. If you plan to add additional array members later, then do not select this option. Since this article is focused on installing a single ISA Server 2006 Enterprise Edition unihomed device as a single member array, we will use this option. Click Next.

Figure 1

7. On the Component Selection page, accept the default settings. Note that you don’t have the option to install the Firewall client. I’m not sure where or how we’ll end up doing this in the future, as its also not an option on the initial setup page. This will likely be worked out by the time the product releases. Note that Advanced Logging is MSDE logging. If you prefer to use SQL logging or text based logging, then do not select this option  Click Next.

Figure 2

8. On the Enterprise Installation Options page, select the Create a new ISA Server enterprise option. Since this will be the only machine in the array, we need to create a new ISA enterprise. Note that the option Create a replica of the enterprise configuration option is not available to workgroup configurations. This is something to keep in mind in the future if you want to have a backup CSS for your enterprise array. However, its not an issue for us, since this is a single machine array. Click Next.

Figure 3

9. Click Next on the New Enterprise Warning page.

Figure 4

10. On the Internal Network page, click the Add button.
11. In the Addresses dialog box, click the Add Adapter button. In the Select Network Adapters dialog box, put a checkmark in the checkbox next to the single interface installed on the computer. Note that in a typical firewall installation, this NIC would be used to define the default Internal network. In a unihomed ISA firewall Web proxy configuration, this is not the case, since all addresses are considered internal. Click OK.

Figure 5

12. In the Addresses dialog box, click OK. Note that the addresses listed in this dialog box will have no meaning in the unihomed ISA firewall configuration scheme. In a normal ISA firewall setup with multiple interfaces, these addresses would define the default Internal ISA firewall Network. However, as I mentioned in the last step, with a unihomed ISA firewall in Web proxy mode, all addresses are considered part of the default Internal ISA firewall Network.

Figure 6

13. Click Next on the Internal Network page. Note again that the IP addresses listed here do not represent the default Internal Network on a unihomed ISA firewall as we'll see later when we apply the single NIC ISA firewall template.

Figure 7

14. On the Firewall Client Connections page, click Next. We don’t have to worry about Firewall client connections because both Firewall and SecureNAT clients are not supported on a unihomed ISA firewall in Web proxy configuration. Only Web proxy clients are supported.
15. Click Next on the Services Warning page.
16. Click Install to being the installation.
17. On the Installation Wizard Completed page, put a checkmark in the Invoke ISA Server Management when the wizard closes checkbox and click Finish.
18. Close the Internet Explorer window entitled Protect the ISA Server Computer.

Have Questions about the article? Ask at: http://tinyurl.com/m9bsu

Post Installation Review

advertisement

The first thing you’ll notice when the console opens is a link entitled Click here to learn about the Customer Experience Improvement Program. Click that link.

Figure 8

This brings up the Customer Feedback dialog box. I highly recommend that you participate in the Customer Experience Improvement Program. No personal data is sent to Microsoft and the result of your participation is to make the ISA firewall product more flexible and provide even higher levels of security to your network. Select the Yes option to participate in the program.

Figure 9

After you select an option and click OK, the link disappears from the middle pane of the console.
Expand all the nodes in the left pane of the ISA firewall console. Then perform the following steps to see the definition of the default Internal ISA firewall Network:

1. In the left pane of the ISA firewall console, click the Networks node under the Configuration node.

Figure 10

2. In the Networks node, click the Networks tab in the middle pane of the ISA firewall console. Double click on the Internal entry.
3. In the Internal Properties dialog box, click the Addresses tab. Here you see the addresses that define the default Internal ISA firewall Network at this time. However, this will change when we configure this ISA firewall to act as a Web proxy only unihomed ISA firewall. Click Cancel to leave this dialog box.

Figure 11

What we need to do now is apply the unihomed ISA firewall template to configure this machine as a unihomed Web proxy only ISA firewall. Perform the following steps to apply the template:

1. In the Task Pane, click the Templates tab. Scroll down the list of templates and click the Single Network Adapter template.

Figure 12

2. Click Next on the Welcome to the Network Template Wizard page.
3. Click Next on the Export the ISA Server Configuration page. Note that you have the option to export the current configuration, but we’ll not use that option because we haven’t made any configuration changes from the default setting.

Figure 13

4. On the Internal Network IP Addresses page, you’ll see the addresses that will be configured to define the default ISA firewall Internal Network. Notice that all IP addresses except the local host network range are considered part of the default Internal network. For this reason, SecureNAT and Firewall clients are not supported in a unihomed Web proxy mode ISA firewall configuration. You do not need to make any changes on this page. Click Next.

Figure 14

5. On the Select a Firewall Policy page, you are offered a single firewall policy to select from. Click on the Apply default Web proxying and caching configuration option. This will apply the default Deny rule to the firewall policy for the array. No Network Rules are created because the Web proxy always replaces its own IP address for the IP address of the Web proxy client connecting to the Internet through the unihomed Web proxy mode ISA firewall. Click Next.

Figure 15

6. On the Completing the Network Template Wizard page, click Finish.
7. Click Apply to save the changes and update the firewall policy.
8. Click OK in the Apply New Configuration dialog box.

At this point you’re ready to start configuring firewall policy and customizing the installation.

Have Questions about the article? Ask at: http://tinyurl.com/m9bsu

Summary

In this article we went over the concepts involved with deploying and installing a unihomed Web proxy mode ISA firewall. We then went over the step by step details of installing a unihomed Web proxy mode ISA firewall. At the end of the process the ISA firewall was ready for configuration and customization. I’ll follow up on this article with one on what I consider to be key post configuration tasks that you should perform before configuring ISA firewall policy.

SQL Data Types Chart

SQL - Numbers, Decimals, and Dates

Data Types: Integers - (3, -17) Point(Decimal) - (3.23415) Date - (2004-06-22 10:33:11.840)

SQL - Boolean Data   ("TRUE" / "FALSE") ( 1 / 0 )

SQL - Character Strings Character Strings: VARCHAR - ('Words or numbers') Text - ('Once upon a time...')

·         SQL Server Table Column Types:

bigint	Integer value (-9,223,372,036,854,775,808 - 9,223,372,036,854,775,807)	2^63
int	smaller Integer value (-2,147,483,648) - (2,147,483,647)	2^31
smallint	smaller Integer value (-32,768) - (32,767)	2^15
tinyint	smaller Integer values 0 - 255	2^8
bit	Integer data value (either 1 or 0 value)	1 or 0
decimal	Decimal values from -10^38 - 10^38	10^38
numeric	Decimal values from -10^38 - 10^38	10^38
money	Money values (-922,337,203,685,477.5808) - (922,337,203,685,477.5807)	2^63
smallmoney	Smaller Money Values (-214,748.3648) - (214,748.3647)	2^31
datetime	Date value (January 1, 1753) - (December 31, 9999)
smalldatetime	Smaller Date Value (January 1, 1900) - (June 6, 2079)
timestamp	Unique Number Value (updates when row is updated)
char	Character String Value (max 8,000 characters)
varchar	Character String Value maximum of 8,000 characters, unless otherwise noted)
nchar	Character String Value (max 4,000 characters)
nvarchar	Character String Value (max 4,000 characters)
text	Character String Value (max 2,147,483,647 characters)	2^31
ntext	Character String Value (max 1,073,741,823 characters)	2^30
binary	Binary Value (max 8,000 bytes)
varbinary	Binary Value (max 8,000 bytes)
image	Binary Value (max 2,147,483,647 bytes)	2^31
uniqueidentifier	Global Unique ID (GUID)

Wireless Configuration of TP-LINK wireless Router

Wireless Connecting

Bridge & WDS

• Change the IP of one model
• Configure WDS or Bridge function
• Note that the Channel and the wireless security must be the same
• Disable DHCP on the second router

WDS for 11N wireless router
Note:

• Change the IP of one model to avoid IP conflict
• The Main AP must supports WDS (Four MAC address format)
• Disable DHCP on the second router
• The Wireless Channel and security must be the same as the Main AP

Bridge for 11b/g wireless router
Note:

• Change the IP of one model
• Disable DHCP on the second router
• The wireless Channel and security must be the same

TL-WR543G/TL-WR743ND WISP Configuration
Default Operation mode is AP Client Router



TL-WR543G/TL-WR743ND WISP Configuration

AP Client Router

• Wireless used to connect to the WISP on client mode,
  and works as the WAN port to provide PPPoE/Dynamic IP connection
• LAN side only have cable access to the device

Configuration:

• 1. Connect your computer to the TL-WA5110G/TL-WA5210G via cable
• 2. Quick Setup -> Choose AP Client Router -> Choose PPPoE/Dynamic IP/Static IP ->
  Type in the SSID of the WISP -> Click Finish to reboot

Or

• 1. Connect your computer to the TL-WA5110G/TL-WA5210G via cable
• 2. Go to Wireless -> Wireless Mode page,
  click Survey button to search the SSID and connect to the WISP -> Click Save to reboot

WISP solution

• Using TL-WR543G/TL-WA5110G
• Works on AP-client router mode/WISP, as a WISP CPE
• Works with outdoor direction antenna
  TL-ANT2414A/TL-ANT2424B/TL-ANT2409B

TL-WR543G/TL-WR743ND WISP Configuration
AP Router
When choose the TL-WR543G/TL-WR743ND on AP Router mode, it works a normal wireless router,
the same as TL-WR541G/TL-WR542G or TL-WR741ND/TL-WR740N

Wireless Security Configuration
Hidden SSID
Hide the SSID/Network name of your wireless router/network,
so other people who do not know it will can not connect to your network

MAC address Filtering
It will block the specified computer to connect to your wireless router/Network

How do I configure TL-WA5110G/TL-WA5210G to wireless AP Client Router mode?

TL-WA5110G/TL-WA5210G to wireless AP Client Router mode

Suitable for: TL-WA5110G, TL-WA5210G

Step 1 Connect your computer to TL-WA5110G/TL-WA5210G with a cable, and then log into the Web-based Utility by entering the IP address 192.168.1.254 into Web Browser.

If you can not log into the Web-based Utility, please refer to the instruction How do I log into the Web-based Utility of TL-WA501G/TL-WA601G for a try.

Step 2 Configure the operation mode to AP Client Router and connect to the wireless network.

1.      Click on Operation mode on the left, select AP Client Router, then click on Save.

2.    Click on Wireless -> Wireless Mode on the left side, select Client.(In that page, only Client mode is available)

3.    If you know the SSID of the wireless network or the MAC address of the AP/WISP, you can type them in the SSID or MAC of AP box manually, and then Click on Save to save the settings

4.    Or you can click on Survey button to view the available wireless networks, then click on Connect.

After click on Connect button, the SSID of the wireless network and the MAC address of the AP will be shown in the Client mode box automatically.

5.      After the configuration, click on Save.

Step 3 Click Network->WAN. Then select the correct type for WAN Connection Type. If you are not sure about the WAN Connection type, please contact your service provider about this.

For Dynamic IP: You just need to select Dynamic IP from the drop-down menu and then click on Save.

For Static IP: Please select Static IP from the drop-down menu, and input the correct parameters in the boxes. The parameters are given by your internet service provider (ISP). Then click on Save.

For PPPOE: Please select PPPOE from the drop-down menu, and input the correct parameters in the boxes. The parameters are given by your service provider. Then click Save.

NOTE: If you want to connect the AP to a wireless router and the IP address of the router is 192.168.1.254 as well, you need to change the IP address of the AP in order to avoid IP conflict. You can do it as follows:

1.     Click Network->LAN on the left side.

2.     Change the IP Address to 192.168.2.254.

3.     Click on save, and reboot your device.

How to configure TL-WA5110G/TL-WA5210G as a repeater

Suitable for: TL-WA5110G, TL-WA5210G

Attention:TL-WA5110G /TL-WA5210G can only support WEP security type under Repeater/Universal Repeater mode.

Information of Root Router:

• LAN IP: 192.168.1.1
• SSID: TP-LINK-test
• Encryption Type: WEP Open Hexadecimal
• Passphrase: 0123456789

Preparation

Since the DHCP function on TL-WA5110G /TL-WA5210G is disabled by default, we have to manually assign an IP address as 192.168.1.x to the computer to match the default IP address (192.168.1.254) of the AP. Please click here for detailed instruction.

For example, we can configure the computer’s Local Area Connection IP address as 192.168.1.100/255.255.255.0

Then please connect the computer to the AP with an Ethernet cable.

Configuration on Device (TL-WA5110G / TL-WA5210G):

1.   Login to the Repeater’s management page.

In the address bar of the web browser, type in the IP address of the repeater (default is 192.168.1.254) and press Enter.

Type in the Username and Password (default is admin).

2.  Click Operation Mode, select AP mode and click Save.

3.   Click Wireless -> Wireless Mode. Select Universal Repeater as the Wireless Mode. Then click Survey.

(If the Root Router supports WDS, you can select Repeater as Wireless Mode.)

4.   Find the Root Router’s SSID on the AP List, and then click Connect.

5.   Click Save.

If you can see the following picture, please wait until it refreshes back to the Status page.

6.    Do the same Wireless Security Settings as your Root Router.

At Repeater/Universal Repeater mode, TL-WA5110G /TL-WA5210G can only support WEP as security type. And if your Root Router´s wireless network is secured, please make sure that the security type is WEP.

In our example, the Root Router is WEP secured.      

Click Wireless ->Security settings. 

Select WEP, and set the same Type, Key Format and Key Type as the Root Router.

Then put in the same password "0123456789".

Click Save.

7. Click System Tools->Reboot->Reboot to restart the device.

After you go through all the above steps, the Repeater should be working properly with the Root Router.

NOTE:

After you finish the settings, please change the Local Area Connection IP address setting for your computer back to the default.