IT Field Engineer here, but not in anyway a networking guys, hence question.
Trying to RDP to a home server, but getting LSA cannot be contacted error :- known good details btw.
All devices on same Hub3.0 generated network with 192.168.0.Xxx addresses.
Weird thing is, my boy can RDP to it from his own PC - he uses it as a host server for a few games.
Only thing I can think of is that BOTH his pc and the server are connected to the network by the same home wifi extender, MY pc is connected directly to the hub.
Can ping it ok, but not RDP to it, any suggestions ? Do I need to do anything funky to the router ?
I'm hoping this help page can offer some assistance local-security-authority-cannot-be-contacted/
Also if you are using Windows 10 Home you will need a workaround as RDP is not enabled remote-desktop-windows-10-home/
Thx to both of these answers ..............
I am aware that RDP is not on 10Home, but both myself and my son use 10Pro - he can connect whilst I cannot.
I can't think how it can be DNS based, as we use the same DNS servers, provided by the Hub3 ?
Yep, I did ....... :-
Solution 1: Change Your DNS Address
Can't think it is this as I have said
Solution 2: Enable Remote Connections in Group Policy Editor
Presume this is on the server, so can't be this as my son can connect to it.
Solution 3: Allow the Connection inside System Properties
Can't be this for same reason
Solution 4: Run a Helpful Command on the Host - Flush DNS
Done this, not resolved
Solution 5: Set to Allow Connections from All Versions
Again, can't be this as son can connect whilst I can't
So just to be clear you are trying to RDP to the PC on the local network, not remotely?
All devices in question have 192.168.0.x IPs?
“Solution 2: Enable Remote Connections in Group Policy Editor
Presume this is on the server, so can't be this as my son can connect to it.“
Group policy is on the server, but maybe it’s not being passed down to the domain members correctly.