How do I get remote access?

[MeepLikesToBuildPc's]

So, on the PC i want to connect to, I enabled Remote Conecctions to this computer AND Allow connections to this computer.

thing is, when on MY pc, I want to log in to the other pc I enter the name into the "computer" tab (which is DESKTOP-DM45L7S) I enter that name, but I get the error that it can't find DESKTOP-DM45L7s

 

Both PC's are on the same Network.

 

How can I get this to work?

 

[mikat]

So, on the PC i want to connect to, I enabled Remote Conecctions to this computer AND Allow connections to this computer.

thing is, when on MY pc, I want to log in to the other pc I enter the name into the "computer" tab (which is DESKTOP-DM45L7S) I enter that name, but I get the error that it can't find DESKTOP-DM45L7s

 

Both PC's are on the same Network.

 

How can I get this to work?

step one: download the microsoft remote desktop application (windows store or mac app store)

step two: make a new connection and enter the credentials (= IP+Microsoft username+Microsoft password)

step three: click connect.

btw: i can help you via skype and i'm dutch so that's an added benefit

[manikyath]

if i recall correctly IP addresses are more reliable than computer names in most cases.

[mikat]

if i recall correctly IP addresses are more reliable than computer names in most cases.

yes. (and always use static ips)

[Speedbird]

So, on the PC i want to connect to, I enabled Remote Conecctions to this computer AND Allow connections to this computer.

thing is, when on MY pc, I want to log in to the other pc I enter the name into the "computer" tab (which is DESKTOP-DM45L7S) I enter that name, but I get the error that it can't find DESKTOP-DM45L7s

 

Both PC's are on the same Network.

 

How can I get this to work?

Are they on the same network?

[Levent]

its pretty straight forward on windows8 and above, if you are on the same network, enable RDP on the target machine and just connect via ip address and use that machines microsoft email and password to connect.

[Speedbird]

if i recall correctly IP addresses are more reliable than computer names in most cases.

The computer names act as DNS names inside the local network and the router should be able to resolve one to a local IP. The only time this wouldn't work is when the router does not resolve internal DNS names.

[Speedbird]

step one: download the microsoft remote desktop application (windows store or mac app store)

step two: make a new connection and enter the credentials (= IP+Microsoft username+Microsoft password)

step three: click connect.

btw: i can help you via skype and i'm dutch so that's an added benefit

There is an RDP client built in to Windows since XP. The modern one does seem to be better though.

[Atmos]

You could just use team viewer. Its free for personal noncommercial use.

 

I use it myself to control my server in my garage, so I don't have to walk outside through the standard 90 degree heat of southern california, and I'm a lazy bastard.

[manikyath]

The computer names act as DNS names inside the local network and the router should be able to resolve one to a local IP. The only time this wouldn't work is when the router does not resolve internal DNS names.

i've actually had some mixed success with this, depending on network setup and specific applications.

[mikat]

There is an RDP client built in to Windows since XP. The modern one does seem to be better though.

the modern one is WAYYYYYY better

[Speedbird]

the modern one is WAYYYYYY better

Makes sense. The Win32 one is a backport from a time when it was called Terminal Services. The Modern one is a port of the iOS/Android app.

[Levent]

i've actually had some mixed success with this, depending on network setup and specific applications.

yeah, WINS/Netbios (resolves computers running in the same network and workgroup) fucks up quite often for me too since it depends on computers to run on same workgroup.

[manikyath]

yeah, WINS/Netbios (resolves computers running in the same network and workgroup) fucks up quite often for me too since it depends on computers to run on same workgroup.

i've actually been using names for putty and samba to access my raspberry pi and linux virtual machine almost exclusively, and it rarely fucks up.

 

lately i seem to have more issues with windows machines using windows protocols, than i have issues with linux machines using windows protocols...

[mikat]

Makes sense. The Win32 one is a backport from a time when it was called Terminal Services. The Modern one is a port of the iOS/Android app.

on windows it is, the mac one is holy. it is the greatest. better than any program ever written.