How to Fix NTRIP Connection Errors Quickly | 6 Things to Check

When using RTK positioning in the field, have you ever encountered troubles such as “cannot connect to NTRIP” or “correction data is not received”? If NTRIP connections are unstable, you cannot take advantage of the centimeter-level (cm level) high-precision positioning you should be getting, which can seriously disrupt work.

This article narrows down six key points to check so you can verify the causes of NTRIP connection errors one by one without guessing and resolve problems as quickly as possible. By checking each item in order you can isolate the problem smoothly and accurately identify the cause. Finally, we also introduce a new solution called “LRTK” that can free you from cumbersome configuration troubles and let anyone achieve high-precision positioning easily.

Table of Contents

• What is NTRIP?

• Main causes of NTRIP connection errors

• Recheck connection settings and correct input mistakes

• Check the communication environment and secure an Internet connection

• Verify the correction service’s operational status and account condition

• Check the mountpoint and whether correction data is being received

• Check GNSS receiver operation and satellite reception status

• Isolate causes using other means and consider alternatives if necessary

• New solution LRTK to simplify high-precision positioning in the field

What is NTRIP?

NTRIP is the international standard protocol (communication method) for distributing correction data for GNSS positioning over the Internet. Its full name is Networked Transport of RTCM via Internet Protocol, and, as the name implies, it transmits correction information (in RTCM format and others) in real time via the Internet. In networked RTK positioning, a mobile GNSS receiver (rover) connects to the Internet via a mobile network or Wi‑Fi and receives real-time correction data from an NTRIP server (commonly called an NTRIP caster) provided by the correction service to which it subscribes.

Correction services using NTRIP are widely available domestically, ranging from the Geospatial Information Authority of Japan’s permanent station network to private companies’ services. They are used across many fields—civil surveying, agriculture, autonomous driving, and more—as a means to obtain centimeter-level (cm level) accuracy. NTRIP plays an important role in high-precision positioning in the field, but on-site issues such as “cannot connect to the server” or “connection is dropped midway” can occur. When such connection failures happen, high precision cannot be achieved, so it is necessary to quickly identify and resolve the cause.

Main causes of NTRIP connection errors

Let’s review the typical factors that can cause NTRIP connection failures. Common causes include the following.

First, input errors in the connection settings. If any of the NTRIP connection details—host name (or IP address), port number, mountpoint name, user ID, or password—are incorrect, the connection cannot be established. Spelling mistakes, omitted digits, or the inclusion of full-width characters are common and fundamental errors. Poor communication environment is also often seen. If the rover’s Internet connection is unstable or the signal is weak, or if the device automatically connects to public Wi‑Fi outdoors and cannot reach the Internet, access to the NTRIP server will be blocked.

Next, malfunctions on the correction service side or account-related problems should be considered. The reference station server (NTRIP caster) you are connecting to may be down or under maintenance, or the selected mountpoint may not be broadcasting correction data. Also, if your correction service contract has expired, or if the same account is being used on another device simultaneously and the service refuses the connection, these will cause failures.

Additionally, problems on the GNSS receiver side cannot be overlooked. If the rover cannot sufficiently track satellites and its position is not fixed, the base-side may wait for the rover’s current position information and show “Wait for GGA,” preventing receipt of correction data. Hardware issues such as antenna or cable misconnection or breakage, the receiver being powered off, or battery depletion can also lead to connection errors.

As shown, the causes of NTRIP connection failures are varied. While error messages and device status displays can give a clue, avoid relying on intuition. Multiple factors may overlap, so it is important to verify each item in order. The next chapters examine six points you should first check on site to resolve NTRIP connection errors as quickly as possible.

1. Recheck connection settings and correct input mistakes

When you cannot connect to NTRIP, the first thing to suspect is incorrect connection information. Recheck that the NTRIP server host name (or IP address), port number, mountpoint name, user name, and password entered on your device (GNSS receiver or app) exactly match the correct information provided by the correction service. If any one item is wrong, you cannot access the server.

For example, verify that the host name (server URL) spelling is correct and that there are no extra spaces at the beginning or end. Pay attention to confusing characters such as the digit 0 and the letter O, or 1 and the lowercase L. Omitting the port number is a surprisingly common oversight, so don’t miss it. Also confirm whether the mountpoint name is case-sensitive (in many cases it is). For user ID and password, ensure you have not entered full-width characters and that no stray line breaks or spaces are included.

This may seem like a basic check, but when you are flustered on site it is easy to overlook elementary mistakes. Calmly compare each input item and make sure the settings are correct. This is the first step to resolving NTRIP connection errors.

2. Check the communication environment and secure an Internet connection

Next, check the communication environment (Internet connection status). Confirm that the rover’s device can stably connect to the Internet via a mobile network or tethering. If you are using a mobile router, check signal strength; if coverage is limited, move to another location or try restarting the device. If using smartphone tethering, confirm the phone has a good signal and, if needed, change position or reconnect.

When working outdoors, devices can unintentionally connect to public Wi‑Fi or internal Wi‑Fi and lose Internet access. Turn off unnecessary Wi‑Fi connections and ensure communication is via the mobile network. Also verify that GNSS receivers and tablets can correctly obtain IP addresses. For example, if the receiver’s network status shows a local IP of 0.0.0.0, the communication module has not joined the network. If no IP address is assigned, review the router or tethering settings or restart devices to reconnect.

As a basic point, when using a mobile network confirm the device is not in airplane mode and that the SIM card’s data allowance has not been exhausted. Communication issues are easily overlooked but can cause NTRIP connection failures. Securing a stable Internet connection is a prerequisite for receiving correction data.

3. Verify the correction service’s operational status and account condition

Next, check the operational status of the correction service you are connecting to. If your device is functioning and communication is possible, confirm whether there is an issue on the reference station service side. Check the service provider’s official site or notifications for any outage or maintenance announcements. If the service is down, you must wait for it to resume. Also check whether your service contract’s usage period has expired; if it has, the connection will naturally be refused.

Also verify your account usage status. Many correction services prohibit using one account from multiple devices simultaneously. If the same ID is logged in on another receiver or device, the later connection attempt may be rejected. If you suspect this, ask the other device to log out or power it down, then try reconnecting. Some services also limit coverage areas; confirm whether your work site is within the service area. If you are outside the area, there may be no nearby reference station and you cannot connect.

Problems originating from the correction service are sometimes difficult for users to address, but checking the above items eliminates one possible cause. If the service status and account conditions are normal, move on to the next steps.

4. Check the mountpoint and whether correction data is being received

Don’t be reassured by merely being connected to NTRIP—also confirm that correction data is actually being received. Even if the device display shows “connected,” if no data arrives for some time the base station may have stopped broadcasting. The selected mountpoint may not be outputting data, so if possible try switching to another mountpoint. Sometimes disconnecting and reconnecting will start data reception.

Also check any error codes or messages displayed at connection for clues to the cause. For example, “Unauthorized” suggests a wrong username or password, while “Mountpoint not found” indicates an incorrect mountpoint name—both corresponding to the connection setting mistakes mentioned above. Errors such as “Host not found” or “Connection timed out” may point to incorrect server name/port settings or communication issues. Once you narrow down the cause from the error message, correct the relevant settings or environment and try reconnecting.

Checking the mountpoint and data broadcast status is important not only to confirm connection but to ensure “data is actually flowing.” A connection without incoming data is meaningless, so don’t skip this check.

5. Check GNSS receiver operation and satellite reception status

Next, check the rover GNSS receiver’s condition. If you are connected to NTRIP but no correction data arrives, the receiver may not be tracking enough satellites to determine its position. In network RTK (such as VRS), if the rover does not send an NMEA message (GGA) indicating its current position, the base side cannot compute a virtual reference and will not start broadcasting correction data. Therefore, if the device display shows “Wait for GGA” or “waiting for position,” take note—that means the rover has not yet fixed its position.

In such cases first review the antenna setup and surrounding environment. If the antenna is tipped over or does not have a clear sky view, satellite signals cannot be obtained. Reposition the antenna in a location with a clear sky view to improve the measurement environment. If you remain still for a while and acquire multiple satellites, a standalone fix will determine your position and the rover will send its location to the base side. Once the rover transmits its current position, correction data should begin to be received.

Also check the receiver’s hardware. Ensure antenna cables are not loose or broken, and that the measurement terminal is properly connected to the receiver. Confirm the receiver is powered on and the battery level is sufficient. Problems on the receiver side are a surprisingly common cause of NTRIP failures, so inspect the device state comprehensively.

6. Isolate causes using other means and consider alternatives if necessary

If you still cannot identify the cause or the issue persists after checking the above items, using other means to isolate the problem can be effective. If possible, try the same NTRIP connection with a different device or a different network. For example, use PC RTK software or a smartphone NTRIP client app with the same correction service credentials to see if you can receive data. If another device or app can successfully obtain correction data, the original device’s settings or hardware may be at fault. Conversely, if no device can connect, the problem is likely on the service side or with the authentication information. If available, also try a different Internet connection (a SIM card from a different carrier or another Wi‑Fi) to check for communication-path issues such as firewalls or proxies.

If field communications are extremely poor and NTRIP connections are impractical, consider temporarily switching the high-precision positioning method. For example, set up your own local base station and transmit correction information via radio, or record GNSS observation data and perform precise post-processing in the office later (PPK static positioning). Flexibly switching methods according to site constraints can allow you to continue positioning work.

In recent years, solutions that reduce dependency on these complex connection settings and communication environments and make high-precision positioning easier have gained attention. One such approach is LRTK, introduced in the next section. With LRTK, you can achieve centimeter accuracy on site without expert knowledge or complicated settings. Let’s look in detail at this simple positioning method using LRTK.

New solution LRTK to simplify high-precision positioning in the field

LRTK is attracting attention as a solution that significantly simplifies high-precision positioning in the field. LRTK is a system that combines a smartphone with a dedicated compact GNSS receiver and is developed to enable centimeter-level positioning without complex settings or advanced expertise. It is expected as a new approach that allows anyone to easily achieve high-precision positioning on site without struggling with tedious NTRIP connection settings.

With LRTK, a dedicated lightweight GNSS receiver is attached to a smartphone and positioning is performed from a dedicated app. The smartphone and receiver are mounted on a monopod (monopod), enabling one person to carry out stable surveying work. Where centimeter-level positioning used to require two people and heavy equipment, LRTK allows a single person to perform it using only a monopod-mounted smartphone. Field reports from LRTK adopters include comments like “I could patrol the site alone and quickly measure many points” and “it greatly shortened positioning time.”

LRTK’s greatest feature is its overwhelmingly simple operation. Tapping the start positioning button on the dedicated app automatically performs everything from acquiring correction data to high-precision positioning. Users do not need to be conscious of complicated settings or operations and can intuitively obtain centimeter-level positioning information. In terms of accuracy, LRTK offers positioning performance comparable to conventional expensive surveying instruments. It supports multi-frequency and multiple GNSS constellations (GPS, GLONASS, Galileo, QZSS, etc.), and under good conditions can achieve horizontal on the order of a few centimeters (a few cm (a few in)) and vertical on the order of a few centimeters (a few cm (a few in)). With an averaging function, stationary measurements can achieve errors of less than 1 cm (less than 0.4 in).

Furthermore, LRTK receivers also support the centimeter-class (cm-class) augmentation service (CLAS) provided by Japan’s Quasi-Zenith Satellite System (QZSS, “Michibiki”). This allows direct reception of correction information from satellites even in mountainous areas without mobile communication, enabling RTK positioning without relying on the Internet in some cases. The ability to achieve centimeter-level results even without a paid Internet correction service contract, depending on conditions, is a significant advantage on site.

By adopting LRTK, high-precision positioning tasks that previously required specialized surveying equipment and skilled operators can be performed easily by anyone. Without being bothered by complex device operations or connection troubles, teams can concentrate on the core measurement tasks—an important benefit for field work. Making high-precision positioning more accessible, LRTK is receiving attention as a new tool supporting DX across a wide range of sites from civil engineering and construction to disaster surveys. By overcoming NTRIP connection troubles and leveraging such advanced technologies, RTK positioning will become even easier to use going forward.