7 Basic NTRIP Error Countermeasures: Causes of Connection Failures and How to Fix Them

Have you ever been troubled on site operating RTK positioning by issues such as "unable to receive correction information" or "cannot connect to NTRIP"? In high-precision positioning, correction data is received from a reference station via a protocol called NTRIP (Networked Transport of RTCM via Internet Protocol), but if this connection does not work properly, you cannot take advantage of the centimeter-level positioning accuracy and work will be interrupted.

This article explains the main causes of NTRIP “unable to connect” issues and seven basic countermeasures to fix them. Even if an NTRIP connection problem occurs during RTK surveying in the field, by checking each item one by one rather than relying on guesswork, you will be able to quickly isolate and resolve the issue. At the end of the article, we also introduce a new solution called LRTK, an iPhone‑mounted GNSS high‑precision positioning device that removes the need for these complicated settings and enables easy high‑precision positioning on site.

Table of Contents

• Check connection settings

• Check the communication environment

• Check the status of the correction service

• Check the data reception status

• Check the GNSS receiver and satellite reception status

• Isolate the cause using alternative methods

• Consider alternative methods if NTRIP is not feasible

• Summary

1. Check the connection settings

Typographical errors in the host name (IP address), port number, mount point name, user ID/password required for NTRIP connections are the most frequent cause of connection problems. Even a single-letter misspelling can prevent you from connecting to the server, so first check whether your configuration contains any mistakes.

As a solution, it is important to accurately recheck the connection information provided by the correction service provider. Carefully verify one by one that the hostname is spelled correctly, that the port number has been entered as specified, that the mount point name uses the correct letter case, and that the user ID and password do not contain any full-width characters. Pay particular attention to hostname typos and omitted port numbers, as these are common mistakes.

If your credentials are incorrect, you may see an "Unauthorized (authentication failed)" error when connecting. Also, if you specify a non-existent mount point name, you may receive a message such as "Mountpoint not found" and be unable to connect. When such error messages appear, immediately check for any spelling mistakes or input errors.

2. Check the communication environment

Next, check the mobile station’s Internet connection status. Verify that the GNSS receiver and its control terminal are properly connected to the network via a mobile data connection or tethering. If the signal from a mobile router or smartphone is weak, try changing location to improve reception or restarting the device. When working outdoors, turn off unnecessary Wi‑Fi connections and ensure the terminal is definitely using the cellular network to access the Internet. Be aware that devices can automatically connect to open Wi‑Fi networks and become unable to access the Internet.

Whether receivers and tablet devices are correctly obtaining an IP address on the network is also an important checkpoint. For example, if the local IP displayed on the device’s status screen remains “0.0.0.0”, it indicates that it is not connected to the network. In that case, review the mobile router or tethering settings and perform the network connection process again on the device to re-acquire an IP address.

Also, as basic checks, double-check whether the SIM card's contracted data allowance has reached its limit and whether the device is in airplane mode. It's not uncommon for a surprisingly simple oversight to be the cause.

Note that in environments such as construction sites in mountainous areas or disaster-affected zones where mobile communications are extremely unstable or cut off, using NTRIP for real-time corrections can be difficult in the first place (plan B for such cases will be described later). First, in situations where communication is possible, secure signal reception as much as you can and ensure the Internet access required for NTRIP connection is fully in place.

3. Check the operational status of the correction service

Also check whether the cause lies with the reference station service that distributes NTRIP correction data. Verify that the correction service you are accessing is operating normally and that the provider has not announced any outages or maintenance. It is also important to confirm that data is being correctly streamed from the selected mount point. In some cases the mount point itself may be temporarily not outputting data (stopped), so it is important to check information from the service provider.

Also, review the contract status of the correction service. Check whether the subscription period has expired or whether limits on the number of uses or the scope of use have been exceeded. In particular, many services prohibit using the same user ID on multiple devices simultaneously. If the same account is already logged in from another device, the connection may be rejected due to a double login. In that case, log out the other device’s connection and then try reconnecting.

Moreover, some correction services limit the areas where they can be used. Check whether you are trying to use the service outside the provider’s coverage area. In regions not supported by the service, you may be able to connect to NTRIP but still not receive correction data. By understanding the service’s operational status and contract conditions in this way, you can help isolate problems even when the cause is not on your side.

4. Check the data reception status

Don't be satisfied with just the indication that you are connected to the NTRIP server; also verify that correction data is actually being received. Many GNSS receivers and surveying apps display the amount of correction data being received and the "Age of Data (data latency)". If these do not change after connecting, it means data is not being received. Even if the device screen shows "connected", if no data flows for a certain period the reference station may have stopped broadcasting. Because the selected mount point might not be correctly delivering correction information, be cautious if the amount of received data does not increase even after waiting for a while after connecting.

As a troubleshooting step, try disconnecting the NTRIP connection once and then reconnecting; communication may resume. Also, if the service you subscribe to offers multiple mount points, try switching to a different mount point to see if you can obtain data. When only a specific mount point is temporarily offline, switching to another point may resume reception.

Also, if error codes or messages are displayed on the device, check their contents. The messages shown can provide clues to the cause. For example, if it says "Unauthorized (authentication failed)", recheck whether the login information is correct; if it says "Mountpoint not found", check whether the mount point name is correct. Do not overlook error messages—reviewing and adjusting settings according to the instructions they display can be the quickest way to resolve the problem.

5. Confirm the GNSS receiver and satellite reception status

Don't only suspect an NTRIP connection problem; also make sure not to overlook checking the condition of the GNSS receiver (rover) you are using. If, during an NTRIP connection, the device's display stops at a state such as "Wait for GGA" or "Waiting for position information", it is a sign that the base station (correction service) is waiting for the rover to transmit its current position. This happens when the rover's GNSS receiver has not yet established a sufficient fix and cannot determine its position.

As a countermeasure, improve the GNSS antenna installation environment and satellite visibility so that the rover can first secure its position using standalone positioning. Install the antenna in a location with an open sky overhead and avoid blockage from tall buildings and trees to increase the number of satellites received. Even in terrain-constrained situations, take measures such as moving slightly toward a more open direction. If the rover can compute its current position and send GGA data to the NTRIP server, the distribution of correction information should begin.

Also inspect the hardware condition of the GNSS equipment. Check that the antenna and communication cables are securely connected and that there are no broken wires or other damage. Also, as a precaution, check the receiver’s power supply and remaining battery level. Because equipment malfunction can prevent satellite acquisition, it is important to carry out basic hardware checks.

6. Isolate the cause using alternative methods

If you still cannot identify the cause after the above checks, or if multiple factors are suspected, using a different device or network to isolate the problem can be effective. If possible, try using another NTRIP client—such as PC RTK software or a smartphone app—to see whether you can obtain correction data with the same connection information.

If other devices can receive data normally, the cause is likely a configuration error or a software problem on the original device. Review the device settings and check the firmware and app update status. Conversely, if other devices also cannot connect, it is more likely to be a fault with the correction service or an issue with authentication information. In that case, prioritize rechecking the service-side status and the contract information mentioned above.

Also, if you have the opportunity, changing the internet connection path can be effective. For example, temporarily switch to a different communication line than the one you normally use (a SIM card from a different mobile carrier or another Wi‑Fi network) and try connecting to NTRIP. If it connects fine on the alternate line, you can assume the original line was the cause (for example, a corporate network firewall was blocking the port used for NTRIP—typically TCP 2101—or special settings were required in a proxy environment). By changing devices or connections and comparing the situation in this way, you can more clearly identify the source of the problem.

7. Consider alternative methods if NTRIP is not feasible

If the communication environment is extremely poor and you absolutely cannot use real-time corrections via NTRIP, consider switching the high-precision positioning method itself. Rather than insisting on an NTRIP connection, it is reassuring to have a Plan B ready to secure the required positioning accuracy by other means.

One alternative is to set up your own mobile base station (local reference point) and transmit correction information wirelessly. For example, install a GNSS receiver on site as the base station and use specified low-power radios or UHF-band radios to stream correction data to the rover in real time. Because it does not rely on the Internet, it can be used in mountainous areas outside cellular coverage. However, note that you will need to prepare equipment and a power supply for the base station.

As an alternative approach, you can forgo real-time corrections and record GNSS observation data to perform precise positioning by post-processing. This method, commonly called PPK (Post-Processed Kinematic), involves observing and recording raw data from the rover and the base station simultaneously and processing it in the office to obtain centimeter-level positions (half-inch accuracy). Although you will not get results immediately, it has the advantage of ultimately ensuring high accuracy even under unstable communication conditions.

Furthermore, depending on the operating environment, it is also possible to utilize satellite-based positioning augmentation services. In Japan, a representative example is reception of the centimeter-level (half-inch-level) augmentation service (CLAS) provided by the Quasi-Zenith Satellite System "Michibiki." With a compatible GNSS receiver, you can obtain high-precision correction information directly from the satellites even in areas where cellular service is unavailable. By using such satellite positioning augmentation signals, you should be able to continue real-time positioning without relying on the Internet.

In this way, by preparing alternative measures in case NTRIP cannot be used, you can continue positioning operations even at sites with poor network conditions or immediately after a disaster. At locations that require high-precision positioning, it is important to always keep a “Plan B” that does not rely on communications in mind.

Summary

That concludes the seven causes and basic countermeasures for cases where correction data cannot be received due to NTRIP connection errors. In practice, most causes of NTRIP connection failures fall into one of the categories above. Even if NTRIP malfunctions in the field, if you calmly check these points one by one you should be able to identify the problem area and resolve it accurately without relying on guesswork. To avoid interrupting high-precision positioning work, it is important to be familiar with how to check connection settings and equipment status on a regular basis. Also, because trouble can be caused by multiple overlapping factors, it is important to avoid assumptions and verify things in a systematic, orderly manner.

However, carrying out troubleshooting each time while taking these measures can become a burden depending on the situation on site. In particular, in situations where every second counts, such as disaster response, or when staff who are not familiar with communications or equipment operate the system, it is ideal to simplify the connection settings themselves to make problems less likely to occur. That is why new solutions that enable high-precision positioning with much simpler operation are attracting attention.

One of them is LRTK, a high-precision positioning device that uses a compact GNSS receiver attached to an iPhone. LRTK combines a smartphone and a dedicated GNSS receiver and is designed to achieve centimeter-level positioning without complicated NTRIP settings. With the dedicated smartphone app, you only need to press the start positioning button; it automatically retrieves correction information and applies position corrections, so it can be operated intuitively even without specialized knowledge. Surveying tasks that used to require two people to carry and set up heavy equipment can be easily handled by one person using a smartphone-mounted monopod with LRTK.

From an accuracy standpoint, LRTK provides positioning accuracy comparable to conventional high-performance surveying instruments. It supports multi-GNSS across multiple bands, and under favorable conditions both horizontal and vertical errors are contained to on the order of several centimeters (a few in). During static observation, averaging the measurements can even achieve accuracy of less than 1 cm (less than 0.4 in). Furthermore, because it also supports the centimeter-class augmentation service (CLAS) provided by Japan’s Quasi-Zenith Satellite System “Michibiki” (cm level accuracy (half-inch accuracy)), it can maintain high precision via correction signals from satellites even in locations without mobile communications.

By adopting LRTK, you can focus on your core measurement work without being troubled by complicated equipment setup or connection failures on site. A major advantage is that high-precision positioning, which used to rely on expensive, specialized equipment and skilled operators, can be performed easily by your own staff. LRTK, which makes high-precision positioning more accessible, is attracting attention as a new tool that supports DX across a wide range of field sites, from civil surveying to disaster investigation.

By putting into practice the NTRIP error countermeasures introduced here and leveraging advanced devices such as LRTK, RTK positioning will become even easier to use in the future. Even if you encounter on-site troubles where NTRIP won't connect, calmly isolate and address the cause and, when necessary, adopt new technologies; doing so should allow you to consistently maintain centimeter-level accuracy.