----------------------
Lantronix
----------------------
Comm Port Redirector for
----------------------
Windows NT/2000/XP
----------------------
Software Release Notes
----------------------
Redirector Version 3.1.0.1
Secure Redirector Version 3.1.2.1
December 6, 2005
Copyright (c) 1995-2005, Lantronix
This document describes the Lantronix Modem Redirector for the Windows NT
software release.
New Features
============
o "Raw mode" port setting puts the redirected port in raw mode: no
configuration or status information is sent between the PC and the server.
o A reconnect limit port setting can be specified. This restricts the
number of reconnection attempts if 'server reconnect' or 'timeout
reconnect' is enabled. The default of zero means no limit.
o The 'server reconnect' and 'timeout reconnect' behavior has been
modified. If the initial connection attempt fails, it does not retry
the connection; it only retries on a broken connection.
Version 3.0.#.1
o Comm Port Redirector now comes in two flavors. The regular redirector
and the secure redirector. The secure redirector uses the AES encryption
algorithm.
o Now supports immediate sends.
Resolved Problems
=================
o Redirector Timeout Reconnect causes application to hang under certain
circumstances.
o Redirected Com ports were not shown in the Windows Device Manager or
add modem wizard.
o Non-admin users under Windows 2000 could not use the redirector
because of registry access violations.
Version 3.0.#.1
o Redirector would crash if using no net close on a raw connection
when opening and closing while data is moving.
o A memory leak was fixed. This leak occurred when an attempt to redirect
a port failed.
Version 3.0.#.2
o Redirector would close ports immediately after opening if the baudrate,
set via system calls, was set to rates higher than 115200.
o Support for Windows 95/98 has been removed,
Version 3.0.#.3
o Com Ports added by Redirector did not show up in the add printer wizard.
Version 3.0.#.4
o Redirector would bug check (crash with the Blue-Screen-Of-Death) with
MULTIPLE_IRP_COMPLETE_REQUESTS when run on a multiprocessor PC or a PC
running hyperthreading. This has been fixed.
Version 3.1.#.1
o When No Net Close is selected, the first opening of the port allowed
the sending of breaks. When the port was closed then reopened, breaks
were not sent. This has been fixed.
o When No Net Close is selected, a connection was made, and traffic was
initiated. If the connection was closed, then reopened while the traffic
continued, there were times where the reopened connection would no longer
receive data. This has been fixed.
Known Problems
==============
The maximum number of com ports that can be successfully redirected using
Windows NT and Windows 2K is 64.
When forming a connection to a MSS100 running code V3.6/4, the ability
to control DTR and RTS does not work correctly. This problem has been
corrected in the current MSS100 beta code.
Applications that open a comm port more than once will not work. This
includes packages such as Procomm that have separate data and fax
channels. See the application notes below.
Certain modems profiles will disconnect the redirector session when
the modem init string is sent. If you notice that the redirector
connects and then disconnects right away then use the Modem Control
Panel to change your modem profile to one of the Standard modem types.
This tells Windows to send a generic init string which does not
override the LRS init string.
Faxing works with fax class 2 only and the modems noted below.
Requirements
============
The following things are required to run the redirector:
1. A Lantronix Device Server.
2. A PC running NT 4.0 or higher running on an IP network. The IP
stack needs to be configured properly.
Windows NT Application Notes
============================
The following packages have been tested against the Windows NT redirector:
32-bit applications
-------------------
o HyperTerminal for NT 4.0
Works.
o Dialup Networking for NT 4.0
Works.
o pcAnywhere32
Works.
o Reachout 7.0 for NT (4.0)
Works, but a little spastic connecting and reconnecting.
o Terminal for NT 3.51
Fax modem table
===============
The following fax modems have been tested against the redirector and
Delrina WinFax PRO 8.0:
Fax Modems that don't support Class 2
-------------------------------------
Intel SatisFAXtion Modem/400e PCFM6501
Hayes Smartmodem OPTIMA 288
USR Sportster 28.8, 33.6, 56K (supports 2.0, not 2)
USR Courier V.Everything (supports 2.0, not 2)
Table of Fax Class 2 modems which have been tested (Y = works, N = doesn't)
---------------------------------------------------------------------------
MSFax Delrina WinFax PRO 8.0
----- ----------------------
SupraFax Modem 28.8 Y Y
Bocamodem V.34 Y Y *4
BestData Smart One 2834FX Y Y *1
Zoom V.34 Y Y *1
ZyXEL U-1496E Plus V.32b/FAX/VOICE Y Y *2
MultiTech MultiModem MT2834 Y Y *2
PPI 28.8 v1.53 N Y
Digicom Scout 28834e N Y
AT&T DataPort 28.8 N N
NetComm Automodem E7F Y *3 ?
Banksia PRO 34 Y *3 ?
Zoom Faxmodem 56KX dial modem V.90 ? Y *5
*1 You must delete the &c1 from the Delrina's modem init string for this modem.
*2 At the end of the fax transmition Delrina reports a "cannot send data
to hardware" message even though the fax was sent successfully.
*3 These are apparently Australian modems that are reported by users to
work. They have not been tested in-house.
*4 It's been reported that Boca no longer supports fax class 2 in any of
their modems, so don't expect faxing to work if you buy a new one.
*5 This has been reported in from the field as "working great" but has
not been tested first-hand. Caveat emptor.
Download Driver Pack
After your driver has been downloaded, follow these simple steps to install it.
Expand the archive file (if the download file is in zip or rar format).
If the expanded file has an .exe extension, double click it and follow the installation instructions.
Otherwise, open Device Manager by right-clicking the Start menu and selecting Device Manager.
Find the device and model you want to update in the device list.
Double-click on it to open the Properties dialog box.
From the Properties dialog box, select the Driver tab.
Click the Update Driver button, then follow the instructions.
Very important: You must reboot your system to ensure that any driver updates have taken effect.
For more help, visit our Driver Support section for step-by-step videos on how to install drivers for every file type.