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 7.x, 6.x, 5.2 or 5.1 server. This allows multiple Remote Desktop Protocol (RDP) 4.0, 5.0, 5.1, 5.2, 6.x and 7.x -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
•	The "Internet Explorer Enhanced Security Configuration" setting in Windows® Server 2003 or Windows® Small Business Server 2003 must be turned off. Click on Windows Start -> Settings -> Control Panel -> Add or Remove Programs -> Add\Remove Windows Components -> Windows Components Wizard. Uncheck the "Internet Explorer Enhanced Security Configuration" option.
•	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, the minimum memory requirement for 3 Remote Desktop users is (3 x 128 Megabytes) + 256 Megabytes of RAM. For Windows Server 2003, the minimum memory requirement for 3 Remote Desktop users is (3 x 128 Megabytes) + 384 Megabytes of RAM. For Windows Small Business Server 2003, the minimum memory requirement for 3 Remote Desktop users is (3 x 128 Megabytes) + 512 Megabytes of RAM. 128 MB of additional RAM or more is recommended for each 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.	The "Internet Explorer Enhanced Security Configuration" setting in Windows® Server 2003 or Windows® Small Business Server 2003 must be turned off. Click on Windows Start -> Settings -> Control Panel -> Add or Remove Programs -> Add\Remove Windows Components -> Windows Components Wizard. Uncheck the "Internet Explorer Enhanced Security Configuration" option.
4.	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.x-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

HKEY_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

A.	Firstly, make sure your WinConnect Server XP is currently registered and working correctly in license mode. Please take note and keep a proper record of the WinConnect Server XP primary serial number (open WinConnect Server XP Control Center --> Terminal Servers, the WinConnect Server XP primary serial number will be displayed on the right window pane).
B.	Please follow the instructions described below to purchase additional WinConnect Server XP licenses: 1. Logon into Windows as an Administrator on the PC where WinConnect Server XP was installed and registered. 2. Make sure the "Internet Explorer Enhanced Security Configuration" setting in Windows® Server 2003 or Windows® Small Business Server 2003 is turned off. Click on Windows Start -> Settings -> Control Panel -> Add or Remove Programs -> Add\Remove Windows Components -> Windows Components Wizard. Uncheck the "Internet Explorer Enhanced Security Configuration" option. 3. Open Internet Explorer --> Tools --> Internet Options --> Security --> Custom Level. Make the "Reset To:" box to show "Medium" and then click the Reset button (the default Security setting "Medium-high" will not work). This is the required Internet Explorer's Security setting and is what the WinConnect Server XP Registration site requires in order to successfully complete the registration process. For Windows XP SP2/3 or Windows Server/SBS 2003 SP1/2, open Internet Explorer --> Tools --> Pop-up Blocker and select "Turn Off Pop-up Blocker". Open Internet Explorer --> Tools --> Internet Options --> General --> Delete Files or Delete --> Delete Files to delete the "Temporary Internet Files". 4. Open the WinConnect Server XP Control Center, click on Help --> Register on the Web. Internet Explorer will be launched and directed to the WinConnect Server XP Purchase/Registration site. 5. On the WinConnect Server XP Purchase/Registration page that says "WinConnect Server XP; Upgrade Your Serial Number or Purchase New License", your WinConnect Server XP primary serial number should be displayed in the "Your Registered Serial Number" box. 6. Select the option "Check this box if you would like to purchase additional user licenses" since you are purchasing additional user licenses online where the payment is by credit card. 7. Click on the "Register New Serial Numbers" button and follow the on-screen instructions to continue with the purchase/registration of additional WinConnect Server XP licenses.
Notes:
a.	During the purchase/registration process, you must accept all ActiveX prompts signed by "ThinSoft ..." and/or the "SheriffNet Module" ActiveX Controls.
b.	Please wait for each page to load completely before proceeding to the next page.
c.	Please DO NOT click on the MS Internet Explorer's "Refresh" or Back" button during the purchase/registration process.
d.	You will need to restart Windows after you have successfully purchased and registered additional WinConnect Server XP licenses.

A.	For local printer re-direction on the remote client:
	1. On the remote client, before connecting to the WinConnect Server XP Host, you will need to install the printer as per normal and make sure that the printer is working correctly, please refer to the printer user manual for installation instructions. 2. On the remote client, open the MS Remote Desktop Connection (RDC) software, click on Options --> Local Resources, and check "Printers". Then connect to the WinConnect Server XP Host. On the remote desktop session, click on Start --> Settings --> Printers and Faxes; you should then see your printer (please see note below). NOTES: Printing at the remote client location is a function of the MS RDC software being used. The MS RDC software send the information about the local printer to WinConnect Server XP/Windows XP/Windows Small Business Server 2003/Windows Server 2003 Host and if that printer is listed among the Windows native printer list, then all will go fine. If the printer model is not one contained within the list of Windows native printers, then it will be necessary to install the printer driver on the WinConnect Server XP/Windows XP/Windows Small Business Server 2003/Windows Server 2003 Host first. In some cases, to install the printer correctly on the WinConnect Server XP/Windows XP/Windows Small Business Server 2003/Windows Server 2003 Host will require actually connecting the printer to the WinConnect Server XP/Windows XP/Windows Small Business Server 2003/Windows Server 2003 Host or the printer driver will not install properly. When this installation is done, the printer should be detected as a local printer when the remote client is connected to the WinConnect Server XP/Windows XP/Windows Small Business Server 2003/Windows Server 2003 Host. If local printing still does not work after following the above procedure, you will need to check with the printer manufacturer to verify if the printer driver is designed to support Windows Terminal Services, or the procedure to install the printer and it's printer driver to work under Windows Terminal Services Printers that use ports that do not begin with COM, LPT, or USB are not redirected in a remote desktop connection. Please check with your printer manufacturer's Technical Support on how to configure your printer to use a COM/LPT/USB port.
B.	For local printer redirection for local printer using DOT port or network printer, please refer to the following MS article (Note: the local printer driver must be installed on the Host): http://support.microsoft.com/kb/302361 Printers That Use Ports That Do Not Begin With COM, LPT, or USB Are Not Redirected in a Remote Desktop or Terminal Services Session View products that this article applies to. Article ID : 302361 Last Review : December 3, 2007 Revision : 4.8 This article was previously published under Q302361 SYMPTOMS When you use Remote Desktop Connection or the Terminal Services Client version 4.0 or 5.0 to connect to another Windows-based computer from a computer that is not running Windows Server 2003, your local printers may not be redirected. As a result, your local printers are not available in the remote desktop or terminal services session. For example, if your Windows XP-based computer has a multifunction print device using a DOT4 port, it may not be redirected in a remote desktop session to a Windows 2000- or Windows Server 2003-based computer. CAUSE This problem occurs because the printer port does not begin with COM, LPT, or USB. By default, printer port names that do not begin with COM, LPT, or USB are only redirected in Windows Server 2003. By default, multifunction print devices may not be redirected unless you are running Windows Server 2003 on your local computer because they use DOT4 ports. RESOLUTION To resolve this problem on a computer that is not running Windows Server 2003, force all ports (including DOT4) on the client computer to be filtered for redirection. To do this, add a DWORD value named FilterQueueType to HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR and set its value data to FFFFFFFF. Follow these steps, and then quit Registry Editor: 1. Click Start, click Run, type regedit, and then click OK. 2. Locate and then click the following key in the registry: HKEY_CURRENT_USER\Software\Microsoft\Terminal Server Client\Default\AddIns\RDPDR 3. On the Edit menu, point to New, and then click DWORD Value. 4. Type FilterQueueType, and then press ENTER. 5. On the Edit menu, click Modify. 6. Type FFFFFFFF, and then click OK. This enables all ports on the client to be redirected. To work around this problem on a client computer that has a multifunction print device, change the port that the multifunction print device uses from DOT4 to an LPT port. For example, to configure a multifunction print device to use an LPT port on a Windows XP-based computer, follow these steps: 1. InControl Panel, openPrinters and Faxes. 2. Right-click the local printer that is not redirected, and then click Properties. 3. Click the Ports tab, click an LPT port, and then click Apply. The printer should now appear next to that port. 4. Close the Printer Properties window, and then reconnect by using Remote Desktop. Important: When a multifunction printer is using a standard LPT port instead of the DOT4 port, it loses its multifunction capabilities, such as scanning, faxing, or copying. To regain the multifunction capabilities, the print device must use the DOT4 port. STATUS This behavior is by design. MORE INFORMATION To view the port name for your printer, or to determine if the device uses a DOT4 port, view the properties of that printer, and then click the Ports(or the Details) tab.

Follow the steps described below to connect to the WinConnect Server XP system's Console session from the remote client via the Remote Desktop Connection software:
Step 1:	Open Remote Desktop Connection (Click Start, point to Programs or All Programs, point to Accessories, and then click Remote Desktop Connection).
Step 2:	Click on the Options button to configure the Windows Logon and connection settings.
Step 3:	In Computer, type in the IP address of WinConnect Server XP system used by WinConnect Server XP software (e.g. 218.10.0.30 /admin). Click Connect.
Step 4:	In the Log On to Windows dialog box, type in the same user name and password that user has logged on the WinConnect Server XP system, and then press the Enter key. The Remote Desktop window will open.

Click Here to view the connection diagram.

A Terminal Server Gateway (TS Gateway) server is a kind of gateway that enables authorized users to connect to remote computers on a corporate network. These authorized users can connect from any computer by using an Internet connection. TS Gateway uses the Remote Desktop Protocol (RDP) together with the HTTPS protocol to help create a more secure encrypted connection.

Earlier versions of RDC cannot connect to remote computers across firewalls and across network address translators. This is because port 3389 is typically blocked to improve network security. Port 3389 is the port that is used for Remote Desktop connections. However, a TS Gateway server uses port 443. Port 443 transmits data through a Secure Sockets Layer (SSL) tunnel.

A TS Gateway server has the following benefits:

• It enables Remote Desktop connections to a corporate network from the Internet without requiring a virtual private network (VPN) connection.
• It enables connections to remote computers across firewalls.
• It helps you share a network connection with other programs that are running on the computer. This enables you to use the Internet service provider (ISP) connection instead of the corporate network to send and to receive data over the remote connection.

To specify a TS Gateway server, follow these steps:

1. Click Start, click All Programs, click Accessories, click Communication, and then click Remote Desktop Connection.
2. Click Options, click the Advanced tab, and then click Settings.
3. Click Use these TS Gateway server settings, type the server name in the Server name box, and then select one of the following logon methods from the Logon methods list:


• Allow me to select later
  This option lets you select a logon method when you connect.
• Ask for password
  This option prompts you for a password when you connect.


4. Select or clear the Bypass TS Gateway server for local addresses check box. By selecting this check box, you prevent the traffic that is moving to and from local network addresses from being routed through the TS Gateway server. This option makes the connection faster.

Click Here to view the connection diagram.

Follow the steps described below to connect to the WinConnect Server XP Host using Terminal Services Web Access:
Step 1:	Install Remote Desktop Web Connection software on the WinConnect Server XP Host. Remote Desktop Web Connection version 5.2.3790 can be downloaded at URL, http://www.microsoft.com/downloads/details.aspx?FamilyID=e2ff8fb5-97ff-47bc-bacc-92283b52b310&displaylang=en
Step 2:	Install Internet Information Services (IIS) on the WinConnect Server XP Host. a. To Install IIS on Windows Server 2003 Go to Windows Start => Control Panel => Add or Remove Programs => click Add/Remove Windows Components. In the Windows Components Wizard, under Components, select Application Server. Click Next. After the installation has completed, click Finish. b. To Install IIS 5.1 on Windows XP Go to Windows Start => Settings => Control Panel => 'Add/Remove Programs' => 'Add/Remove Windows Components'. Check the box next to 'Internet Information Services (IIS)' and do not change the other default settings.
Step 3:	Go to Windows Start => Settings => Control Panel => Windows Firewall => Exceptions. Under Programs and Services, check the box next to World Wide Web Service (http) and click ok.
Step 4:	From the remote desktop client, run Internet Explorer browser and go to URL, http://server_name/tsweb (i.e. http://145.316.241.81/tsweb)
Step 5:	Remote Desktop Web connection will then be running in the Internet Explorer.

To connect to the WinConnect Server XP Host using Terminal Services Web Access, please refer to the following MS article:

http://support.microsoft.com:80/kb/951607

You cannot connect to a remote computer or start a remote application when you use Terminal Services Web Access or Remote Web Workspace on a Windows XP SP3-based or Windows Small Business Server 2003 SP1-based computer that this article applies to. Article ID: 951607 - Last Review: March 4, 2009 - Revision: 8.0

SYMPTOMS

On a Windows XP Service Pack 3 (SP3)-based or Windows Small Business Server 2003 Service Pack 1 (SP1)-based computer, you experience the following symptom: When you try to connect to a remote computer through Remote Desktop Web Connection (TSWeb), the Connect button is disabled.

CAUSE

This issue occurs if the ActiveX control for the Remote Desktop Connection client is not enabled on the Web browser. By default, the ActiveX control is disabled after you install Windows XP Service Pack 3 (SP3) or Windows Small Business Server 2003 SP1.

RESOLUTION

To work around this issue, follow these steps:

1. Start Internet Explorer.
2. Visit the Web site that is causing this problem.
3. If you are using Windows Internet Explorer 7, follow these steps:
1. On the Tools menu, point to Manage Add-ons, and then click Enable or Disable Add-ons. The Manage Add-ons dialog box appears.
2. In the list of add-ins, search for the Microsoft Terminal Services Client Control ActiveX control or for the Microsoft RDP client Control ActiveX control. If you cannot find the control, see the steps in "If the control is not displayed in the list of add-ons" at the end of this section.
3. Click the control, click Enable, and then click OK to close the Manage Add-ons dialog box.
If you are using Internet Explorer 6, follow these steps:
1. On the Tools menu, click Manage Add-ons. The Manage Add-ons dialog box appears.
2. In the list of add-ins, search for the Microsoft Terminal Services Client Control ActiveX control or for the Microsoft RDP client Control ActiveX control. If you cannot find the control, see the steps in "If the control is not displayed in the list of add-ons" at the end of this section.
3. Click the control, click Enable, and then click OK to close the Manage Add-ons dialog box.
4. Add the site to your Trusted Sites in Internet Explorer.
5. Restart Internet Explorer.
6. Try to connect to the remote computer. Or, try to start the remote application.

If the control is not displayed in the list of add-ons

Sometimes the Microsoft Terminal Services Client Control ActiveX control will not be displayed in the list of add-ons. If it is not displayed, you can try the following steps to attempt to display the control by resetting Internet Explorer back to a default configuration.

1. Start Internet Explorer.
2. Click File, and then click Import and Export.
3. Follow the steps in the wizard to export your Favorites.
4. Click Tools, and then click Internet Options.
5. Click Advanced, and then click Reset.

Once Internet Explorer has been reset to a default configuration, try to connect to the remote computer or start the remote application. If it does not work, then follow the steps in the workaround to enable the Microsoft Terminal Service Client Control ActiveX control. If the control is still not listed, you can modify the registry to remove a key, if it exists.

Important This article contains information about how to modify the registry. Make sure that you back up the registry before you modify it. Make sure that you know how to restore the registry if a problem occurs. For more information about how to back up, restore, and modify the registry, click the following article number to view the article in the Microsoft Knowledge Base: 322756 (http://support.microsoft.com/kb/322756/ ) How to back up and restore the registry in Windows

Remove the following registry key, if it exists:
HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Ext\Settings\{7584C670-2274-4EFB-B00B-D6AABA6D3850}

Once the registry key is removed, exit and restart Internet Explorer, and try to connect to the remote computer or start the remote application again.

If this does not resolve the issue, you can re-register the mstscax.dll file. To do this, follow these steps:

1. Exit Internet Explorer.
2. Click Start, click Run, and the type or copy and paste the following text in the Open box, and click OK:
3. %windir%\system32\regsvr32 mstscax.dll
4. At the confirmation prompt, click OK. Restart Internet Explorer, and try to connect to the remote computer or start the remote application.

MORE INFORMATION

In Windows XP Service Pack 2 (SP2), you had to install the Msrdp.ocx file to enable the Terminal Services ActiveX control. Windows XP Service Pack 3 (SP3) already includes this ActiveX control and installs it by using the Mstscax.dll file. By default, this ActiveX control is disabled in Windows XP Service Pack 3 (SP3).

APPLIES TO

Microsoft Windows XP Service Pack 3
Windows Home Server
Microsoft Windows Small Business Server 2003, Premium Edition Service Pack 1 (SP1)
Windows Small Business Server 2008 Premium
Windows Small Business Server 2008 Standard
Windows Essential Business Server 2008 Standard

You will need to disable "Single session per user" option. To do this, on Windows desktop, open "WinConnect Server XP Control Center". Select and right click on the WinConnect Server XP computer name, select Properties and set the option "Single session per user" to "No" and then restart Windows.

"Single Session Per User" setting restricts a user to a single Remote Desktop session. When enabled, the active Remote Desktop session will be disconnected when the same user login on another Remote Desktop session. When disabled, the same user can login on multiple Remote Desktop sessions. Default setting is "Yes".

Note: If the Single Session Per User option is enabled, the Reconnect Setting from User will be automatically disabled and the user is allowed to reconnect to a disconnected Remote Desktop session from any computer.

This is related to Windows Local Security Policy --> Local Policies --> Security Options
--> Accounts: Limit local account use of blank passwords to console logon only security option.

"Limit Blank Password Use" setting limits local account use of blank passwords to console logon only. If set to ?Yes?, Remote Desktop User (apply to local user account only, i.e. Non-Domain user account) will need a password to logon into Windows. Default setting is "Yes".

2X LoadBalancer v10.5 was tested working with WinConnect Server XP on Windows XP Professional or Windows Server 2003.

The 2X LoadBalancer software is available for download at url, http://www.2x.com

For Step-by-Step Installation Guide on 2X LoadBalancer software, refer to url, http://www.2x.com/documentation

For more product information on 2X LoadBalancer software, refer to url, http://www.2x.com/loadbalancer

Disclaimer: ThinSoft does not guarantee nor warrant that the 2X LoadBalancer software will be suitable for a particular purpose. It is entirely up to the customer's discretion to make this decision and verify that the 2X LoadBalancer software meets his/her requirements.