Issues following updating AX55 EU V1 to new "stable" firmware 1.3.3 Build 20240628 rel.37017(4555)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

Issues following updating AX55 EU V1 to new "stable" firmware 1.3.3 Build 20240628 rel.37017(4555)

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
Issues following updating AX55 EU V1 to new "stable" firmware 1.3.3 Build 20240628 rel.37017(4555)
Issues following updating AX55 EU V1 to new "stable" firmware 1.3.3 Build 20240628 rel.37017(4555)
2024-10-01 14:35:54 - last edited 2024-10-01 15:34:28
Model: Archer AX55  
Hardware Version: V1
Firmware Version: 1.3.3 Build 20240628 rel.37017(4555)

So I updated the main router (AX55) to its new firmware today, and now the connection to our home server, and 1 of the satellites is unstable. The router was previously running beta 1.2.6 Build 20231130.

 

The server is connected directly to the router via a 2 metre CAT6 Ethernet cable, and has been assigned a static IP in the DHCP server section of the router.

 

All was fine on the beta 1.2.6 Build 20231130 firmware, but on the new "stable" firmware, the server keeps being disconnected from the network every few minutes, and can take anywhere from 30 seconds to 2 minutes to reconnect.

 

This has made it impossible to now use the server.

 

Due to issues with how the property was built, Satellites connected via Ethernet backhaul are required to ensure stable Wi-Fi throughout, and where possible, Ethernet connection to devices (TVs, Set-top boxes, Games Consoles etc) is also best, hence the 2 Mercusys MR70Xs and the Network switches (TP Link and Mercusys brands). All Ethernet cables are a minimum of CAT6, with the Backhaul cables being CAT7.

 

Since the update, the Satellite in Bedroom 3 will not connect via Ethernet Backhaul, and keeps switching wireless connection between the AX55 and the Satellite in Bedroom 1 with the apparent same frequency as the Server disconnections.

 

Network topography map:

 

Resolved. Had to factory reset. Luckily I had backed up settings before the update.

  1      
  1      
#1
Options