Three auxiliary ports are provided on the AX3000 (2 serial ports and 1 parallel port). Each of these ports is independent and can be accessed through different network protocols.
An LPD printer is set both at the AX3000 level and at the
Windows level (TCP/IP Printing).
AX3000 Level:
An LPD printer can be configured with 3 parameters:
- an IP address (the AX3000’s IP address),
- an identifier for the auxiliary port (character string),
- an optional filter to pre-process the file before printing
(but generally this processing is done at the operating system level).
Enter the AX3000 Set-Up and select [Configuration]-[Aux.
Ports]-[xxx]. In the displayed box, set the "Associated Service"
to "LPD", then select "Net Service Parameters" and press
<Space>.
The displayed box allows the LPD protocol to be customized. The following
parameters must be set:
- Printer Port Name:
It's port identifier
- NL=CR+NL Filter:
Always No
Windows Level:
To add a printer, select the 'Add printer' icon (in the 'Start'-Settings'-'Printers' menu).
Within the displayed dialog box, select 'Local printer' (Disable the Plug-And-Play detection). Click on
'Next'.
Within the next dialog box, select 'Create a new port' and select 'LPR
Port'. Click on 'Next'.
Note: if 'LPR Port' is not available, you need to install 'Print Services for Unix'.
Finally within the next dialog box, enter the two requested parameters:
- name or address of the server providing LPD: AX3000 IP address
- name of printer or print queue of that server: this is the 'Printer Port Name' AX3000 Set-Up parameter.
When this printer is added, all print jobs sent to this printer are automatically redirected to the AX3000.
Top
Using RDP or ICA Redirection to Connect a Printer
A printer controlled by the RDP or ICA Redirection protocol is only set on the AX3000
level (no setting required on Windows).
Enter the AX3000 Set-Up and select [Configuration]-[Terminal]-[Session X]. In the displayed box select
"Printer" and press
<Space>.
The displayed box allows the redirectionprotocol to be customized. The following
parameters must be set:
-
Used Port: select Parallel, AUX1 or AUX2
-
Printer Name: up to 16 characters
-
Printer Driver: enter the printer driver name. Take care to spaces or
special symbols. The name is not case sensitive.
For example: HP Laserjet 4P
-
Time_Out: number of seconds waited by the terminal in event of a printer
incident (no paper, off-line). After this time, the incident is reported to
Windows.
Note: if the printer driver is not correct (or not installed on Windows) the
printer is not created.
Top
Using RDP Redirection for Addressing a COM Port
This method creates up to two COM ports at the client/terminal level that that
particular user/RDP session can access. This enables the user to access any
devices attached to his AUX1 or AUX2 ports through the standard COM1/COM2 port
mechanism (and install any corresponding device drivers)
For example this could be used to map terminal AUX1 port to COM1. The user can
now attach any serial device (scales, scanner, printer, display, cash-drawer,
etc) to AUX1 and the application will access the device as COM1.
The redirected ports are local to the RDP session/user, so the serial device/COM
port cannot be accessed by any other user. This is to simulate COM ports on PCs
- one PC cannot normally access the COM port of another PC.
To redirect an AUX port, enter the AX3000 Set-Up and select
[Configuration]-[Terminal]-[Session X]. In the displayed box select "Aux. Ports
Redirection" and press <Space>.
The displayed box allows AUX1 and AUX2 to be redirected as COM1 and COM2
respectively.
Note 1: the Redirection protocol is only available for AX3000 models 75 on Windows
2003.
Note 2: no further software is required.
Top
Using ICA Redirection for Addressing a COM Port
This method creates up to two COM ports at the client/terminal level that that
particular user/ICA session can access.
To redirect an AUX port, enter the AX3000 Set-Up and select
[Configuration]-[Terminal]-[Session X]. In the displayed box select "Aux. Ports
Redirection" and press <Space>.
The displayed box allows AUX1 and AUX2 to be redirected.
When redirected, the terminal COM1 and COM2 ports must be remapped to Windows server COM ports. This remap not automatically performed. It must be done from the terminal, through the "change client" or "net use" commands.
Example: the Windows COM4 port is remapped to the terminal COM1 port
net use com4: \\client\com1:
or
change client com4: com1:
This enables the user to access any
devices attached to his AUX1 or AUX2 ports through the standard COM1/COM2 port
mechanism (and install any corresponding device drivers)
For example this could be used to map terminal AUX1 port to COM1. The user can
now attach any serial device (scales, scanner, printer, display, cash-drawer,
etc) to AUX1 and the application will access the device as COM1.
Note : the redirected ports are local to the ICA session/user, so the serial
device/COM port cannot be accessed by any other user.
Top
Using a Virtual COM Port Third Party Software
This method creates new virtual COM ports at the
server level that all users can access.
For example the server probably has a local
hardware COM1 and COM2 port. This method creates
for example COM5 and COM6 etc - and these COM
ports are 'logically' connected to the remote
serial AUX ports on one or more the Axel
terminals.
The serial devices are available to everyone,
seen from the server and any application as
COM4/COM5 - but physically may be spread around
the WAN attached a various Axel terminals.
(The port redirection software makes the
connection between for example COM4 and the
terminal's serial port using the IP address and
TCP port number of the serial port).
Several Windows drivers are available. Axel have
qualified Serial/IP from Tactical
Software.
Top
Using the TCP/IP Socket Method
Note: this method can only be used if you have the full control of the software which handles the device.
The method lets your Windows software open a "socket" (i.e. a network connection) to the AX3000 auxiliary port. The socket parameters are the AX3000 IP address and the "TCP port" of the AX3000 auxiliary port.
Note: the "TCP port" is a numeric value, which identifies the auxiliary port. As three auxiliary ports are provided on the AX3000 the IP address is not enough to identify each auxiliary port.
Through the AX3000 setting the auxiliary port use the "rtty" service, and you are prompted to enter a TCP port number (default 2048) If multiple auxiliary ports are controlled through this method each auxiliary port must be associated with a unique TCP port.
Top
Problems Connecting to Windows 2003 SP1
There is an incompatibility with M75 terminal firmware
pre rev 0416c3 (terminals shipped prior to May
2005) and Windows 2003 Service Pack 1.
Please contact Axel for firmware patch.
Top
Connection error: Invalid Client - Total transition abort
At the RDP connection time, in event of licence
issue the following message can be displayed:
"Invalid Client - Total transition abort".
The three possible reasons are:.
- No more TSE Cal are available: new CAL
must be bought.
- The Axel terminal had been already
connected to another TSE server. In this case,
the licence token stored by the Axel terminal
is not compliant with this server. To reset
the Axel "Licence Store", enter the AX3000
Set-Up, select the '?' on the upper-right
corner and press <Ctrl><Alt><Shift><R>. The
displayed dialog box allow you to delete the
current licence token(s).
- The Windows server doesn't convert a
temporary licence to a 'standard' licence. The
server must be updated:
- for Windows 2003, install Service Pack 1.
- for Windows 2000, please consult
http://support.microsoft.com/default.aspx?scid=kb;en-us;827355
Top
No Connection to Windows
Several causes may explain why the AX3000 cannot establish a session to the
Windows Terminal Server.
"Connecting to..." is displayed
- Check that the "good link" led located on the AX3000 rear panel is lit – if not check cables, hub, switch
etc.
- Check, through the AX3000 Set-Up, that the correct IP address is associated with the Windows
host. "Ping" the server from the AX3000 Set-Up, (select
[Diagnostics]-[ping]). In event of failure, check the network cables and the IP address with the network administrator.
If using DNS or DHCP try using a static IP address.
The session is automatically closed
or
The screens "flashes" and "Connecting to..." is displayed
- Check the IP address of the server the terminal is attempting to connect to
(through the AX3000 Set-Up).
- Check the "Terminal Service" is installed and enabled on the Windows host (only NT4 TSE, 2000 Server and 2000 Advanced Server support this service).
- Check the "License Manager" is available and can handle all RDP terminals.
"The server encryption level is not correct" is displayed
Check the AX3000 encryption level matches the server’s encryption level (from the terminal
select [Configuration]-[Terminal]-[Session
X], then 'General Parameters' and press <Space>) for the Windows server
(run the "Terminal Services Configuration" utility
on the 'Administrative Tools' folder).
"Invalid
Client - Total transition abort" is
displayed
See previous F.A.Q.
Top
Remote Configuration Failure: "TRAILER
LABEL NOT FOUND"
Description:
When a set-up file is sent to an AX3000 through the "rsh
setup_send" command, the error message Trailer not found" is
displayed.
Explanation:
This problem is due to the native Windows rsh command being unable to
send more than 10Kb over the network.
When the size of the "set-up" file (created by the "rsh setup_get"
command), is greater than 10Kb, the set-up file is cut and the last lines are
lost (and of course the last line END_AX_SETUP).
Two solutions are available to fix that:
- Using a set-up file less than 10Kb:
The size of the file can be decrease by removing lines beginning by a #
(these lines are commented out). To get directly a file without commented
lines, use the
"rsh setup_get_lite" command.
- Using another rsh command:
Other Windows rsh command are available. Please contact us
Top
LPD Print Jobs
can be Delayed for Several MinutesDescription:
When several LPD print jobs are spooled,
the first batch (about 10) are correctly processed but the others
may remain spooled for a few minutes before being processed.
Explanation:
This problem is due to the Window's "socket" management
(a socket is a TCP/IP connection).
Notes about LPD and TCP/IP:
- A TCP/IP connection (i.e. a socket) is established for each
LPD print job. When the LPD print job is completed, this TCP/IP
connection is closed (i.e. the socket is released).
- A socket is composed by 4 parameters:
local IP address / local TCP port / remote IP address / remote
TCP port
The local IP address is the Windows address , the remote IP address
is the Axel address and the remote TCP port is 515 (Axel LPD
service). The local TCP port value is given by Windows.
Note: to list the sockets in use invoke the netstat command
- When a TCP/IP connection is closed, the associated socket
is not immediately released. This socket is set in an intermediate
status (TIME_WAIT) for 3 minutes. During this TIME_WAIT status,
the socket is not available for another TCP/IP connection.
The problem is due to the "remote TCP port" socket
parameter. Only 11 TCP ports are available to process LPD print
jobs: from 721 to 731. When 11 print jobs are processed in less
than 3 minutes, the 11 associated sockets are locked (status ESTABLISHED
or TIME_WAIT). So the next print job will be delayed until a TCP
port is released.
The Windows default is for 11 ports (721-731) to be used. To
avoid this limitation, Windows must be set-up to use any TCP ports
greater than 1024.
Setting-up Windows depends on both the Operating System and
the installed Service Pack. For information on changing this setting
please read the article "Updated TCP/IP Printing Options
for Windows NT 4.0 SP3 and Later" on the
Microsoft
site (or on the Axel archive page).
Top
