Applies to: Hughes 9203, H69044 Revision 6 only; not 9202M or 9211.
Work through these checks
1. Check the local path
Open the installed terminal address from the affected client; the documented default is http://192.168.128.100. If it does not open, verify the Ethernet/WLAN connection and ask the administrator to compare the client subnet with the actual terminal address. If another authorized client opens the page, compare the two client configurations before touching the antenna. A local page that opens lets you proceed to the network check; it does not prove internet service.
2. Read network attachment
On Home, record registration and both attachment fields. PS means packet-switched network attachment for data; CS means circuit-switched attachment. These are separate from a PDP context, the data session used by a client. If registration or PS attachment is missing, give that state to the provider rather than editing the client’s session. If PS is attached, inspect the session next; do not interpret CS alone as a working data connection.
3. Read the IP mode before interpreting sessions
First read the installed Netmode without changing it. In NAPT, multiple clients share one PDP session and one global address: inspect that shared session and the local client path; do not demand an Owner entry for every client. In NAT, compare the affected client with the relevant context Owner. Relay supports only one connected client and changes its address through DHCP when the context changes. If a session is missing or rejected, record the mode, service and complete error for the provider before changing APN settings. Do not start Streaming merely as a test.
When to stop and get help
Keep passwords private. Avoid a factory reset while the failed stage is still unclear.
What to tell support
Give the administrator or service provider the failure time, terminal software version, Ethernet/WLAN path, client IP address, installed terminal address, registration/PS/CS states and affected session Owner. Include the complete error text and whether another authorized client works. Send screenshots and logs privately with passwords removed; retain the original evidence before changes. Include the installed Netmode; context Owner is relevant only where that mode uses a client-specific context.
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.