Community beginner query:
When making a RDP connection to an exterior buyer, I appear to have a really unhealthy connection:
- I click on someplace within the related PC, however nothing occurs.
- Commonly the connection drops.
- …
To ensure that the connection to work, I make a connection, utilizing Sinema RC Consumer, as you’ll be able to see right here:
I’ve measured the standard of the RDP connection utilizing ping -n 1000 , with the next outcome:
...
Reply from 192.168.2.206: bytes=32 time=10ms TTL=126
Reply from 192.168.2.206: bytes=32 time=15ms TTL=126
Reply from 192.168.2.206: bytes=32 time=10ms TTL=126
Reply from 192.168.2.206: bytes=32 time=9ms TTL=126
Reply from 192.168.2.206: bytes=32 time=10ms TTL=126
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.2.206:
Packets: Despatched = 75, Obtained = 65, Misplaced = 10 (13% loss),
Approximate spherical journey occasions in milli-seconds:
Minimal = 8ms, Most = 89ms, Common = 11ms
The numbers are usually not good: 13% packet loss, common spherical journey of +10ms, most as much as ±90ms, …
Some extra data:route print outcome:
===========================================================================
Interface Record
9...34 73 5a b9 a3 27 ......Realtek USB GbE Household Controller
14...00 09 0f aa 00 01 ......Fortinet SSL VPN Digital Ethernet Adapter
27...34 73 5a b9 a3 26 ......Intel(R) Ethernet Connection (13) I219-LM
3...00 ff 3b 76 7f 5b ......TAP-Home windows Adapter V9
17...b4 0e de e7 7b 6f ......Intel(R) Wi-Fi 6 AX201 160MHz
18...b4 0e de e7 7b 70 ......Microsoft Wi-Fi Direct Digital Adapter
19...b6 0e de e7 7b 6f ......Microsoft Wi-Fi Direct Digital Adapter #2
4...00 50 56 c0 00 01 ......VMware Digital Ethernet Adapter for VMnet1
28...00 50 56 c0 00 08 ......VMware Digital Ethernet Adapter for VMnet8
10...00 09 0f fe 00 01 ......Fortinet Digital Ethernet Adapter (NDIS 6.30)
1...........................Software program Loopback Interface 1
===========================================================================
IPv4 Route Desk
===========================================================================
Energetic Routes:
None
Persistent Routes:
None
IPv6 Route Desk
===========================================================================
Energetic Routes:
None
Persistent Routes:
None
The results of tracert IP_Address is the next:
tracert 192.168.2.206
Tracing path to RemotePC [192.168.2.206]
over a most of 30 hops:
1 <1 ms <1 ms <1 ms 172.30.0.1
2 9 ms 10 ms 9 ms RemotePC [192.168.2.206]
3 9 ms 10 ms 9 ms RemotePC [192.168.2.206]
Hint full.
What is the subsequent step to find out the basis explanation for this unhealthy connection?
Thanks upfront
Edit:
As a response on Zac’s first edited remark, hereby the pathping outcome:
Immediate>pathping 192.168.2.206
Tracing path to 192.168.2.206 over a most of 30 hops
0 OwnPC [172.30.0.41]
1 172.30.0.1
2 * * RemotePC [192.168.2.206]
3 RemotePC [192.168.2.206]
Computing statistics for 75 seconds...
Supply to Right here This Node/Hyperlink
Hop RTT Misplaced/Despatched = Pct Misplaced/Despatched = Pct Handle
0 OwnPC [172.30.0.41]
15/ 100 = 15% |
1 0ms 23/ 100 = 23% 8/ 100 = 8% 172.30.0.1
0/ 100 = 0% |
2 10ms 15/ 100 = 15% 0/ 100 = 0% RemotePC [192.168.2.206]
2/ 100 = 2% |
3 10ms 17/ 100 = 17% 0/ 100 = 0% RemotePC [192.168.2.206]
Hint full.