Summary of NTRIP Communication Error Countermeasures｜8 Checkpoints When You Cannot Reconnect

Have you ever experienced communication troubles in RTK surveying such as “correction data cannot be received” or “cannot reconnect to NTRIP”? When NTRIP connections are unstable, the centimeter-level high accuracy you depend on cannot be utilized, and field work can be delayed.

NTRIP (Networked Transport of RTCM via Internet Protocol) is the international standard protocol for distributing GNSS correction data over the Internet. Users connect their rover GNSS receiver to the Internet via a mobile data connection or Wi‑Fi, access the NTRIP server (caster) of the correction service they subscribe to, and receive real-time correction data. In Japan, NTRIP-compatible high-precision positioning services are widely used across many fields, including the Geospatial Information Authority of Japan’s permanent GNSS reference station network and services provided by private companies. NTRIP is indispensable for realizing network RTK, but because it depends on Internet communication, if the server cannot be reached or the connection is dropped, high-precision positioning can be severely disrupted.

Typical causes of NTRIP connection trouble include input errors in connection settings, poor communication environment, failures or downtime on the correction service side, account issues, and malfunctions in the receiver (GNSS device). You can often infer the cause from error messages or status displays, but multiple factors may be involved, so it’s important to check each possible cause one by one rather than relying solely on inference.

This article organizes these points into eight items and explains them in order. By checking each item sequentially you can accurately isolate the cause and quickly resolve the problem. At the end, we also touch on a new RTK solution called “LRTK” that realizes stable positioning without complicated settings. If you are troubled by NTRIP connection errors, use this article as a reference to stabilize high-precision positioning in the field.

Contents

• Recheck connection settings

• Check the network environment

• Check the operational status of the correction service

• Check account information and usage status

• Check mount points and data reception status

• Check the GNSS receiver status

• Isolate the cause using other methods

• Consider alternatives when communication is difficult

1. Recheck connection settings

First, recheck the configuration information required for NTRIP connection. If there is even one input mistake in the NTRIP server’s hostname or IP address, port number, mountpoint name, user ID, or password, the connection cannot be established. The most frequent causes of communication errors are basic setting mistakes such as typos in the hostname, omitted port numbers, incorrect mountpoint names, and mixing full-width and half-width characters in IDs/passwords. For example, confusing the numeric “0” (zero) with the letter “O”, or accidentally including full-width characters in a hostname, are common. Compare the connection information provided by the correction service you subscribed to with your settings and confirm that every character is entered exactly as given. Note that mountpoint names may be case-sensitive, so be careful. Also check that no unnecessary spaces have been inserted into input fields. If authentication errors like “Unauthorized” or messages such as “Mountpoint not found” appear, first suspect mistakes in these setting values. Returning to the basics and carefully checking each item one by one is actually the simplest and most effective troubleshooting.

2. Check the network environment

Next, check the network connection status of the device receiving NTRIP. If you are connected via a mobile router or smartphone tethering, check that the signal is strong. If the signal is weak, moving the device to a different location or restarting it may improve the situation. If you are using a mobile router, be aware of battery depletion—confirm that the power has not switched off and communication has not been interrupted. Outdoors, turn off unnecessary Wi‑Fi connections to ensure you are using the mobile data connection. If you are using smartphone tethering, check the settings to ensure it does not automatically stop, so that communications remain stable. Be careful that your device does not automatically connect to public Wi‑Fi on site and lose Internet access. Also check that the GNSS receiver or tablet has obtained a proper IP address from the network (for example, if the device’s local IP remains 0.0.0.0, communication is not established). Don’t forget basic checks such as whether the SIM card’s data allowance is exhausted and whether airplane mode is off. If you are using mobile data directly in the GNSS receiver, also verify that the SIM card’s APN (access point name) settings are correct. Poor communication environment is a major cause of NTRIP errors, so first review signal conditions and the foundation of your network connection. It’s also effective to check the site’s communication environment before going to the field: if the measurement site is out of service range, you cannot receive NTRIP corrections at all, so secure communication means in advance.

3. Check the operational status of the correction service

Also check whether there are problems on the NTRIP correction service side. Verify through official notices or status information whether your service provider is performing maintenance or experiencing communication outages. If the service is down, nothing you do on the user side will allow a connection, and you must wait for recovery. It is also important to check whether your contracted correction service subscription period has expired (renewal may be required). Some services limit their coverage area, and if your work site is outside the service area, the connection cannot be established. If you are near the boundary of the provider’s coverage, confirm that your work location is within the supported area. Some services publish real-time operational status or outage information on their websites. If you can quickly determine that the problem is on the service side, you can avoid wasting time troubleshooting on the user side. If other devices using the same correction service cannot connect either, the problem is likely due to the service provider. Understanding the service-side status helps you determine whether the trouble is caused by the user side or the service side.

4. Check account information and usage status

Checking account-related issues for the NTRIP correction service is also essential. First, reconfirm that the user ID and password you are using are correct. Even if there are no input errors, most services will refuse connections if the same account is used simultaneously on multiple devices. If another device is logged in, log it out once and then reconnect. Be sure to verify that the subscription for the account has not expired. If payment or contract renewal is pending, the account may be deactivated and cause communication errors. If a single ID is shared within your organization, take care to avoid simultaneous use. Account-related issues often appear as errors like “Unauthorized,” so pay special attention when such messages appear. If the problem persists, contacting the service provider to check the account status can be effective. Keep track of renewal dates to prevent suspension of service due to expiration.

5. Check mount points and data reception status

Even if you appear to be connected to the NTRIP server, it is important to confirm whether correction data is actually being received. The device or application display may show “connected,” but if no data flows for a period of time, the reference station side (correction service) may have stopped data transmission. If you selected the wrong mountpoint or the chosen reference station is temporarily suspended, you may be connected but not receiving data. If you can switch, try another mountpoint to see if you can receive data. Sometimes simply disconnecting and reconnecting resumes data reception. If that doesn’t help, try restarting the receiver or the application. Also be sure to check the content of any error codes or messages. For example, if “Mountpoint not found” appears, the mountpoint name may be specified incorrectly; if “Timeout” or no response appears, it suggests a network or server-side issue. It’s also important to select a mountpoint that matches your receiver’s supported frequencies. If you are using a single-frequency receiver (L1 only), select correction data intended for single-frequency receivers (e.g., MSM4), while multi-frequency receivers should use multi-frequency data such as MSM7. A mismatch between the receiver and the correction data format can result in a connection that cannot fully utilize the correction information. If correction data is being received but a fix is not achieved, discrepancies in the reference station’s reference coordinates or the geodetic datum may be the cause. If you are using your own base station, recheck the coordinate values and the datum configured at the base station. In short, do not rely solely on the connection status display—check whether data is actually being received, and change mountpoints or reconnect as necessary.

6. Check the GNSS receiver status

In addition to NTRIP, check the condition of the rover GNSS receiver itself. If the receiver cannot sufficiently capture satellites, reception of correction data via NTRIP may not start. For example, if the device display stops at “Wait for GGA” during NTRIP connection, the reference service is waiting because it has not received the rover’s current position information. VRS-type correction services require the rover to send its own position (GGA message). Normally this transmission occurs automatically, but if the setting is disabled, correction data will not be delivered. Confirm that GGA transmission is enabled in the NTRIP client settings. This situation can occur when the rover has not yet fixed its own position. As a countermeasure, review the GNSS antenna placement and orientation to ensure a clear sky view and adequate satellite reception. Inspect the antenna cable for looseness or breakage, and check that the receiver has sufficient power or battery. Once the rover can stably determine its position, it will send GGA data to the NTRIP server and correction data should begin to flow. Therefore, improving satellite reception environment and the receiver’s hardware condition are important checkpoints.

7. Isolate the cause using other methods

If possible, try other methods to isolate the location of the problem. For example, use RTK software on a PC or an NTRIP client app on a smartphone and try to obtain correction data with the same connection information. If another device can successfully connect to NTRIP, suspect a setting error or hardware fault in the original device or application. Conversely, if the same error occurs on other devices, the problem is more likely due to a service-side outage or account issue. If you have the capability, try connecting via a different Internet line as well. For example, try a SIM card from another carrier or connect via a different Wi‑Fi network to see if the problem is resolved. This helps verify whether the trouble is due to a specific line environment (firewalls, proxies, etc.). Trying multiple approaches will allow you to narrow down the cause more accurately.

8. Consider alternatives when communication is difficult

In environments where NTRIP communications are extremely difficult, consider alternative high-precision positioning methods. For example, in mountainous areas or disaster sites where mobile networks are out of range, you can set up your own mobile base station (local reference station) and transmit correction data via radio. Alternatively, if real-time positioning is not essential, switch to post-processing (PPK: Post-Processing Kinematic) by recording GNSS observation data and performing precise positioning later in the office. In Japan, there are also systems that receive correction information directly from satellites without using the Internet, such as the centimeter-class augmentation service (CLAS) provided by the QZSS “Michibiki.” Having such alternatives prepared allows you to continue positioning work even if NTRIP is unavailable.

Furthermore, new solutions designed to make RTK positioning simple and reliable in the field have emerged. One such solution is LRTK (a smartphone-mounted high-precision GNSS positioning device). LRTK combines a smartphone with a small GNSS receiver and, using a dedicated app, automatically acquires correction information and performs high-precision positioning with a single tap. It is designed to enable centimeter-level positioning without requiring complex NTRIP connection settings. The typical setup mounts the smartphone and receiver on a dedicated monopod, allowing stable point measurement by a single operator. Where previously expensive, large surveying instruments required two people to operate, LRTK enables one-person surveying with a lightweight smartphone-mounted system. Field users who have adopted LRTK report being able to measure many points quickly by one person and dramatically reducing surveying time.

The greatest feature of LRTK is its extremely simple field operation. By pressing the measurement start button on the dedicated smartphone app, the app automatically acquires correction information and applies position corrections. NTRIP settings and switching to base-station modes can be done intuitively in the app, so users can begin operating without difficult settings or specialized knowledge. Coordinate system settings required for surveying (support for JGD2011/2022 and geoid height conversion) are completed within the app, so there is no need to consult height conversion tables in the field.

In terms of accuracy, LRTK matches the performance of conventional high-cost surveying equipment. It supports multi-frequency GNSS and multi-GNSS reception (GPS, GLONASS, Galileo, Michibiki, etc.), and under good conditions achieves horizontal accuracy of a few centimeters (a few in) and vertical accuracy of a few centimeters (a few in). It also has a function to average measurement data, and static measurements can achieve accuracy below 10 mm (10 mm (0.39 in)). In addition, LRTK supports the QZSS “Michibiki” centimeter-class augmentation service (CLAS), allowing reception of corrections via satellite even where mobile communication is unavailable.

By introducing LRTK, tasks that previously relied on specialized surveying equipment and skilled personnel can be carried out easily by in-house staff. Being free from complicated equipment operation and connection troubles allows field teams to concentrate on the actual measurement tasks, which is a major benefit. LRTK, which makes high-precision positioning more accessible, is attracting attention as a new tool supporting DX across a wide range of fieldwork from civil engineering surveying to disaster investigations.

Above, we introduced eight checkpoints to verify when NTRIP connection trouble occurs. When you encounter NTRIP errors in the field, calmly go through the points introduced here in order to identify the cause and achieve rapid problem resolution. If correction information can be received stably, the efficiency of field work using high-precision positioning will improve dramatically. By familiarizing yourself with these checkpoints in advance, you can respond calmly when trouble occurs and minimize time loss on site.