Axel AX3000 80, User Manual

Page: 31 / 224

Initial Power-On
AX3000 Models 80 and 85 - User's Manual
21
Method 2:
If DHCP does not supply these values the thin client
will try to resolve a ‘hardwired’ DNS name
("axrmserv" or "axrmservssl").
If one of these 2 names is resolved the thin client knows the AxRM server IP address. When
resolving "axrmsrvssl", the thin client assumes the TCP port is 443 and the protocol is "XML-
SSL". For "axrmsrv", the TCP port is 80 and the protocol is "XML".
Method 3:
If neither "axrmservssl" nor "axrmserv" cannot be resolved, as a final attempt the thin client
assumes AxRM resides on the same PC as the DHCP server (TCP port 80 and protocol XML).
Method 4:
Only used when the location (IP address or name) and the TCP port of the AxRM machine are
specified within the AX3000 Set-Up. See Chapter 3.6.2. (This is not viable for setting up brand
new thin clients, as required AxRM PC data to be already entered in the thin client setup)
The IP address of the AxRM server and the location method used is shown on the status line:
Auto-Conf. / DHCP: aaa.bbb.ccc.ddd / AxRM (1): www.xxx.yyy.zzz:nnnn.......
The thin client sends an 'auto-configuration' request to AxRM every 5 seconds. If no response is
received after 10 attempts the thin client starts the mechanism again, i.e. from stage 1.
This loop stops when either AxRM responds or if a user presses any key on the keyboard, causing
the normal interactive quick setup to run.
2.2.4 - Stage 4: Receiving the Firmware File
A dialog box on the thin client screen provides the status. From this stage the mechanism cannot
be aborted.
Note that firmware downloading may not have been specified by AxRM, in which case the
procedure passes directly to stage 5.
The dialog box is as shown:
After having received the firmware the thin client reboots automatically and re-runs stages 1, 2 and
3 before passing on to stage 5.