Orbi pro in access point mode dropping RDP connections

Hi DaneA

The deterioration of the capabilities of the Orbi Pro has gone way beyond just HyperV and remote desktop protocol (RDP).  Now my samsung galaxy s6 (Android 7) is reporting authentication errors and all our devices are dropping connections - 2 roku, Samsung S2 tablet (android 7), Dell windows 10 PC, HP Windows 10 PC.  The wifi is just completely unreliable.

Ping -t shows request timeouts frequently, for example:

C:\Users\nhinkle>ping 192.168.1.102 -t

Pinging 192.168.1.102 with 32 bytes of data
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Request timed out.
Request timed out.
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Request timed out.
Request timed out.
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Request timed out.
Request timed out.
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=3ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=2ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128
Reply from 192.168.1.102: bytes=32 time=1ms TTL=128

Ping statistics for 192.168.1.102:
Packets: Sent = 36, Received = 30, Lost = 6 (16% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 1ms
Control-C
^C

This is constant, whether I have the Satellite on or off.  With the Satellite off, I still get this and the topology is: r7000 with wifi off and its' lan port one hard wired to the WAN port of the SRR60. 192.168.1.102 is a server on lan port 3 of the R7000.  In this configuration, the Wifi on the SRR60 just drops packets constantly but if I use a lan port on the back of the SRR60, I get no packet loss.  So I can have functional Wifi in my house, I have had to drop back to my original configuration where I was using an older R7000 as an access point.  I now have that old R7000 in the exact same place as the SRR60 and I swapped the cable over and ran Ping -t to that R7000 for 30 minutes with 0 packet loss. 

I don't see the point of doing a speed test as speed is not the issue.  When the issue happens, there is no speed as the connection is dropped.