Is anyone here familiar with Windows Remote Desktop? I am wondering how well this works in terms of security and functionality versus a paid program such as gotomypc, remotepc, or splashtop.

quote:

Originally posted by deepocean:
Is anyone here familiar with Windows Remote Desktop? I am wondering how well this works in terms of security and

functionality versus a paid program such as gotomypc, remotepc, or splashtop.

Works very well as long as you are on your own network behind a good firewall and good security practices. Do not under any circumstances should you implemented it outward facing from your network. Use GotoMyPC, Teamviewer or something similar.

quote:

Originally posted by TXLe:

Works very well as long as you are on your own network behind a good firewall and good security practices. Do not under any circumstances should you implemented it outward facing from your network. Use GotoMyPC, Teamviewer or something similar.

Thank you. This is exactly what I needed to know. I do not mind learning how to do it, but if it would create security issues, I would much rather use a paid version.

The free version of team viewer would be an option, except this will be for small business use. Perhaps they would not know, but we would know, and we are not doing that.

Go to my pc is now like $450 a year. That makes no sense for us for something which will only be used maybe 5 times a year, for a half hour each time.

You can use OpenVPN to access RDP securely.

Something like OpenVPN on a raspberry pi.
http://www.pivpn.io/

There is also Chrome Remote Desktop

https://www.computerworld.com/...computer-easily.html

Wish I could help. My only experience has been with TeamViewer which worked flawlessly.

It works better than all the rest but you must be able to forward port 3389 on your router, have a static IP or use a Dynamic DNS Utility.
Windows Home Version does not have Remote Desktop.

quote:

Originally posted by smschulz:
It works better than all the rest but you must be able to forward port 3389 on your router, have a static IP or use a Dynamic DNS Utility.
Windows Home Version does not have Remote Desktop.

What are the security concerns of using Windows Remote Desktop? The computers using it all have Windows 7 Pro.

quote:

Originally posted by smschulz:
It works better than all the rest but you must be able to forward port 3389 on your router, have a static IP or use a Dynamic DNS Utility.
Windows Home Version does not have Remote Desktop.

Noted above was Chrome Remote Desktop. I installed it tonight on my office desktop and remoted into it from my laptop and mobile phone almost seamlessly. I'm thinking about trying to use it to get into my mom's computer when she's having issues rather than having to drive to her home. Is there anything I need to be aware of using this utility?

quote:

Originally posted by deepocean:

quote:

Originally posted by smschulz:
It works better than all the rest but you must be able to forward port 3389 on your router, have a static IP or use a Dynamic DNS Utility.
Windows Home Version does not have Remote Desktop.

What are the security concerns of using Windows Remote Desktop? The computers using it all have Windows 7 Pro.

If you do not use a secure VPN to connect to the network and then run the RDP session within the tunnel, but either use NAT (Network Address Translation) or other method to present the RDP machine to the public side of your network edge, you are leaving that RDP machine open to all number of exploits. It can take a few minutes for an active RDP listening machine to be scanned and exploited, and often a payload dropped on that machine, or that machine used to compromise the rest of the network.

quote:

Originally posted by deepocean:

quote:

Originally posted by smschulz:
It works better than all the rest but you must be able to forward port 3389 on your router, have a static IP or use a Dynamic DNS Utility.
Windows Home Version does not have Remote Desktop.

What are the security concerns of using Windows Remote Desktop? The computers using it all have Windows 7 Pro.

The only security concern is the desktop is "listening" for a connection.
Brute force scans have a possibility to connect if weak passwords are used.
Additionally, if really concerned you can change to a non-standard port other than 3389 to reduce the risk.
If really concerned about security then there are two-factor authentication methods or you could first connect with a VPN.
Again, a little over kill for most normal use scenarios.

quote:

Originally posted by sigmonkey:

It can take a few minutes for an active RDP listening machine to be scanned and exploited, and often a payload dropped on that machine, or that machine used to compromise the rest of the network.

That sounds BAD. Is there anything I should be aware of with regard to using the Google Chrome remote desktop? I'm thinking of using that as a backup to one of the paid services.

quote:

Originally posted by deepocean:

quote:

Originally posted by sigmonkey:

It can take a few minutes for an active RDP listening machine to be scanned and exploited, and often a payload dropped on that machine, or that machine used to compromise the rest of the network.

That sounds BAD. Is there anything I should be aware of with regard to using the Google Chrome remote desktop? I'm thinking of using that as a backup to one of the paid services.

It sounds bad, but it is not all that common unless you use a weak password.
Certainly possible but I have had many, many connections over the years and never any exploits.
But anything is possible, right?
Just weigh you risks and costs associated like anything else in security.

A public facing Windows RDP is subject to continual brute force attack on passwords.

Yes, it's "bad".

I have been working with computers since 1980, involved in the 80s in the US of AF in IT with DARPA and also worked with Microsoft in the development and implementation of RDP under Citrix Winframe/MetaFrame and MS Hydra during the 90s, as well as full time the past 26 years in consulting and corporate enterprise capacity. I live this stuff everyday, and really don't have time or energy to measure male sexual appendages with anyone over discussions if all of this. (and one of the reasons, I quit getting involved in discussions of such things), but I stepped in on this one, so...

There is still a great deal of art to the science, and more "ways to skin the cat" than are able to be properly dissected or discussed in such a venue as this forum.

Bottom line. If you want to use Windows RDP protocol to connect, you need a VPN to wrap the session.

The longer a method is "in use" and the more times it is employed, the greater risk to anyone who uses it.


"security" is a constant game of trying to stay one step behind the people who are trying to exploit you, all the while, hoping they don;t hit you with the "zero day" or "day before your figure this shit out" exploit.

I’m just starting to use RealVNC which is free for non-business use. The server goes on a Windows 10 NUC mini PC that I use to control my GoTo telescope mount. I don’t use it for anything else. I can’t speak to how secure it is. I’m just throwing the name out there for consideration. I run the client side software on a Galaxy Tab A to control the mount via the PC. I can smoke a cigar and enjoy some scotch while imaging distant galaxies without having to get out of my chair.

Well, someday anyway. I’m still in the early learning phase.

Anyway, RealVNC might be an option to look at.

Remote Utilities, Any Desk.

IMO just sign up for Teamviewer and be done with it.

What I do is:

Use their 2-step authentication so that you have to get a code on your phone to sign in to your TV account, in addition to knowing your account username and password.

On the target PC (Extras > Options > Security), disable random passwords, create a very strong custom password, and use the whitelist such that only your account is allowed to connect to the target PC.

∆∆∆∆∆∆∆ This.

Used LogMeIn for ages And have switched to TV 10 years or so ago. It's excellent.

Start with the free version And move upwards if You feel comfortable with it.

0-0

quote:

Originally posted by sigmonkey:

I have been working with computers since 1980, involved in the 80s in the US of AF in IT with DARPA and also worked with Microsoft in the development and implementation of RDP under Citrix Winframe/MetaFrame and MS Hydra during the 90s, as well as full time the past 26 years in consulting and corporate enterprise capacity. I live this stuff everyday, and really don't have time or energy to measure male sexual appendages with anyone over discussions if all of this. (and one of the reasons, I quit getting involved in discussions of such things), but I stepped in on this one, so....

Getting a little testy are we?

quote:

Bottom line. If you want to use Windows RDP protocol to connect, you need a VPN to wrap the session.

I don't disagree at all.
That or 2FA.