Difference between putty and remote desktop?

Question

Can anyone please tell me the difference between putty and remote desktop which is a Windows OS feature

Answer 1

Putty is a terminal emulator type of tool... a means of logging-in to a web server remotely so you can get ROOT access and perform Linux commands much the same is if you were sitting at a terminal directly connect to the server, in the same room with it. It is a type of remote access... a type commonly referred to as "Telnet"... but very different from the "Remote Access" to which you refer in your question.



"Remote Desktop" is just Microsoft's name for its "Remote access," which means using one Windows machine to go out onto the internet and access yet another, REMOTE Windows machine...



...and the person doing said accessing is able to see the REMOTE Windows machine's desktop on HIS local machine's desktop the same as if he were sitting at the REMOTE Windows machine's keyboard.



It's a means of a support person, for example, being able to access the computer of someone he's trying to help, so that he can control the remote machine and install something, or uninstall something, or configure something, or fix something just the same (only slower, and more maddeningly) as if he were out in the field, sitting at the keyboard of the computer into which he's remotely logged.



Windows has remote access capability built-in to it, but it's very poorly done. One would think that Microsoft would have done a better job...



...but then, again, Microsoft wrote Windows Paint, too. So, no surprise, then, that "Remote Desktop" isn't as good as it could be at what it does. I, presonally, NEVER use it. Life's too short.



The preferred remote access tool of this type used to be "pcAnywhere" until Symantec bought it and ruined it.



Today, "UltraVNC" is considered a best-of-breed remote access product for use in Windows.



Other similar products which incorporate a server into the mix for administrative purposes include: LogMeIn, CrossLoop, Team Viewer, and others. Of them, I prefer the higher-end products by the maker of LogMeIn...



...but I use CrossLoop, which is completely free to everyone, and which, because of the way it operates, gives the user a better sense of security; and a better feeling that the helper can't ever log-in without them knowing about it.



Or I use UltraVNC. And I'm experimenting with a couple others, one of which is truly amazing so far... and also free, unbelievably.



Hope that helps.





NOTE TO bhas_singh: Most "answers" web site have a pretty serious policy about not just copying and pasting from Wikipedia and other such places. Any of us could do that and fill our answers with air and fluff. If you know something, and can make a real contribution, then please do so. But don't just copy-'n-paste crap from Wikipedia and places similar.

Answer 2

Putty Remote Desktop

Answer 3

If you want to use either Remote desktop or Remote access, your PC and Remote PC must be in same network or you should have a successful network connection. I think Remote desktop is little bit easy to take full control. But when you take remote access remote user can see what you are doing on his PC. but this feature is not possible in Remote desktop. This is the main different between these two. If this is not in same network Teamviewer is pretty simple tool for this.

Answer 4

Remote Desktop is a Windows feature. Putty is a standalone client used for Telnet, SSH, etc.

Answer 5

hmmm!



PuTTY is a terminal emulator application which can act as a client for the SSH, Telnet, rlogin, and raw TCP computing protocols. The name "PuTTY" has no definitive meaning[1], though 'tty' is the name for a terminal in the Unix tradition, usually held to be short for teletype.



PuTTY was originally written for Microsoft Windows, but it has been ported to various other operating systems. Official ports are available for some Unix-like platforms, with work-in-progress ports to Classic Mac OS and Mac OS X, and unofficial ports have been contributed to platforms such as Symbian and Windows Mobile.



PuTTY was written and is maintained primarily by Simon Tatham and is currently beta software. Licensed under the MIT License, PuTTY is free and open source software.





Features



Some features of PuTTY are:



* The storing of hosts and preferences for later use.

* Control over the SSH encryption key and protocol version.

* Command-line SCP and SFTP clients, called "pscp" and "psftp" respectively.

* Control over port forwarding with SSH (local, remote or dynamic port forwarding), including built-in handling of X11 forwarding.

* Emulates most xterm, VT102 control sequences, as well as much of ECMA-48 terminal emulation.

* IPv6 support.

* Supports 3DES, AES, Arcfour, Blowfish, DES.

* Public-key authentication support.

* Support for local serial port connections.

* Self-contained executable requires no installation.





Applications



Main functions are realized by PuTTY files themselves:



* PuTTY - the Telnet and SSH client itself;

* PSCP - an SCP client, i.e. command-line secure file copy;

* PSFTP - an SFTP client, i.e. general file transfer sessions much like FTP;

* PuTTYtel - a Telnet-only client;

* Plink - a command-line interface to the PuTTY back ends;

* Pageant - an SSH authentication agent for PuTTY, PSCP and Plink;

* PuTTYgen - an RSA and DSA key generation utility;

* pterm - a standalone terminal emulator.





AND ABOUT



Remote Desktop Protocol (RDP) is a proprietary protocol developed by Microsoft, which concerns providing a user with a graphical interface to another computer. The protocol is an extension of the ITU-T T.128 application sharing protocol.[1] Clients exist for most versions of Microsoft Windows (including Windows Mobile), Linux, Unix, Mac OS X and other modern operating systems. By default the server listens on TCP port 3389.





Features



* 32-bit color support. 8-, 15-, 16-, and 24-bit color are also supported.

* 128-bit encryption, using the RC4 encryption algorithm.[8] (this is the default security; older clients may use encryption of lesser strength). But because of the man-in-the-middle vulnerability in pre-version 6.0 implementations, in many circumstances the traffic can be decrypted along the way.[9]

* Transport Layer Security support.

* Audio Redirection allows users to run an audio program on the remote desktop and have the sound redirected to their local computer.

* File System Redirection allows users to use their local files on a remote desktop within the terminal session.

* Printer Redirection allows users to use their local printer within the terminal session as they would with a locally or network shared printer.

* Port Redirection allows applications running within the terminal session to access local serial and parallel ports directly.

* The clipboard can be shared between the remote computer and the local computer.



The following features were introduced with the release of RDP 6.0 in 2006:



* Remote Programs: Application publishing with client-side file type associations.

* Seamless Windows: Remote applications can run on a client machine that is served by a Remote Desktop connection.

* Terminal Services Gateway: Enables the ability to use a front-end IIS server to accept connections (over port 443) for back-end Terminal Services servers via an https connection, similar to how RPC over https allows Outlook clients to connect to a back-end Exchange 2003 server. Requires Windows Server 2008

* Support for remoting the Aero Glass Theme (or Composed Desktop), including ClearType font smoothing technology.

* Support for remoting of Windows Presentation Foundation applications: Compatible clients that have .NET Framework 3.0 support will be able to display full Windows Presentation Foundation effects on a local machine.

* Rewrite of device redirection to be more general-purpose, allowing a greater variety of devices to be accessed.

* Fully configurable and scriptable via Windows Management Instrumentation.

* Improved bandwidth tuning for RDP clients.

* Support for Transport Layer Security (TLS) 1.0 on both server and client ends (set as default).

* Multiple monitor support. Spread session across two monitors.