Windows 10: can't connect using RDP

I have everything setup for RDP to work and in fact it was working. out of the blue it stopped. I get this error each time I try.Host Computer: RDP is enabled. Target machine: Firewall accepts remote calls. RDP is enabled. I've added my @hotmail.com user as both local Admin and RDP member.I have removed all devices from my router and let them all get rediscovered.I run RDP from Host. I enter the Target computer name. I get this error below every time. and as I said, 1 week ago this all worked and I have not installed anything outside of Windows Updates.

:)

 

RDP and Network Connection Drops While on Ethernet

Sam,

1. Even without issuing the ping -t command I will experience a RDP drop and network bottleneck
2. RDP clients are the same version
3. No firewall setup
4. All connecting with the same cables from similar ports

winbox1 has full duplexTrue
winbox2 does not have duplex True

Pretty sure it's something with the network setup, I might reinstall the OS

 

RDP and Network Connection Drops While on Ethernet

I have the following setup:

2 x windows 10 and 1 X windows 7 computers connected to the same router through cable having 192.168.0.1 as the router gateway.

win7-box: 192.168.0.38
win10-box1: 192.168.0.211
win10-box2: 192.168.0.24

I am connecting from win7-box, which I'm using as the main machine, through RDP to the other 2 win10 machines.

The connection to 192.168.0.211 runs smoothly but when I connect to 192.168.0.24, the connection gets interrupted after 30-60 seconds and I get the "This computer can't connect to the remote computer" error:





While ping 192.168.0.24 -t from 192.168.0.38 was running I got this:





Even if after the The connection has been lost error that corresponds to the Request timed out ping error - the connection seems to be restored (as ping is up again), if I try to RDP again I get the "Destination host unreachable" error.





Now I cannot RDP to 192.168.0.24 anymore until I manually log into this host by physically using its keyboard.

I also did a ping 192.168.0.1 -t on 192.168.0.24 and noticed the General Failure error that corresponds to the Request timed out from the win7-box

enter image description here

I also noticed that I get the General Failure error intermittently, even if don't try a RDP connection on this win10-box2 machine.

What I did:

I tried a Network Reset from the Network&Internet settings:

• Tried switching the cable itself and the cable port on the router
• Tried using a different static ip, other than 192.168.0.24
• Tried using the wireless connection to the same router and noticed that even if do get some isolated Request timed out error when continuously pinging win10-box's ip, no issues are found and RDP connection is stable.

I assume this has to be something wrong in my current win10-box2 configuration as the router seems to be working fine on other devices.

The network configuration on win10-box2 is as follows:





The question would be - what else should I try/check in order to solve this issue?

 

RDP

I guess I am showing my age.

In times past I was able to use RDP to remotely connect from my pc to a remote host pc - provided that remote pc was RDP enabled and the fire-wall was opened for the RDP port.

These days it seems much more complex.

Is there a step-by-step instruction sheet to follow? Or, better, is there an app/utility which configures the host more-or-less automatically?