WinConnect Server XP is a software solution that turns a Windows Small Business Server 2003 (32-bit), Windows Server 2003 (32-bit) or Windows XP (Home and Professional (32-bit) Editions) Host computer into an RDP 6.0, 5.2 or 5.1 server. This allows multiple Remote Desktop Protocol (RDP) 4.0, 5.0, 5.1, 5.2 and 6.0-enabled devices (such as Terminals, Internet/Information Appliances, Tablet PCs and PDAs) to connect to it to run Windows applications simultaneously and independently. These devices can connect to the server over a wired or wireless TCP/IP connection, such as local area network (LAN), wide area network (WAN), dial-up (Internet), digital subscriber line (DSL, ADSL), Integrated Services Digital Network (ISDN), or virtual private network (VPN) connection.

You can remotely connect to control your computer from another office, from home, or while travelling. This allows you to use the data, applications, and network resources that are on your office computer, without physically being in your office.

WinConnect Benefits:

•	Reduces enterprise TCO by providing an alternative to MS Windows® 2000 Server or Windows Server 2003
•	Remote connection means that you have access to your data and Windows applications wherever you need it
•	Centralized processing means that your data is safer, stored on a central computer
•	Centralized processing means that your Thin Client devices (such as Terminals, Internet/Information Appliances, Tablet PCs and PDAs) are less expensive to purchase and less expensive to maintain back

•	You must purchase or register WinConnect Server XP from the computer on which it was installed. Hence, please ensure that you have installed the WinConnect Server XP software on the computer and make sure it is working correctly in demo mode and meeting your requirements before purchasing and registering WinConnect Server XP online.
•	Make sure you have logged into the computer as a full-access Administrator
•	Under Microsoft Internet Explorer, click on Tools/Internet/Options/Security/Custom Level. Set the "Reset To:" option to "Medium" and click on the Reset button. Next, click on the "OK" button to apply the changes
•	When prompted to install and run "ThinSoft Inc. Registration Control", you must click on the "Yes" button to accept and trust content from ThinSoft Inc

•	Color Depth - Supports for up to 24-bit color
•	Audio - The audio stream, such as .mp3 or .wav formats, is played through the client's audio system
•	Parallel and Serial Ports - The applications running on the Host PC can have access to the peripherals (such as customer display pole, cash drawer, bar code reader/scanner, and other devices) connected to the parallel and serial ports on the client (Windows XP Professional only)

•	Color Depth - Supports for up to 24-bit color
•	Audio - The audio stream, such as .mp3 or .wav formats, is played through the client's audio system
•	Storage - The client's storage is accessible as if it were a network shared drive(s) Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only)
•	Parallel and Serial Ports - The applications running on the Host PC can have access to the peripherals (such as customer display pole, cash drawer, bar code reader/scanner, and other devices) connected to the parallel and serial ports on the client (Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only)
•	Printer - The default printing device can be the printer connected to the client locally (Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only) or a network printer
•	Clipboard - Data can be interchanged between the applications running on the Host PC and applications running on the client via the shared clipboard

•	Supports local drive mapping (Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only)
•	Supports local serial and parallel ports redirection (Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only)
•	Supports local printing (Windows XP Professional (32-bit), Windows Server 2003 (32-bit) and Windows Small Business Server 2003 (32-bit) only)

•	Windows Small Business Server 2003 (32-bit), Windows Server 2003 (32-bit) or Windows XP (Home or Professional (32-bit) Edition) computer
•	Network/Internet connection
•	A Pentium III 1GHz or faster processor is the minimum recommendation for 1 Host and 1 Remote Desktop users. Increase the processor speed by 100MHz or more per additional Remote Desktop user, depending on the applications the user will be running. For best performance, a single or dual Pentium IV processor is suggested. Equivalent AMD processors are also supported.
•	For Windows XP (32-bit), the minimum memory requirement for 2 users (1 Host user and 1 Remote Desktop user) is 256MB. For Windows Small Business Server 2003 (32-bit) and Windows Server 2003 (32-bit), the minimum memory requirement for 2 users (1 Host user and 1 Remote Desktop user) is 384MB. Additional 64MB or more per additional Remote Desktop user, depending on the applications the user will be running.

Installation is simple. By following a few steps, it normally takes less than 10 minutes to set up. See the WinConnect Server XP User Manual for instructions.

You can purchase/register the WinConnect Server XP software online via the WinConnect Server XP Control Center or visit our web site at http://www.thinsoftinc.com.

Important Notes for Internet Registration:

1.	Ensure that you are using the Microsoft’s Internet Explorer as the default browser.
2.	Make sure you have logged into the Windows Small Business Server 2003 (32-bit), Windows Server 2003 (32-bit) or Windows XP (Home and Professional (32-bit) Editions) as an Administrator with full access rights.
3.	Within Microsoft Internet Explorer, click on Tools => Internet => Options => Security => Custom Level. Set the "Reset To:" option to "Medium" and click on the Reset button. Next, click on the "OK" button to apply the changes. This is the required Internet Explorer setting and is what the WinConnect Server XP Registration page requires in order to successfully work the purchase/registration process.

Notes: When prompted to install and run the "ThinSoft ..." and/or the "SheriffNet Module" ActiveX controls, you must click on the "Yes" button to install and run the ActiveX controls.

Please wait for each page to load completely before proceeding to the next page.

Step 1:	Click on the WinConnect Server XP Control Center icon located on your desktop. This will launch the WinConnect Server XP Control Center. First, select Help from Control Center menu, and then select Register on the Web from the Help sub-menu.
Step 2:	Microsoft Internet Explorer will be launched and directed to the WinConnect Server XP Registration site. Select the language you wish to use to register WinConnect Server XP.
Step 3:	If you have purchased WinConnect Server XP prepaid serial number(s), enter the prepaid serial number(s), and click the “Register New Serial Numbers” button. If you do not have the WinConnect Server XP prepaid serial number(s) and want to purchase/ register WinConnect Server XP license online, select the option “Check this box if you would like to purchase additional user licenses” and click “Create New License and Purchase WinConnect Server XP” button.
Step 4:	Enter the information requested and click “Continue with Registration”.
Step 5:	Once WinConnect Server XP is successfully registered, you will need to restart Windows.

WinConnect Server XP can be purchased online via http://www.thinsoftinc.com at a price of US$ 299.95 per pack of 3 users. Each WinConnect Server XP license allows an additional 3 users. As user needs increase, additional licenses can be purchased online.

Yes, up to a maximum of twenty-one (21) Remote Desktop Clients can be connected to the WinConnect Server XP Host.

It depends on the type of software products you are using. Most software products will allow all users to open and edit different documents at the same time, using the same program. Each user can also use different software products, concurrently.

If you have any questions regarding compatibility of a particular application program, you can download the trial version of WinConnect Server XP to test your application before you purchase. Alternately, you can ask the software vendor if the application supports Windows Terminal Services. If Terminal Services is supported, the software will most likely work on WinConnect Server XP environment.

Users who intend to run the software products concurrently are advised to do the following:

(a) Review the Software Products' End User License Agreement if they are authorized to run multiple instances/sessions, using a single copy of the Software Products, concurrently

and/or

(b) Check with the respective companies of the Software Products for such usage and/or similar usage.

It depends on the types of applications you are running. Some applications will provide full read and write privileges to the user who opened or accessed the file first; the other users may then have read only privilege.

All of your preferences are stored in individual "profiles". Your profile stores all of your preferences, and individual information.

In order to take advantage of this feature, each user must log in to the system with a unique user name.

The Remote Desktop Client supports windowed DOS box where you can run DOS applications and access the DOS command prompt.

Files can be stored on the central WinConnect Server XP Host or on the local storage of the Remote Desktop Client.

Yes, if the Remote Desktop Client is a RDP 5.1, 5.2 or 6.0-enabled device and local drive redirection is enabled when connecting to the WinConnect Server XP Host.

Data can be stored in the central WinConnect Server XP Host instead of the local PC hard drive. Normally, the server is located in a secured place and is only accessible by an IT personnel who has the rights to do so. The data transmitted from your Remote Desktop Client, normally, takes a path along a secured communication/network, to the WinConnect Server XP Host. Consider this security against data stored on a PC, in an open office environment, vulnerable to be stolen along with your data (in the Thin Client environment, they would have stolen a "nearly" worthless box with no data in it).

The performance of the WinConnect Server XP Host will depend on the system set-up and configuration, the number of users supported and the applications the users will be running.

For more information, refer to "What is the recommended WinConnect Server XP Host requirement?" above.

A broadband Internet connection over digital subscriber line (DSL, ADSL), cable or Integrated Services Digital Network (ISDN) connection improves performance. However, RDP transfers only minimal data (such as display data and keyboard data) between the WinConnect Server XP Host and the Remote Desktop Client, therefore, it works even with a low-bandwidth Internet connection over a wired or wireless connection (Dial-up, GPRS, etc.).

It depends on the server settings. If the 'Max session idle time' option is enabled, connections will be disconnected after the specified amount of idle time. This means that the session will disappear from your screen and it will become 'disconnected'. It doesn't mean the applications you had opened will be closed. If you reconnect to the WinConnect Server XP Host again, they will still be active. You may configure the server settings so that 'Disconnected' sessions stay in that state for certain amount of time, during which you can reconnect. If you do not reconnect within the specified amount of time, the disconnected session will be log off and all applications will be closed, at which point, the next time you reconnect, you will have to re-run the applications, as you will be starting a new session.

Yes, Windows and Novell Netware networks are supported. You only require one network node (one network card and one IP address) for all the users. Users can login to the network by using different user names and passwords.

The Console user cannot monitor and control the activities on the Remote Desktop Clients.

The Security Policy Settings in Windows Small Business Server 2003 (32-bit), Windows Server 2003 (32-bit) and Windows XP Professional (32-bit) Edition allow the Administrator to control certain user's privileges, as well as control certain actions allowed for the users.

Administrator can modify the security-relevant settings, including users' rights to shut down Windows, by configuring the Local Security Policy.

The WinConnect Server XP allows multiple users to simultaneously and independently share the same hardware and software installed on the Host computer. Some software is licensed for use on a single computer while other software may be licensed for single or multiple users. It is the responsibility of the WinConnect Server XP purchaser/user to read and comply with the licensing agreements of any software that may be used.

Additionally, it is the responsibility of the WinConnect Server XP purchaser/ user to read and comply with the Windows licensing agreement with regards to Remote Desktop access, or contact Microsoft for clarification.

You may download or purchase the WinConnect Remote Desktop Client software from our web site at http://www.thinsoftinc.com

The Remote Desktop Client software is available for download at the
Microsoft web site here. The client software is installed by default on computers running Windows Small Business Server 2003 (32-bit), Windows Server 2003 (32-bit), Windows XP Professional (32-bit) and Windows XP Home Edition.

The instructions on how to create a Remote Desktop connection and start a Remote Desktop session are available for download at the Microsoft web site here.

The Remote Desktop Client software is available for download at the Microsoft web site here.

You can option WinConnect Server to use a port other than 3389. To do so, run Regedt32. When using Regedt32, please be careful as it is possible to damage your system. Using Regedt32, locate the

KEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Terminal Server\WinStations\RDP-Tcp

key. Within this key, locate the PortNumber subkey. By default, it will be set to 00000d3d hex, or 3389. Modify the hex value and save. Reboot the computer for it to take effect.

Please remember that you will need to modify all clients that connect to this computer. For WinConnect, when you configure a connection the port address will appear on the "Advanced" tab. To change the port used by the Microsoft client, follow the client instructions found here.

The use of a firewall will improve the security of your WinConnect Server. However, both the built-in Windows XP firewall and third party firewalls will block the network traffic necessary for Remote Desktop Protocol (RDP). This traffic must be enabled for WinConnect Server to work.

There are two ports necessary for WinConnect Server. First is a TCP port required for RDP. This is normally 3389. The second is a UDP port required if you want the computer to be visible as a terminal server to a client browsing the network. This is port 137.

If you are using a third party firewall, please see the documentation that comes with your firewall.

To configure the built-in Windows XP firewall, go to Start>Control Panel>Network Connections. Right click on the network connection that will be used by your terminals and select Properties. On the Advanced tab you must check Protect My computer and network by limiting or preventing access to this computer from the Internet. When this option is checked, the Settings button is accessible. On the Services tab, check Remote Desktop. This will enable the TCP port of 3389. Click on the Add button. Enter "Server Browser" under Description of Service. Enter the name of the server in Name or IP address of the computer hosting this service on your network. Enter "137" for External Port number. Click on UDP, and then click on OK. Click on OK in the Advanced Settings dialog box and then click on OK in the Local Area Connection Properties dialog box.

For additional security it is possible to change the port number used by RDP. Instructions for doing this can be found at products_wcs_faq.html#faq29. If you do change this port number, you must also adjust your firewall to enable TCP traffic through whatever port you have chosen.

There are two ways to accomplish this, depending on whether you have multiple external IP addresses:
1) Use multiple external ip addresses. In order to do this, you configure your router to map a different external IP address to each internal server. For example, let us presume that you have two internal servers at internal addresses 192.168.10.1 and 192.168.10.2. You have two external IP addresses 64.64.64.11 and 64.64.64.12. You would edit your firewall NAT configuration to look like this:

ip nat source static tcp 192.168.10.1 3389 64.64.64.11 3389
ip nat source static tcp 192.168.10.2 3389 64.64.64.12 3389

This configuration would map incoming traffic to port 3389 on 64.64.64.11 to port 3389 on server 192.168.10.1. Incoming traffic to port 3389 on 64.64.64.12 would be mapped to port 3389 on server 192.168.10.2.

Note that the exact configuration syntax will vary from firewall to firewall. The example is for a Cisco 2600. The advantage to this approach is that client software will not need to be optioned to use a non-standard port.

The disadvantage is that it will require multiple external IP addresses.

2) Use a single IP address. In order to use a single external IP address, you will need to map different port numbers to each internal server. Let us presume that you have two terminal servers at 192.168.10.1 and 192.168.10.2 and one external IP address at 64.64.64.11. In this case you would edit your firewall NAT configuration to look like this:

ip nat source static tcp 192.168.10.1 3389 64.64.64.11 3389
ip nat source static tcp 192.168.10.2 3389 64.64.64.11 3399

This configuration would map incoming traffic to port 3389 on 64.64.64.11 to port 3389 on server 192.168.10.1. Incoming traffic to port 3399 on 64.64.64.11 would be mapped to port 3389 on server 192.168.10.2.

Again, the exact configuration syntax will vary from server to server. Port 3389 was chosen as an example. You can use other ports so long as they do not conflict with other uses. To support additional machines, you will select a different port for each server.

In order to use this approach, you do not need to change the RDP port on server 192.168.10.2 in the server configuration. This is because the firewall NAT will redirect the incoming traffic to the standard port on the server. You do need to change the port used by the clients. In order to access server 192.168.10.2, the client software must be optioned to connect to port 3399 at address 64.64.64.11. Port number can be specified on the "Advanced" tab when editing a connection in WinConnect. Instructions for changing the port for the Microsoft client can be found at here.

The advantage to this approach is that a single external IP address can be used. The disadvantage is that client software must be configured to use a non-standard port.

First, get the IP address of the host computer (the computer that will have WinConnect Server XP installed on it).

Click Start then Run and enter the letters CMD.

In the DOS box that appears, enter the command: ipconfig. Then hit the Enter key.

The computer’s IP address will be displayed in the information shown.  Make note of it.

Next, open a browser and enter the URL http://www.portforward.com in the address bar.

At the bottom of PortForward’s opening page, make a note of the IP address shown after the text:

Your external IP address is

This IP address is what your remote users will need to enter into the “Computer” field in the Microsoft Remote Desktop Connection program on their computers.  Remote Desktop Connection is part of Windows XP and can be found on either the Accessories or Communications menus (Start/Programs/Accessories/Communications) depending on which version of Windows XP is installed.

In the second paragraph on the PortForward opening page, locate the word Routers and click on it.  This will take you to a page displaying most brands and models of routers. Locate the specific brand and model of router used in your location and click on it (if your router is not listed, please contact your router's vendor for details on how to configure your router's port forwarding for Remote Desktop access).

This action takes you to the Application page.  Scroll down until you locate Remote Desktop and click on it.

You will now see a step-by-step set of instructions for configuring your router to allow Remote Desktop access.  You will be asked to enter an IP address at the beginning of the configuration routine; this is the IP address you obtained in the first part of these instructions.


Note:
Static IP address:

There are two IP addresses involved regarding Remote Desktop access.  One is the external IP address owned by the router and the other is the internal IP address of the host computer.  Ideally, both of these should be “static” (meaning they never change).  Unfortunately, this is not always the case.

The external IP address is controlled by your Internet provider.  You may check with them if you are not sure whether your account has a static IP address.
The host computer’s IP address is entirely in your control. For detailed information on how to set your host computer to employ a static IP address, please see this web page, http://www.portforward.com/networking/static-xp.htm