Windows 10: Win11 Can't Access Win10 Network Drive After Name Change—RDP & Ping Work Fine

: I’m experiencing a strange network issue that started right after I changed the name of my Windows 11 laptop. Before the name change, everything worked fine, but now my Win11 PC cannot access the shared drive on my Win10 PC.What Still Works: Remote Desktop: Win11 → Win10, Win7, XP no issues. Ping: Win11 can ping Win10 successfully. Other Network Shares: Win11 can access shared drives on Win7. Win10 Access: Win10 can access shared drives on XP & Win7.What Fails: Win11 → Win10 Shared Drive: "Cannot access" errors.What I’ve Tried: Checked all sharing settings folders, permissio

:)

 

RDP connection win10 -> win11

Hello,

I am trying to connect from one laptop (win10) to another one (win11) in the same wi-fi, over RDP, but I'm keep getting the "Your credentials did not work" message.

1. I enabled Remote Desktop connection on my target laptop (the one with win 11) and allowed remote connection in the Firewall settings.

2. For the RDP configuration, I entered the IP address of the target laptop and for the username I used the value that I got in cmd, "whoami" command. For the password I entered the one which I use on login screen.

I already tried everything that I found on the internet, and it does not work.

The funny thing is that when I try in opposite direction, RDP from laptop (win11) to laptop (win10), I manage to login over RDP, but in the direction that I need it is not working (although I follow all the same steps).

Do you have any idea what I can do more, because I am frustrated ?!

Thank you in advance.

 

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 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