AC1750 Some apps failing after a few hours
My home network is an TP-Link Archer C7 [v2, 3.15.3 build 180114 rel .39265n] as my main router. I also have an TP-Link Archer A7 [v5, 1.0.14 build 20200220 rel .33197(5553)] configured as an AP and cabled to the C7.
After working successfully for over a year, the network began recently having issues. I found that some apps on our phones could not successfully retrieve data from their servers; i.e., the apps load, appear to authenticate, but then freeze. Internet browsing (via Chrome) still works without issue. Google play downloads still work without issue. Direct connections via cable to either the router or the AP still work without issue - including logins to sites, etc. Printer via WiFi continues to work.
Going through all my phone apps it appears to be only specific apps -- about five of them -- that exhibit this problem while other apps have no issues. When the problem occurs, all of these apps exhibit the behavior. When I reset the router, they all start working again. So, it does not appear to be a specific app but something these apps do which they don't like with whatever the router is doing. If I switch to 4G (no wifi) on the phone, then all the apps work without issue -- other than slower transmission.
Troubleshooting has shown that when I disable the guest networks (on both the C7 router and the A7 AP), then use of the main WiFi network is successful on both bands and my apps successfully connect to their servers. If I enable the guest networks, then these apps again fail in an attempt to retrieve datafrom their servers. Occasionally, even with the guest networks disabled, I still have to reset the router to get this working again. But, once I reset it, all of the apps begin working fine with no issues. When I notice the issue with one of the apps, then I can confirm it happens with all five of the apps.
I recently upgraded the firmware so it is possible this is a factor. Again, this setup has been working without issue for over a year. It was only a little over a week ago that I began seeing this issue. My next step is to try going back to the previous firmware version.