Applies to: Intellian FB250 only, 2013F2-UM0221-V1_03, copyright 2013. The shared manual’s FB500 hardware/class/data rates and later editions are excluded. This archived baseline does not establish current FleetBroadband activation, coverage, tariffs or firmware compatibility.
Work through these checks
Confirm local access and device identity
Use the owner’s existing Web Console address and credentials. The original default is http://192.168.1.35 only if unchanged; do not reset to recover it. Read Settings → Terminal Info → Information for software and Model ID. Setup → Terminal Info is a different view showing signal, temperature, GPS acquisition and registration context. Preserve the result of each authorised view.
What the result means: A local response confirms management access, not satellite registration or paid data readiness. Distinguish a failed local login from a visible satellite-state message before escalation.
Separate tracking, registration and active data
Read ADU and REGISTERED together with CS/PS/GPS icons. ADU green steady is lock, while REGISTERED blinking amber is voice-only readiness and blinking green packet-data-only readiness. The console can explicitly report Registered to Network but no active data connection exists. That is distinct from a local-access failure or a registration error; keep the full message without following its invitation to activate data.
What the result means: Antenna lock, voice/data registration and an active PDP context are separate evidence. Note the first unconfirmed stage; a green lamp alone is not a reason to start traffic or change the installation.
Preserve existing connection and diagnostic records
View the existing Data → Connection page. For an already connected context, the manual shows APN and assigned public IP; do not activate or disconnect a context. Under Settings → Terminal Info, keep the event/error Logs and separate Call Log with existing call/data history. Call/Data Usage is a total counter with a Clear control; read it without clearing. Correlate existing entries with the original fault time, not a newly generated session.
What the result means: Support receives the failed stage and its existing timeline. A context entry, historical call/session and total counter answer different questions; none alone proves present application delivery or an exact bill.
When to stop and get help
Preserve working communications. Do not start or disconnect PDP sessions, alter APN/Always On/router/security settings, select satellites, restart or use safe mode. Do not approach or disturb the powered antenna/coax; installation, damage and persistent red faults require qualified service. Current service restrictions require the actual provider.
What to tell support
Privately retain model/software, fault time, local-page response, named LED patterns, CS/PS/GPS state, existing context state and full matching event/error text. Keep existing call/data history and counters without Clear. Position, IMEI, IMSI, antenna serial, addresses and credentials belong only with authorised support.
Original troubleshooting guidance based on the official sources below. Menu names can change. This is an independent guide, not a manufacturer service bulletin or a bench-tested repair.