Windows 10: I can't reach local PC with ping and rdp but he can navigate without problem

Hi,


I have 5 pcs on a Lan and i can reach 4 of 5 pc with rdp and ping from local server.

But i can't reach 1 pc.


From this pc, i can navigate and all everything but if i try to ping this pc with other pc or server, i can't reach it.


I tried to ping other pc from server and i can reach all.


All pc have different ips.


I tried all guide of microsoft but I can't solved the problem, i have no more idea.

:)

 

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

 

Windows 10 RDP Performance

Thank you for the reply!

My local machine was fine - connected via WIFI.

I ran pings to my work PC and to 8.8.8.8 as a control - didn't drop packets during either test and ping response times were normal (around 30ms).

I've used RDP to connect to my work PC over VPN for several years. When my laptop was running win7, i had no performance problems, but now that I've updated it to win10, the native 10 client seems to be very cumbersome, with no apparent options to tweak
performance settings.

Today I'm in the office, and I'm composing this reply from within an RDP session on my laptop to my work PC - the performance is better then when i connected across the Internet, but it's still not great.

When connecting from the Internet, RDP is almost unusable.

 

RDP and Network Connection Drops While on Ethernet

This cannot be the case as I am pinging in the same way from 2 more windows computers without getting the General Failure error