Router connection fails or API authentication is rejected

Prerequisites and authority

Start with read-only checks and authorized records. Capture evidence before changes. Stop and escalate when data replacement, financial changes or wider outages are possible.

Router connection or API authentication fails

Basic

Confirm the saved management address, port and router power. Check whether one router or all routers at a site are affected.

Intermediate

Test TCP API reachability from the BryanNet host and runtime. On Windows a scoped test example is:

Test-NetConnection 10.200.0.11 -Port 8728

The address is illustrative. A successful TCP connection does not authenticate the API user. A timeout suggests routing/firewall/path failure; a refused connection suggests service/port; rejected login suggests credentials or policy.

Advanced

Inspect source-address restrictions, input firewall ordering, API service state and dedicated account rights. Test VPN/return routes if remote. Check whether credentials changed outside BryanNet.

Do not disable the firewall or expose the API publicly as a diagnostic shortcut. Correct the narrow rule, route or credential mismatch and retry through BryanNet.

Verify authentication, a supported operation and later synchronization. If bootstrap still fails, retain its per-component error and escalate with firmware, provider type and redacted configuration evidence.