User's Manual

ME BreadCrumb User Guide Rajant Corporation
- 49-
6.1.2 BREADCRUMB DEVICE CANNOT CONNECT TO BCWN
Table 5. BreadCrumb Device Cannot Connect to BCWN
Problem Resolution
Discharged batteries can cause the BreadCrumb device
to appear to power up, but not be able to establish
connectivity to the BCWN.
When deploying the BCWN, ensure that the batteries
should be fully charged.
On rare occasions, the PCMCIA cards within a
BreadCrumb device can work loose, resulting in the
BreadCrumb device’s not being able to establish
connectivity to the BCWN.
Open the BreadCrumb device’s case and verify that the
PCMCIA cards are securely seated in the PCMCIA
slots.
When using external antennas, faulty cable connections
or crimped cables can result in difficulty establishing
and maintaining network connectivity.
Check antenna cables and their connections to the
BreadCrumb device.
6.1.3 BCADMIN ISSUES
Table 6. BCAdmin Issues
Problem Resolution
The screen is red and empty. The BCAdmin workstation does not have a 10.x.x.x
address, which is required to administer the BCWN.
The screen is black and empty. BCAdmin is unable to communicate with any
BreadCrumb devices. Verify that a personal firewall
application such as BlackICE or Zone Alarm is not
preventing BCAdmin from communicating with the
BreadCrumb devices. The Window XP Service Pack 2
built-in firewall also blocks communications with
BreadCrumb devices by default.
BreadCrumb boxes are turning red on the screen. This means that BCAdmin has been unable to
communicate with BreadCrumb device for 60 seconds.
This could be due toe several factors:
LOS obstructions
Dead or failing BreadCrumb battery.
BreadCrumb device is rebooting.
Encryption settings are mismatched between BCAdmin
and the affected BreadCrumb devices.
Clicked ‘BreadCrumb Properties’ from the
BreadCrumb box’s popup menu, but nothing happens.
An old version of BCAdmin is being run with a new
version of Java Runtime Environment (JRE). Install
the latest version of BCAdmin.