|
 |
 |
Home > Support > WinConnect |
|
|
Manual
 |
 |
 |
|
Released Date: |
January 2009 |
Size: |
4.5MB |
Download Time: |
approx 13 minutes (56kpbs) |
|
|
|
 |
 |
 |
System Requirements
Recommended
System Requirements on Host PC |
• |
486 or higher
|
• |
Linux operating system
with X-Windows® System installed |
• |
16 megabytes of RAM (depending
on supported display resolutions) |
• |
400 kilobytes of disk
space (storage for the program executables
and for stored connection profiles) |
• |
Network/Internet connection
|
• |
Display adapter with Linux
driver support |
|
Installation for Embedded Systems
What is WinConnect? |
WinConnect is a Remote Desktop Protocol (RDP) 5.1 client for the Linux operating system. Using RDP, you can create a remote connection to a Windows computer to run Windows applications. The connection can be over a local area network (LAN) or over the Internet. The low bandwidth required by RDP will even allow a connection over a dial-up or wireless connection. Because most of the processing is done on the host machine, you can display Windows applications on computers that are not Intel or Windows based – such as a personal digital assistant (PDA).
For more information on Microsoft terminal services, please see http://www.microsoft.com/windows2000/technologies/terminal/ |
What are the advantages of WinConnect? |
• |
Remote connection means that you have access to your data and Windows applications wherever you need it. |
• |
Central processing means that your data is safer, stored on a central server. |
• |
Central processing means that your desktop computers are less expensive to purchase and less expensive to maintain. |
• |
A Linux-based client means that you have the low cost and high reliability of Linux, combined with the Windows applications that you need. |
|
Who should use WinConnect? |
Terminal and Set-Top-Box Manufacturers:
• |
Reduce costs and increase reliability by using the Linux operating system |
• |
Supports RDP 5.1, including local printing |
• |
Ideal for large accounts. Graphical user interface allows the installer to configure connections to multiple servers |
• |
Ideal for small businesses – WinConnect can connect to a terminal server without configuration.. Maximum simplicity! |
• |
Choose from two different user interfaces for the one that best fits your memory and storage requirements |
• |
Expert technical and engineering support |
• |
Software can be customized to meet your needs |
PDA and Mobile Phone Manufacturers:
• |
Provide access to Windows applications from your PDA |
• |
Take advantage of the Remote Access capability that will be built into every Windows XP Professional computer |
• |
Using your PDA, users can obtain mobile access to their Windows desktop, IT professionals can provide mobile access to their mission critical applications |
• |
Choose from two different user interfaces for the one that best fits your memory and storage requirements |
• |
Expert technical and engineering support |
• |
Software can be customized to meet your needs |
• |
Reduce per-unit cost by using the Linux operating system, or ask us about porting WinConnect to your platform |
|
WinConnect Features |
• |
Supports RDP 5.1 for connection to Windows Vista, Windows 7, Windows Server 2008, Windows Server 2008 R2, Windows NT 4 Terminal Server, Windows 2000 Server, Windows XP Server and Windows XP Professional |
• |
Runs under Linux on i86 and StrongARM processors. Additional processor support available on request. (Downloaded version supports i86 only. Please contact us for the StrongARM version.) |
• |
Supports local printing |
• |
Supports sound (XP host required) |
• |
Supports up to 24 bit color (XP host required) |
• |
Supports cut-and-paste between terminal sessions and between Linux and Windows applications |
• |
Supports local drive mapping so that Windows applications can access data on Linux drives, including floppy and CD drives |
• |
Easy-to-use interface provides menu-driven configuration. |
• |
Terminal servers can be selected from a list, or pre-configure server connections. |
• |
Terminals can be configured to automatically connect to a terminal server, concealing the complexity of a local menu. |
|
System Requirements |
• |
Linux operating system with X Windows System installed |
• |
7 to 21 megabytes of RAM, depending on supported display resolutions. A 320 X 240 display running at a 16 bit color depth will require about 8 megabytes. 200 to 400 kilobytes of storage (depending on the user interface selected) |
• |
Network/Internet connection |
• |
Display adapter with Linux driver support |
• |
Host system can be a Windows NT 4 Terminal server, Windows 2000 Server, Windows XP Server or Windows XP Professional |
|
Linux dependencies |
• |
Kernel version 2.2 and above |
• |
X Windows version 2.2.6 and above |
• |
TCP/IP socket interface |
• |
GLIBC version 2.1 and above |
• |
GDBM version 1.8 |
• |
GTK+ version 1.2.10 (enhanced user interface only) |
• |
GLIB version 1.2.10 (enhanced user interface only) |
|
Linux Distributions Supported |
Note: this is not intended to be an inclusive list of supported Linux distributions; these are the distributions that have been tested in our lab.
We have successfully tested:
• |
Red Hat 6.2 and above |
• |
Turbolinux 6.1 and above |
• |
Caldera 2.4 and above |
• |
Debian 2.2 and above |
• |
Debian GNU/Linux 3.0 ("woody") |
• |
Debian GNU/Linux 3.1 ("sarge") |
• |
Madrake 7.1 and above |
• |
Familiar 0.4 and above |
• |
Fedora Core 3 |
• |
SuSe Professional 9.1 and above |
There are no distributions that are known not to work with WinConnect. |
FAQ
1. |
What
is WinConnect?
WinConnect is a software solution that enables
Linux-based terminals to connect to WinConnect Server,
Windows Vista, Windows 7, Windows Server 2008,
Windows Server 2008 R2, Windows 2003 Server, Windows 2000 Server,
Windows NT 4 Terminal Server or Windows XP Professional via Remote Display
Protocol (RDP). Because most of the processing
is done on the Windows servers, users can display
the latest Windows® applications on computers
that normally would not be powerful enough,
making use of a 486 or an old Pentium computer.
The connection can be over a local area network
(LAN) or over the Internet.
|
2. |
Why would I want to use the WinConnect software?
WinConnect Benefits:
• |
Remote connection means
that you have access to your data and
Windows applications wherever you need
it. |
• |
Central processing means
that your data is safer, stored on a central
server. |
• |
Central processing means
that your desktop computers are less expensive
to purchase and less expensive to maintain. |
• |
A Linux-based client
means that you have the low cost and high
reliability of Linux, combined with the
Windows applications that you need. |
• |
Recycling old computers
as terminals means that you preserve the
environment while saving money. |
|
3. |
How
do I buy additional software licenses for different
number of users?
WinConnect can be purchased online at http://www.thinsoftinc.com
for US $99.95. Each WinConnect license allows
an additional user. As user needs increase,
additional licenses can be purchased online.
WinConnect is designed to be run by a single
user on a single computer. If you wish to have
multiple simultaneous users on a single Linux
machine, you must use WinConnect VX. back
|
4. |
What
is the recommended system memory to run WinConnect
on the Linux desktop?
The minimum memory required to run Linux operating
system, X-Windows and WinConnect is 16MB, as
all Windows applications are executed on the
Windows server and displayed on the Linux desktop.
However, more memory may be required depending
on the type of Linux-based applications you
may be running on the Linux desktop itself.
|
5. |
What
is the recommended Linux desktop requirement to
run WinConnect?
• |
486 or higher |
• |
Linux operating system
with X-Windows® System installed |
• |
16 megabytes of RAM
(depending on supported display resolutions) |
• |
400 kilobytes of disk
space (storage for the program executables
and for stored connection profiles) |
• |
Network/Internet connection |
• |
Display adapter with
Linux driver support back |
|
6. |
What
distributions of Linux have been tested with WinConnect?
We have tested the following distributions:
• |
Red Hat 6.2 and above |
• |
Turbolinux 6.1 and above |
• |
Caldera 2.4 and above |
• |
Debian 2.2 and above |
• |
Debian GNU/Linux 3.0
("woody") |
• |
Debian GNU/Linux 3.1
("sarge") |
• |
Mandrake 7.1 and above |
• |
Familiar 0.4 and above |
• |
Fedora Core 3 |
• |
SuSe Professional 9.1
and above |
|
7. |
What
services must Linux provide for WinConnect?
Kernel version 2.2 and above
X Windows version 4.0 and above
TCP/IP socket interface
GLIBC version 2.1 and above
GDBM version 1.8
GTK+ version 1.2.10 (enhanced user interface
only)
GLIB 1.2.10 (enhanced user interface only) back
|
8. |
What
user interface options are available for WinConnect?
There are two user interfaces to choose from.
These provide the user with the ability to create
and manage connection profiles. The first is
a basic interface that runs directly on top
of X Windows. This interface is designed to
run on a 200 x 200 display. The second is an
enhanced interface that runs on top of GTK.
It is designed for a 640 x 480 display.
We can customize the user interface if required.
|
9. |
What
processors are supported by WinConnect?
We are currently supporting the Intel x86, SPARC,
Hitachi SH3 and the StrongARM processor families.
WinConnect can be ported to other processors
if desired.
|
10. |
What
do I need to add additional users?
Additional users are supported by adding additional
Linux desktops running WinConnect.
|
11. |
How
difficult is it to set-up the WinConnect?
Installation is simple. By following a few steps,
it normally takes less than 15 minutes to set
up. See the WinConnect User Manual for detailed
instructions.
|
12. |
When
both users open the same file, can they save the
file at the same time?
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.
|
13. |
Can
both users use the same program at the same time?
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.
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.
|
14. |
What
is the difference between WinConnect and WinConnect
VX?
WinConnect is designed to be used by a single
user on a Linux computer. It can only be run
on Linux session 0. If you want to have more
than one user on your Linux computer or if you
need to run WinConnect in a session other than
session 0, you should use WinConnect VX.
|
15. |
Will
multiple users running Windows applications concurrently
make my Windows server work slower?
The Windows server set-up and configuration
will depend on the type of Windows applications
being run.
For more information, please visit Microsoft
web site here.
|
16. |
Where
are my files stored?
Files are stored on the central Windows server,
rather than on the local PC hard drive.
|
17. |
Can
I elect to store files locally on my computer?
If your Windows server is running WinConnect
Server XP, Windows 2000 Server or Windows XP
Professional, you may store files on your local
hard or floppy disk.
|
18. |
Why
is the thin client method cheaper?
Analysts estimate that thin clients reduce your
cost of desktop computing by 35-57 percent per
year over a typical networked PC (1, 2). Take
the 35 percent savings against a low estimate
of the fully realized annual cost of operating
and managing a networked PC, which is $9,000
(3). (Estimates run as high as $14,000 for this
cost.)
$9,000 x .35 = $3,150 savings per year or $
263 per month
Based on the price that starts as low at $99.95
per license for thin terminals, you can easily
implement the thin client solution in your workplace.
Since these savings are in terms of reduced
maintenance, service and support, without the
need for constant hardware upgrades, the terminals
can be viewed as best long-term solution.
The recent TCO analysis done by Gartner Group
showed that the total annual indirect cost benefit
for thin clients is 32 percent for thin client
compared with fat managed PCs, and 90 percent
for thin clients compared with fat unmanaged
PCs (4).
• |
35 percent: Gartner
Group, "Microsoft Terminal Server
Edition and Thin-Client Computing",
1998, pages 11-12. |
• |
57 percent: Zona Research
"Desktop Clients: A Cost of Ownership
Study" 1996, page 5. |
• |
Actually $9,983, Gartner
Group Research. |
• |
DF-14-2800, P.Lowber,
28 September 2001, Gartner Group, "Thin-Client
vs. Fat-Client TCO", pp 2. |
|
19. |
Can
I use WinConnect to connect to a remote Windows
server using a dial-up modem?
Yes. You just need to set-up a Dial-up connection.
Ensure that the serial ports and modem have
been installed; and supporting Point to Point
Protocol.
|
20. |
Will
my connection to the server be disconnected for
any reason?
It depends on the server settings. If idle disconnect
feature is enabled, connections will reset after
the specified hours of idle time. This means
if you haven't used the WinConnect software,
the session will disappear from your screen,
it will become 'disconnected'. It doesn't mean
the applications you had opened (e.g. Netscape,
Word etc), will be closed. If you reconnect
to the server again, they will still be active.
You may configure the server settings so that
'Disconnected' sessions stay in that state for
certain hours, during which you can reconnect,
by simply typing in your password again. If
you do not reconnect within the specified hours,
the session will be reset and all applications
will be closed, at which point, the next time
you reconnect, you will have to re-run the applications
(e.g. Netscape, Word etc), as you will be starting
a new session.
|
21. |
I need a SVGA card, rather than a VGA card in
my PC?
The main difference between a SVGA and a VGA
card is the resolutions that it may support.
Choose the one that will meet your needs, making
sure the one you chose have an associated Linux
driver to support the resolutions that you want
it to support.
|
22. |
Do
I have my own Preferences for Word/Excel, bookmarks
for Netscape, or are they shared?
All of your preferences are stored in individual
"profiles". Your profile stores all
of your preferences, and individual information.
It is only accessible by you.
|
23. |
How
secure is my data, using WinConnect software?
Data is stored in the central Windows server
or other file servers. Normally, the server
is located in a secured place and is only accessible
by IT personnel who has the rights to do so.
The data transmitted from your "client",
normally, takes a path along a secure network,
to the server, so others may not intercept it.
Consider this security against data stored on
your 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).
|
24. |
Does
WinConnect allow me to view video clips and listen
to music or other sounds on the Linux station?
Yes, you can listen to music and other sounds
if you are connected to WinConnect Server XP,
Windows 2003 Server or Windows XP Professional
host. Windows 2000 servers, however, do not
support sound on RDP clients. You can view video,
but performance will not be as good as on a
standalone Windows machine.
|
25. |
How
do I use WinConnect to connect to a remote Windows
server using a dial-up modem?
You need to set-up a Dial-up connection. Ensure
that the serial ports and modem have been installed;
and supporting Point to Point Protocol (PPP).
One way to check for serial-port recognition
is to use the dmesg program which displays the
boot message. Run the dmesg program (piped through
the less command) and look for lines in the
output describing serial ports similar to these:
# dmesg | less
.......
ttyS00 at 0x03f8 (irq=4) is a 16550A
ttyS01 at 0x02fb (irq=5) is a 16550A
ttyS03 at 0x02e8(irq=3) is a 16550A
.........
To check if PPP exist on the system, use
the dmesg command again.
#dmesg | less
........
PPP: version 2.3.7
PPP line discipline registered
Another quick way to check if PPP is installed
is to use the rpm command.
# rpm -q ppp
ppp-2.3.11-7
1) To setup the dialer from GNOME desktop
panel
i) Click on the Gnome Application "Start"
button, "Programs", "Internet
Menu" and follow by the "Dialer
Configuration Tool".
ii) The tool's window will then appear.
iii) If the symbolic link /dev/modem/ does
not exist, click on "Add" and then
"Next" to query the modem.
iv) If a modem is found, click on the "Keep
this modem" and "Next" buttons
to select Devices as "/dev/ttyS0".
v) Next, enter a name for the dialup account,
along with the ISP's dialup number.
vi) Click on the "Next" button and
enter your assigned username and password.
vii) After clicking on the "Next"
button, you will be asked to select your ISP.
If your ISP is not listed, just select Normal
ISP.
viii) Click "Finish" to save the
account.
ix) To start your PPP connection, select Programs,
Internet, then click on the "RH PPP dialer"
menu.
x) Select the ISP account you created, click
OK and start the connection.
xi) In order to connect to Internet successfully,
you may need to specify your ISP's DNS servers
in your system's /etc/resolv.conf file.
e.g enter the line using this format :
nameserver 165.21.83.88
nameserver 165.21.100.88
2) To setup the dialer from KDE desktop panel
i) Click on the Application "Start"
button, select "Internet" and follow
by "kppp".
ii) The kppp configuration dialog box will
appear when you click on the setup button.
iii) Under the Account tab, click on the "New"
button.
iv) Enter the name of your ISP along with
the ISP's phone number.
v) Click on the IP tab and select whether
it is a dynamic or static IP address assigned
to your computer.
vi) Next, click on the DNS tab to enter your
ISP's DNS IP address.
vii) Under the Device tab, select the correct
modem device and connection speed for your
modem.
viii) When finished, click on the Modem tab
where you can use the buttons to change the
default modem AT commands, to query your modem,
or to test your modem by using kppp's built-in
terminal program. You can also change the
modem's volume by using the slider control
in the dialog box.
ix) When finished, click on the PPP tab where
you can select or deselect the options according
to your preference. If you click "Dock
into Panel" on connect, kppp will display
satiny modem icon with blinking send and receive
lights.
x) When finished, click OK and the kppp windows
will appear.
xi) To start your Internet connection, click
on the connect button in the kppp window.
|
26. |
How
do I set my Linux system to automatically connect
to the Windows terminal server?
It is first necessary to install WinConnect
and create a "default" connection
(marked in the connection profile as being the
"default") that is set with the options
desired.
On the Linux system, it is necessary to establish
a standard user (not root). Once this has
been done, this user's home directory will
be /home/. In this directory will be a file
called bashrc.
Edit the user's .bashrc file and, at the
bottom, add two lines:
winconnect -c
logout
Then save the file.
The next time this user logs in, WinConnect
will establish a connection using the options
set by the WinConnect default connection profile
options. The user will not have the ability
to damage the WinConnect settings by editing
them; the system administrator can log in
as "root" to edit them as necessary.
|
27. |
Why
doesn't my Windows XP Professional computer appear
in the list of available servers?
It is first necessary to enable the Remote Desktop
functionality. This is done on the "Remote"
tab of the System Properties dialog box. See
your Windows XP documentation for additional
details.
With this enabled, WinConnect can connect
to the XP computer if you supply its IP address.
If you wish the computer to appear in the
list of available servers, you must do the
following:
1. On the Windows XP computer, select "Run"
off of the start menu.
2. The program to open is "Regedit".
3. Find the following key: My Computer\HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server
4. Add or alter this value: TSAdvertise =
1
5. Exit Regedit and reboot the computer.
This procedure is recommended for experienced
computer users only. Regedit is an advanced
tool, and it is possible to damage your Windows
installation.
The simplest way to change your XP settings
for use with WinConnect is to download and
import the registry file at EnableRem-Adv-Col.reg
|
28. |
How
do I install a printer under Red Hat 7.2?
A) To setup a Printer with Redhat 7.2
1) On the Gnome desktop, go to the Main Menu
Button (on the panel) -> Programs ->
System -> Printer configuration.
2) To add a printer such as one attached to
the parallel port or USB port of your computer,
click the NEW button in the main printconf
windows.
3) Click NEXT to proceed.
4) Enter a unique name for the printer in
the Queue Name field, e.g. lp
5) Select local printer from the Queue Type
menu and click NEXT.
6) Printconf attempts to detect your printer
device. A printer device attached to the parallel
port Is usually referred to as /dev/lp0. A
printer device attached to the USB port is
usually referred to as /dev/usb/lp0. After
selecting your printer device, click NEXT.
7) Next, printconf will try to detect what
printer is attached to the printer device.
8) After selecting the queue type of the printer,
the next step is to select the printer driver.
Select the printer driver from the list. The
printers are divided by manufacturers. Click
the arrow beside the manufacturers for your
printer. Find your printer from the expanded
list and click the arrow beside the printer
name. A list of drivers for your printer will
appear. Select one.
9) Click the Apply button in the main windows
to save your changes and then print a test
page to ensure the configuration is correct.
B) Configure WinConnect for local printing
1) Click on the printing tab of the WinConnect
profile.
2) All existing Linux print queues can be
seen by clicking the drop-down arrow. After
selecting the desired print queue, associate
it with a windows printer driver. For example,
if you have a HP DeskJet 970Cxi connected,
click on the drop-down arrow of the windows
driver and select the HP DeskJet 970Cxi.
3) After connecting to the Windows Terminal
Server, you will have a new printer available
to Windows applications. Under Windows XP,
this printer will be called something like
lp (from XXX ) where XXX is the Linux station
name. Under Windows 2000 server, it will be
called lp/XXX/ Session 2 where XXX is the
Linux station name.
|
29. |
How
do I install a printer under Mandrake 8.1?
A) To setup a Printer with Mandrake 8.1
1) Connect a printer to the computer and
power up.
2) Log in as root.
3) Open a terminal session and run the command:
printtool
4) Choose Add printer to start the new printer
wizard.
5) You will be presented with the list of
available connections
6) Choose Local Printer - if you are connecting
a printer directly to a parallel / USB port
of your computer, in most cases the printer
model will be auto-detected.
7) Next you need to provide a name for your
printer, to easily identify it if you need
to, e.g. lp, and optionally a Printer description
and a physical location. Click OK.
8) You are then presented with the list of
supported printers. Check whether Printerdrake
did the auto-detection of your printer model
correctly. Search for the correct model or
a compatible one in the list when the cursor
is pointing to the wrong model.
9) After that, you are presented with the
settings associated with the chosen driver.
If the settings are correct, click OK.
10) Set the printer as the default printer
and finally test print the printer.
The above printer setup can also be accomplished
under KDE -> Control Center -> System
-> Printing Manager
B) Configure WinConnect for local printing
1) Click on the printing tab of the WinConnect
profile.
2) All existing Linux print queues can be
seen by clicking the drop-down arrow. After
selecting the desired print queue, associate
it with a windows printer driver. For example,
if you have a HP DeskJet 970Cxi connected,
click on the drop-down arrow of the windows
driver and select the HP DeskJet 970Cxi.
3) After connecting to the Windows Terminal
Server, you will have a new printer available
to Windows applications. Under Windows XP,
this printer will be called something like
lp (from XXX ) where XXX is the Linux station
name. Under windows 2000 server, it will be
called lp/XXX/ Session 2 where XXX is the
Linux station name.
|
30. |
How
do I upgrade WinConnect from a previous version?
To upgrade WinConnect from a previous version
1) Log in as root.
2) Download the new version of WinConnect
3) Before installing, note the unlock code
from the WinConnect "Menu>License>Show
information" dialog box.
Note: If you are upgrading from versions prior
to 1.3, please email support@thinsoftinc.com
for assistance.
4) Uninstall the installed version of WinConnect.
From a terminal session run /usr/local/share/winconnect/uninstall.
5) Install the new version of WinConnect
following the standard installation instructions.
6) Use the unlock code saved in step 3 to
unlock the new version.
|
31. |
What is the maximum resolution and colors, under
Windows, that can be set on the WinConnect running
on the Linux desktop when connecting to the Windows
server?
The maximum resolution is 1600 x 1200, depending
on the video card's resolutions support on the
Linux desktop. When connected to an XP or Windows
Server 2003 host, WinConnect supports 24 bit
color. The maximum for a Windows 2000 host is
256 colors.
By default, XP and Windows Server 2003 support
a maximum of 16 bit color. You must use REGEDIT
to enable 24 bit color.
Use Start/Run and type in the command "regedit"
and hit the enter key.
Browse to:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Terminal
Server\WinStations\RDP-Tcp
On the right hand pane, highlight the ColorDepth
key and right-click. Select Modify and change
the "Value Data" field to 4.
|
32. |
How
do I place multiple terminal servers behind a
firewall?
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 http://support.microsoft.com/default.aspx?scid=kb;EN-US;187623
.
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.
|
|
|