Remote control opensuse windows

Yes No. Thank you! Any more feedback? The more you tell us the more we can help. Can you help us improve? Resolved my issue. Clear instructions. Easy to follow. No jargon. Pictures helped. Didn't match my screen.

Find a Partner. Become a Partner. Open Source Projects. SUSE Italia. SUSE Israel. SUSE Luxembourg. SUSE Nederland.

SUSE Polska. SUSE Suomi. About Us. Success Stories. Investor Relations. Social Impact. This is also not the place to use a password which you have preveously used in a mailling list, or as the password to your email account.

By allowing remote connctions to you machine, you move your computer password from the first category to the second category. On the internet there are people constantly trying to guess your password to break into your machine. These attempts use a list of "easy to remember" passwords.

The number of machines that have be broken into with this simple method is astonishing! I do not want to help you get on that list! So, Please take this warning seriously The second requirement is authorization. Now that we've verified who is on the other side of the line, is he allowed to do this?

And last, but in no way least, comes encryption. The Internet is basically insecure. So you need to realize when it's possible for outsiders to spy on your remote connections. Please considder this seriously, as with many of these methods a third person could easily read your bank account number, Username and even your password, giving him all he needs to financially ruin you! It is simple to setup, and secure. But only as your passwords are In this form you can start as many "Virtual Sessions" as "Server" has resources to handle.

This is similar to the windows " Terminal Server " functionality. Since you got access to the Physical screen, both the remote and the local users share this session and can see what the other is doing.

That is why these methods are used for remote support, and called " Remote Desktop Sharing ". This is similar to the windows " Terminal Server " function. As you can see VNC is very flexible, and therefor has lots of options each suited for diferent needs. Here we use a VNC setup designed to use minimal resources on the server. This is done by not starting the VNC session until someone tries to connect, and shutting the VNC session down as soon as client disconnects from it.

The VNC sessions are identical to the sessions on the physical screen of "Server", they even start of with the identical logon screen.