I soon will have a need for remote connections and manipulation of other systems. Is TeamViewer the 'go-to' software for the 'pros'? I'm not looking for freeware (except to try it), but a good solid software for remote connections, making diagnosis' and software configuration, troubleshooting, etc.
Thanks,
Salt
The only thing I can think of other than TeamViewer is the built in Windows Remote Desktop software. The only problem is it only works on LAN which means you can only connect to PCs in your own network. If you only need LAN connection, the built in software is okay. Remote Desktop Connection (RDC) - Network
Thanks for your comments. I use RDC in my LAN now, but will need remote access outside LAN. TV seems to be the one of choice.
I 2nd Teamviewer.
Once you connect via Teamviewer you could create yourself a password so you can connect whenever you need, that way when assistance is required you don't even need the passcode as you would already have a permanent one.
This guide will help show you how to set that up - http://www.teamviewer.com/en/res/pdf..._access_en.pdf
That all depends on security protocol you follow though, in some cases, the user opening Teamviewer and giving you the pass code may be deemed safer.
Regards,
Jamie
Thanks, Jamie. I appreciate the pointers and guide.
I also recommend TeamViewer. Another issue with RDC is that you can only run the RDC server on machines that are running Pro or Ultimate. For instance, a machine running Win 7 Home Premium can connect to a machine running Win 7 Pro, but the Win 7 Pro can't connect to the machine running Win 7 HP.
Good point...only pro and above can host RDC sessions.
What about security issues, client-side and host side? Seems like there must be some. This thread contains several assertions that it is not secure:
TV Security
But I am pretty serious when it comes to my security, so it seems like there could be ways to minimize risks. A few I can think of are:
1. Run TV from a virtual machine or use a special system drive/partition for TV sessions (multi-boot or shut down and swap system drives).
2. Don't allow TV to run unless a session is...in session.
3. Don't use wake-on lan (I guess if needed, one could use vpn or ssh instead?)
4. Use the strongest security measures and authentication TV allows
5. Be cognizant of what is on the clipboard when you connect and what you place on it while in session. I guess it could be disabled altogether, but clipboard copy/paste function could be quite useful for remote sessions (I use it on my LAN).
6. Edit windows firewall to accept no incoming connections when TV is not in use (this will allow web browsing and such, but makes your machine invisible and unavailable).
Edit: 7. Set up a separate Remote Access machine and place it on a separate subnet. Any incoming connections would be restricted to that subnet.
Anyone have any thoughts on the security issues involved and other ideas on how best to batten down the hatches? I think I like #7 the best and is likely how I would set up.
Last edited by msalton1; 03 Sep 2014 at 13:35.
Just wanted to say thanks for the comments here. I think TV is the no brainer here, at least to start. TV claims to be very secure, but I think the security measures mentioned in my last post (specifically #7) will cover the bases.
Again, thanks!
Quote