Best way to remotely access WIN10 Pro machine?

[wood1e1]

Hi,

I have been trying different 'free software' and bought some as well.

I have tried most recently, 'Microsoft Remote Desktop Beta' but that just won't connect, even though the WIN10 pro machine has been set up to be open, well I think it has!! This is the error: https://www.screencast.com/t/AbsER5xMueX

So if remote access is allowed why would it not find it? Anyway, I am almost giving up and maybe tehre is a different way to connect?

 

[SecuritySteve]

In the App Store, Microsoft Remote Desktop works fine for all of my RDP needs. Not sure if the Beta is what is causing you problems or not.

Otherwise it is likely a network or configuration issue on your laptop.

 

[wood1e1]

ok So what are the 'network or configuration issues' that are likely on the laptop?

As far as I am concerned I have set up Laptop to accept 'Remote Access'

https://www.screencast.com/t/KKmtGExG7d

Then every time I get this: https://www.screencast.com/t/sHr9kkm0Ss7b

The software I am now using is this: https://www.screencast.com/t/WJL1z8XaXA just in case you are using soemthing different.

So I am confused as what I have done wrong!

 

[SecuritySteve]

Does your system have a firewall active, or Endpoint Protection software that might be denying RDP ports?

I would run nmap against your laptop from your Mac. Check to see if any of the RDP ports are actually open.

Edit: Is it also possible for you to check using another Windows system trying to use RDP to get into the laptop as well?

 

[wood1e1]

It was the anti virus that was blocking.

I know get a username and password... for a user, but when I enter it doesn't connect.

Do I need to create a new user on WIN10 Laptop? Or maybe a domain? Domain/user or @user? I am not sure what this is?

 

[SecuritySteve]

You might need to create a user. Looks like you're getting close though. Additionally you might have better luck logging in as .\user so that it tries to log in with local machine credentials, instead of domain credentials if it is connected to a domain.

 

[wood1e1]

Hi

Well, that seems to have worked, set up a local user now I have just set up all my apps again! Never mind I am in now and hopefully it will be more seamless that various different programmes I have used.

And now figure out how to allow exceptions to firewall

The only thing that I would like to change is

a) Can I remove the request on the laptop to allow me access? As I might be out and about sometime and unable to click 'yes allow access' on the laptop

 

[SecuritySteve]

Yes, but I'm not sure where the option is. I'm sure there is a guide somewhere that answers exactly that.

 

[milleron]

I'm wondering if your problem came from checking the box that allowed only connection from computers with Network Level Authentication. If you're trying to connect from a Mac, does it have that "Microsoftish" type of Authentication? Perhaps if you'd not checked that box, it would have connected from the start. That might not seem consistent with the error message you got from MRD, but Microsoft error messages are notorious for being misleading. It's been that way for 30 years. They're coded by idiot savants who can communicate with computers but not with human beings.
I've no idea where you got a beta version of Microsoft Remote Desktop, but the standard version usually works flawlessly from Mac to PC on a LAN. The only inconsistency I've seen is that occasionally, for some unknown reason, it needs to be given an IP address rather than the remote PC's name. Once connected, it's rock stable.