Two methods can be used to fix this problem:
The AxRM tool uses the following commands:
- PING: checking terminal
availability,
- RSH: running administration
commands,
- TFTP: downloading firmware,
- REMOTE ACCESS: taking
control of a terminal,
- BOOTP: "repairing" a
terminal when the firmware is lost.
If you have a firewall there is a high chance
that some services will be blocked by default.
There are three ways to resolve this issue.
- Connect the terminal to a non-firewalled PC, (maybe direct with crossover
Ethernet cable) there by avoiding the firewall.
- Turning off the firewall for the duration of the download
- Enabling AxRM to work through the firewall. This is covered in more
detail below.
Enabling PING
The ICMP protocol must be allowed.
Enabling RSH
From the PC/Firewall, RSH requires an outgoing
port, and an incoming port. When 'RSH' is
allowed within the firewall:
- an outgoing port is enabled (514),
- along with a range of incoming ports
starting at 1024. (or another value is the
'Local RSH Port Base' default valued had been
modified)
Enabling REMOTE ACCESS
Two outgoing ports must be enabled:
- 4096: 'Set-Up via Telnet'
function
- 4098 : 'Remote Control'
function.
Enabling TFTP
Enable port 70 - this is the port TFTP listens
to.
Enabling BOOTP
Enable port 69 - this is the port TFTP listens
to.
If this doesn't happen please call Axel with any error messages given.
Top
AxRM
Installation Problem (fraplus1.ocx and
btnplus1.ocx components)
During the installation of
AxRM the following error messages may be seen:
An error occurred while registering the
file c:\windows\system32\FraPlus1.ocx
An error occurred while registering the
file c:\windows\system32\BtnPlus1.ocx
This error is due to an incompatibility of these
components with the new Windows function 'DEP'
(Data Execution Prevention)
Note: Data Execution Prevention is a set
of hardware and software technologies that
perform additional checks on memory to help
prevent malicious code from running on a system.
It's only used on some CPU processors.
To install AxRM it
is necessary to
restrict the
function of DEP:
In the control panel click on "system". On
the "Advanced" tab, under Performance, click
"Settings" . On the "Data Execution
Prevention" tab select the option "Turn on DEP
for essential Windows programs and services
only". Reboot the server to make this change
take effect.
The AxRM installation will now proceed as normal.
Top
SQLDMO.DLL Installation Problem
During AxRM V3 installation, the SSQLDMO.DLL installation may fail. This can be fixed by installing the "Microsoft SQL Server 2005 Backward Compatibility"
package.
Packages can be downloading from the Microsoft site:
http://www.microsoft.com/downloads/en/details.aspx?displaylang=en&FamilyID=b33d2c78-1059-4ce2-b80d-2343c099bcb4
In event of problem these packages are also available from the Axel web site:
- Package X86
- Package X64
Install the package. (Ensure that 'SQL Distributed Management Objects' is selected.)
Top
Unable to Use 'Remote Access' Function
The two possible problems are the following:
1 - 'Remote Access' option and related icon are
inaccessible (greyed out)
The target terminal is too old. This function is not available on these discontinued products:
- AX3000 Models 55 & 65E
- AX3000 Models 60 & 60E
- AX3000 Models 65, 65B & 65E
2 - Error Message "Remote Control Service is not enabled on the Axel device"
This message indicates:
- Either the current terminal firmware doesn't offer this function.
→ Update the terminal firmware (minimum version: 0632b).
- Or the remote access is not enabled at the terminal set-up level.
→ Enter the terminal set-up and go to [Configuration]-[Advanced]-[Remote
Control]
- Or the connection is blocked by a firewall.
→ Ensure port 4098 is enabled
Note: to check the firmware revision
or to enable the remote control service, use the
'Set-Up via Telnet' function (enabled by default
on all terminals)
Top
