Home Network Community > 5G/4G Routers > TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
< 5G/4G Routers

TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)

TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)

TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
3 weeks ago - last edited Tuesday
Model: Archer NX200  
Hardware Version: V2
Firmware Version: 1.0.0 3.0.0 v60e0.0 Build 240822 Rel.76438n

Hello, I live in Italy and I am experiencing issues connecting the TP-Link Archer NX200 router to the network with the mobile virtual network operator 1 Mobile (which operates on the Vodafone network). I have added a new APN profile with the following settings:

  • PDP Type: IPv4
  • APN Type: Static
  • APN: web unomobile it (with dots)
  • Username: (empty)
  • Password: (empty)
  • Authentication Type: CHAP
  • Data Roaming: Enabled
  • NAT: Enabled
  • Mobile Data: Enabled

The router detects the network and bands (the signal is strong and 5G), but it fails to connect. If left powered on, it connects only after many hours, typically the following night/morning, and starts exchanging data. Once the connection is established, it seems to work well, although there are occasional brief disconnections of a few seconds, but it recovers quickly. The issue reoccurs when the router is turned off, as it can no longer reconnect quickly (it still detects the network and bands, but it appears not to be registered on the network and thus does not exchange data). After many hours, it seems that during the night, the router manages to reconnect and register on the network, resuming data exchange and allowing browsing.I would like to know if this is a firmware issue or a configuration problem (the settings used work, but the connection only happens at night after many hours). With SIMs from non-virtual operators, the router works and connects immediately (using default settings). The 1 Mobile SIM works well in a smartphone, both for cellular data and as a hotspot. Below are some parameters I set for Android, which I couldn’t find in the Archer NX200 interface:

  • APN Type: default, supl, dun
  • Virtual Network Operator Type: IMSI

The router is updated, or at least no updates are available. Below are the details from the web interface:

  • Firmware Version: 1.0.0 3.0.0 v60e0.0 Build 240822 Rel.76438n
  • Hardware Version: Archer NX200 v2.0 00000000 (on the packaging and label under the router, it says EU/2.20, so I’m confused if the version is 2.0 or 2.2)

I noticed there is a beta version of the software. Do you think it could resolve my issue? Or is it a configuration problem, and should I contact support to check if it’s possible to update the ISP configurations for my “non-standard” virtual operator? I specify that I have tried with other SIMs from standard, non-virtual operators, and the router works fine, connecting immediately with the default settings.


Thank you in advance for any responses you can provide.

  1      
 
  1      
 
#1
Options
1 Accepted Solution
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)-Solution
2 weeks ago - last edited Tuesday

  @David-TP 

 

Hi David,I’ve updated the router’s firmware and tested it for two days. It seems to be working well. The router connects to the network in about 2 minutes and browses without issues. It also feels more stable, though there are still occasional, brief disconnections of 5-6 seconds every 8-9 hours. It reconnects automatically, so I’m not sure if it’s due to the network or the router itself. Overall, it’s functioning well and seems stable, I’d say the issue has been resolved nicely.

 

One last question: I’d like to pair it with a repeater in access point mode, connected via Ethernet in mesh mode. Does it support Ethernet backhaul for the mesh?

 

Thanks for your support and great work!

Recommended Solution
  1  
  1  
#5
Options
5 Reply
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
3 weeks ago

  @Pitte 

Hi, welcome to the community.

I'll check with the senior engineer for more advice, and will update here as soon as possible.

It would be better if you could save a screenshot of the internet status before Archer NX200 eventually gets connected.

Please also save a copy of the web UI system log.

Thank you very much.

Best regards.

 

▶Check What's Currently Going on With Deco ▶Deco BE85 1.2.0 Enhanced Mesh Backhaul Stability and Device Roaming Experience ▶Deco BE65/BE65 Pro 1.2.0 Enhanced Mesh Network Stability and System Security ▶Deco BE75 1.1.0 Added WireGuard VPN, Manual Channel Selection and More Try to leave a Message if urgent help is required.
  0  
  0  
#2
Options
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
3 weeks ago

  @David-TP 

 

Hi David, thanks for your reply. 
As requested, this evening I rebooted the router so I could take a screenshot of the internet status before it gets connected (as always, it's taking a long time to reconnect and is still offline). Below the screenshots of the internet status.

 

Below are the system logs from last night until midday (the router connected during the night and has been online all day). The logs show the time it actually connected to the network (2025-08-28 02:46:57) because it correctly updates the date and time from the internet (the previous date was 2016). It seems there were a few short disconnections of a few seconds during the day, but it reconnected right away on its own and I didn't notice.

BBA Platform version:3.1.8-rc26
2016-01-01 00:40:26 [5] LTE: SIM plugged.

2016-01-01 00:40:26 [5] System: Enable Access Control
2016-01-01 00:40:27 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:40:27 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:40:27 [5] LTE: Not registered, searching!

2016-01-01 00:40:27 [6] LTE: p_str(p_len=30)=150,600,3600,21600,43200,86400, p_size=16

2016-01-01 00:40:27 [6] LTE: table[0]=150

2016-01-01 00:40:27 [6] LTE: table[1]=600

2016-01-01 00:40:27 [6] LTE: table[2]=3600

2016-01-01 00:40:27 [5] LTE: Not registered, not currently searching!

2016-01-01 00:40:27 [6] LTE: table[3]=21600

2016-01-01 00:40:27 [6] LTE: table[4]=43200

2016-01-01 00:40:27 [6] LTE: table[5]=86400

2016-01-01 00:40:27 [6] LTE: table_number=6, lte_disconn_reboot_threshold=21600

2016-01-01 00:40:27 [6] LTE: type=0, reason=REBOOT, value=0, new config flag=00000080, new status flag=00000080

2016-01-01 00:40:27 [6] LTE: type=7, reason=REBOOT_REASON_LTE_DNS_DISCONNECTED, value=0, new config flag=00000000, new status flag=00000000

2016-01-01 00:40:30 [5] LTE: Registered with a network!

2016-01-01 00:40:30 [5] LTE: Network type is NR.

2016-01-01 00:40:30 [5] LTE: network changed: 0,0->222,10

2016-01-01 00:40:30 [5] LTE: Start connecting to the network!

2016-01-01 00:40:30 [5] LTE: Fail to connect to the network, start autoconnect!

2016-01-01 00:40:32 [5] LTE: Connected to the network!

2016-01-01 00:40:32 [6] LTE: first_valid_uptime=54

2016-01-01 02:40:31 [5] LTE: The network disconnected, start autoconnect!

2016-01-01 02:40:37 [5] LTE: Fail to connect to the network, start autoconnect!

2016-01-01 02:40:39 [5] LTE: Connected to the network!

2025-08-28 02:46:57 [6] LTE: first_conn_uptime=7274

2025-08-28 02:46:57 [6] LTE: health_conn_uptime=7274

2025-08-28 05:30:31 [5] LTE: Network type is LTE.

2025-08-28 05:30:39 [5] LTE: Network type is NR.

2025-08-28 05:30:42 [5] LTE: Network type is LTE.

2025-08-28 05:30:42 [5] LTE: Network type is NR.

2025-08-28 07:24:23 [5] DHCPD: Recv DISCOVER from EC:91:61:CE:52:13
2025-08-28 07:24:23 [5] DHCPD: Send OFFER with ip 192.168.1.2
2025-08-28 07:24:23 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:24:28 [5] DHCPD: Send OFFER with ip 192.168.1.2
2025-08-28 07:24:32 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:24:32 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:25:01 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:25:01 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:28:15 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:28:15 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:28:17 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:28:17 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:30:00 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:30:00 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:30:02 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:30:02 [5] DHCPD: Recv INFORM from EC:91:61:CE:52:13
2025-08-28 07:30:02 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 07:54:37 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 07:54:37 [5] DHCPD: Recv DISCOVER from EE:8B:E1:CE:FE:63
2025-08-28 07:54:37 [5] DHCPD: Send OFFER with ip 192.168.1.3
2025-08-28 08:24:03 [5] Mesh: Del Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 08:46:52 [6] LTE: p_str(p_len=30)=150,600,3600,21600,43200,86400, p_size=16

2025-08-28 08:46:52 [6] LTE: table[0]=150

2025-08-28 08:46:52 [6] LTE: table[1]=600

2025-08-28 08:46:52 [6] LTE: table[2]=3600

2025-08-28 08:46:52 [6] LTE: table[3]=21600

2025-08-28 08:46:52 [6] LTE: table[4]=43200

2025-08-28 08:46:52 [6] LTE: table[5]=86400

2025-08-28 08:46:52 [6] LTE: table_number=6, lte_disconn_reboot_threshold=150

2025-08-28 09:04:01 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:04:05 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:13:31 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:13:32 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:13:33 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:13:34 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:23:20 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:23:21 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:23:23 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:23:23 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:27:05 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:27:05 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:27:07 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:27:07 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:28:53 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:28:54 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:28:55 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:28:56 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:34:36 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:34:37 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:34:38 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:34:38 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:42:55 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:42:55 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:42:56 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:42:57 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:45:38 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:45:39 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:45:40 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:45:41 [5] Mesh: Success Add Client : MAC : EC:91:61:CE:52:13

2025-08-28 09:45:46 [5] Mesh: Del Client : MAC : EC:91:61:CE:52:13

2025-08-28 11:06:44 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 11:06:44 [5] DHCPD: Recv DISCOVER from EE:8B:E1:CE:FE:63
2025-08-28 11:06:44 [5] DHCPD: Send OFFER with ip 192.168.1.3
2025-08-28 11:06:57 [5] Mesh: Del Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 11:06:57 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 11:21:07 [5] Mesh: Del Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 11:21:07 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 11:23:42 [5] Mesh: Del Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 12:08:52 [5] LTE: The network disconnected, start autoconnect!

2025-08-28 12:08:58 [5] LTE: Fail to connect to the network, start autoconnect!

2025-08-28 12:09:00 [5] LTE: Connected to the network!

2025-08-28 13:17:54 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 13:17:54 [5] DHCPD: Recv DISCOVER from EE:8B:E1:CE:FE:63
2025-08-28 13:17:54 [5] DHCPD: Send OFFER with ip 192.168.1.2
2025-08-28 13:17:58 [5] Mesh: Del Client : MAC : EE:8B:E1:CE:FE:63

2025-08-28 13:18:00 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

 

Below you can find the system logs after I rebooted the router tonight (as I said it's still offline).

BBA Platform version:3.1.8-rc26
2016-01-01 00:16:55 [5] DHCPD: Recv REQUEST from EE:8B:E1:CE:FE:63
2016-01-01 00:16:57 [5] DHCPD: Recv REQUEST from EE:8B:E1:CE:FE:63
2016-01-01 00:16:58 [5] DHCPD: Recv REQUEST from EE:8B:E1:CE:FE:63
2016-01-01 00:17:00 [5] DHCPD: Recv DISCOVER from EE:8B:E1:CE:FE:63
2016-01-01 00:17:00 [5] DHCPD: Send OFFER with ip 192.168.1.2
2016-01-01 00:17:02 [5] LTE: SIM plugged.

2016-01-01 00:17:02 [5] System: Enable Access Control
2016-01-01 00:17:02 [5] System: Enable IPv4 SPI Firewall
2016-01-01 00:17:02 [5] System: Enable IPv6 SPI Firewall
2016-01-01 00:17:03 [5] LTE: Not registered, searching!

2016-01-01 00:17:03 [6] LTE: p_str(p_len=30)=150,600,3600,21600,43200,86400, p_size=16

2016-01-01 00:17:03 [6] LTE: table[0]=150

2016-01-01 00:17:03 [6] LTE: table[1]=600

2016-01-01 00:17:03 [6] LTE: table[2]=3600

2016-01-01 00:17:03 [6] LTE: table[3]=21600

2016-01-01 00:17:03 [6] LTE: table[4]=43200

2016-01-01 00:17:03 [6] LTE: table[5]=86400

2016-01-01 00:17:03 [6] LTE: table_number=6, lte_disconn_reboot_threshold=3600

2016-01-01 00:17:03 [5] LTE: Not registered, not currently searching!

2016-01-01 00:17:03 [6] LTE: type=0, reason=REBOOT, value=0, new config flag=00000080, new status flag=00000080

2016-01-01 00:17:03 [6] LTE: type=7, reason=REBOOT_REASON_LTE_DNS_DISCONNECTED, value=0, new config flag=00000000, new status flag=00000000

2016-01-01 00:17:05 [5] Mesh: Success Add Client : MAC : EE:8B:E1:CE:FE:63

2016-01-01 00:17:05 [5] Mesh: Success Add Client : MAC : 08:92:04:1C:3E:88

2016-01-01 00:17:06 [5] LTE: Registered with a network!

2016-01-01 00:17:06 [5] LTE: Network type is NR.

2016-01-01 00:17:06 [5] LTE: network changed: 0,0->222,10

2016-01-01 00:17:06 [5] LTE: Start connecting to the network!

2016-01-01 00:17:06 [5] LTE: Fail to connect to the network, start autoconnect!

2016-01-01 00:17:08 [5] LTE: Connected to the network!

2016-01-01 00:17:08 [6] LTE: first_valid_uptime=55

 

If you need more information let me know.

Thanks in advance for the support!

 

 

 

  1  
  1  
#3
Options
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
3 weeks ago

  @Pitte Hi, thanks for the further details.

The engineer provided a new beta version for Archer NX200, and I've shared it via email.

It is suggested to update to this link manually and test whether it helps.

Wait for your reply.

Best regards.

 

▶Check What's Currently Going on With Deco ▶Deco BE85 1.2.0 Enhanced Mesh Backhaul Stability and Device Roaming Experience ▶Deco BE65/BE65 Pro 1.2.0 Enhanced Mesh Network Stability and System Security ▶Deco BE75 1.1.0 Added WireGuard VPN, Manual Channel Selection and More Try to leave a Message if urgent help is required.
  0  
  0  
#4
Options
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)-Solution
2 weeks ago - last edited Tuesday

  @David-TP 

 

Hi David,I’ve updated the router’s firmware and tested it for two days. It seems to be working well. The router connects to the network in about 2 minutes and browses without issues. It also feels more stable, though there are still occasional, brief disconnections of 5-6 seconds every 8-9 hours. It reconnects automatically, so I’m not sure if it’s due to the network or the router itself. Overall, it’s functioning well and seems stable, I’d say the issue has been resolved nicely.

 

One last question: I’d like to pair it with a repeater in access point mode, connected via Ethernet in mesh mode. Does it support Ethernet backhaul for the mesh?

 

Thanks for your support and great work!

Recommended Solution
  1  
  1  
#5
Options
Re:TP-Link Archer NX200: Connection Issues with MVNO 1 Mobile (Vodafone)
2 weeks ago

  @Pitte 

Hi, thank you very much for the update.

Archer NX200 doesn't support Easymesh Ethernet Backhaul. I'm afraid the EasyMesh range extender needs to be wirelessly connected to the NX200.

Best regards.

▶Check What's Currently Going on With Deco ▶Deco BE85 1.2.0 Enhanced Mesh Backhaul Stability and Device Roaming Experience ▶Deco BE65/BE65 Pro 1.2.0 Enhanced Mesh Network Stability and System Security ▶Deco BE75 1.1.0 Added WireGuard VPN, Manual Channel Selection and More Try to leave a Message if urgent help is required.
  0  
  0  
#6
Options

Information

Helpful: 1

Views: 220

Replies: 5

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.