Revision 7.10
2/28/2012
(i) Replace
dockserver.yourdomain.com
with
localhost
–
or
(ii) From a
root
account, omit
and simply type the
remainder of the line directly to the shell.
All the examples assume the the remote computer is on a linux platform. Everything
described here can be accomplished on a remote computer with a Microsoft
Windows Operating System, it's just harder. Many Microsoft Operating Systems
don't ship with the required TCP/IP command line tools. There are many third party
toolsets, both open source and proprietary, that the end user can obtain and install
to accomplish the required tasks (e.g.
putty
). It is
beyond the scope
of this
document and
Webb Research Customer Support
in providing assistance in these
selections and installations.
12.8.3 Checkout/Troubleshooting Sequence
Most of the problems that you encounter will involve misconfigured networking
components: name servers, NAT routing issues, and particularly Firewall issues. It's
important that one proceeds stepbystep and confirm the proper operation of each
component before proceeding to next component.
The Iridium RUDICS system simply delivers characters to and from the Glider to a
TCP/
IP socket
on the Dock Server. You strongest debugging technique is pretending to be a
Glider by executing:
telnet dockserver.yourdomain.com 6565
Any characters you type are sent to the the Dock Server in exactly the same manner
that Glider sends characters. Any characters sent by the Dock Server to the Glider
show up on your console.
The proper checkout sequence is:
1.
Follow the techniques in
Section 12.8.4 Checkout/Troubleshooting Procedures
in the
following environments:
1. Verify the proper operation of the Dock Server as a self contained computer,
i.e. make NO USE of any network connections. You will pretend to be a Glider.
Substitute
localhost
for
dockserver.yourdomain.com
.
Page 163 of 228
