Note that the usage of the terms filename and foldername are to be replaced with the file or folder you are manipulating.

Compress and Back Up Files and Folders

zip -r putty.zip putty/

This command would compress the putty folder, along with its contents, into a file named putty.zip.

zip  putty.zip putty.html

This command will compress the file putty.html into a zip file renamed putty.zip.

Create Files or Directories

rm filename.html

This command will remove the file designated.

touch filename.html

This will use the touch command to create a file.

mkdir foldername

This uses the make directory command to create a new file directory or folder.

rmdir foldername

This will use the rm or remove command on a chosen folder or directory. Be sure that any folder you attempt this command on is empty.

mv foldername1/file.html foldername2/file.html

This will enage the mv or move command to move a designated file. This command can also be used to rename a file.

Directory Navigation

cd

This command is used to change a directory or a common method used for moving files from one folder to another.

cd foldername1/foldername2 would move you to foldername2.

cd /

This command would move you to a root directory or folder.

pwd

Representing the present working directory, this command will print to your console the current directory where you are working.

List Contents

ls

This will list the contents of the current directory you are working in.

ls -1

This command will show the files properties, or long format, such as size, permissions, date modified and more.

ls -r

This command will list your subdirectories recursively.

ls -a

This command will show all files including hidden ones.

Utilizing these shortcuts can save time and help any user to maximize their time working with PuTTY and executing basic shell commands.

Why Use SSH?

There are a few reasons why users choose to use tools like PuTTY to manage their SSH requirements.

1. Speed
2. Accessibility

As well as its capacity for port and GUI forwarding.  An SSH server also has multiple authentication methods.

• Challenge/Response
• Password/Public Key
• Host-Based

How Can You Use SSH with a PuTTY Client?

You can use PuTTY to create basic SSH connections. A basic connection can be used to access files or to achieve a remote connection.

Elements of the benefits of tunneling with PuTTY via SSH include:

• Remote Forwarding
• Local Forwarding
• Secure Connection/Client to Server
• Access on Inaccessible Networks

SSH tunneling offers the capacity for multiple connections such as single tunnel points, multiple ports, and multiple destinations. This can greatly relieve the clicking nightmare that could arise for individuals who monitor tech support elements with programs like PuTTy.

File Copying with PuTTY SSH

Another reason to launch an SSH session in PuTTY is when you need to copy files from one location to another. This form of SSH session allows a user to transfer files quickly and securely with support for entire directory structures.

Remote Commands

Last but certainly not least is PuTTY’s remote viewing and connection capabilities. This is highly useful for monitoring, configuring, or even running full tech support from a remote location.

Getting to know your PuTTY client as well as the SSH tunnels and sessions you can manage within it is really more than half of the battle. If you can learn the ins-and-outs of this type of programming, you can open up distinct possibilities in furthering your knowledge, or even education SSH tunneling with remote access clients like PuTTY.

PuTTY Command Sender/ PuTTYCS

This productivity tool is a definitive hit with PuTTY users. It works by eliminating repetitive tasks that are performed on separate servers. PuTTYCS allows users to send a unix command to several PuTTY server windows at once. Users can utilize this tool in backing up files, starting and stopping processes, viewing log files and more, with one simple and time saving command.

PuTTYTabs

PuTTYTabs will provide a bar that floats above the PuTTY client sessions in TABS. Selecting any of the tabs pulls the chosen tab to the front of the session so it is available for use. Many remote tech support users have found this add-on to be a vital part of their PuTTY sessions since it is highly common for those in technology fields to require the usage of more than one SSH server on a regular basis.

PuTTY Session Manager

Another great tool for remote support  allows you to organize your PuTTY sessions into folders as well as assigning them hotkeys. Although this will require Microsoft .NET 2.0 it will also make many of the required functions more automated by assigning hotkeys to each session.

Quest PuTTY

This tool adds a great active directory single sign-on feature to PuTTY. Using SSPI, or MS Security Service Provider Interface, this will add a new menu-item called GSSAPI. Listed under Connection then SSH, this adds the GSSAPI option to your PuTTY configurations GUI.

PocketPuTTY

The real geek will definitely need a portable version of PuTTY. This version runs on Windows Mobile 2003, 5.0 OS. This gives the power of remote connection to those that are on-the-go.

These five PuTTY add-ons will most certainly go a long way in making PuTTY sessions more convenient, flexible and time-saving instruments for SSH success.

Many applications will recognize these changes and make their own adjustments in display accordingly. When applications do not recognize alterations in resized windows, you may suffer from issues such as application crashes or corrupted displays. This is why you may need to disable the resizing options in PuTTY.

Disabling Resizing Options in PuTTY

1. Open the PuTTY application and click on the Session link on the left-hand panel.
2. On the right-hand panel, click the Default Settings option, then the Load button.
3. In the right-side panel the Window option should be clicked, then select the Forbid resizing completely option.
4. Additionally, you can also choose to select an option that will only support the font size being changed instead of the rows and columns. To do this simply check the Change the size of the font on the displayed button options.
5. Once you have selected the desired formatting options, click on the Session link in the left-side panel.
6. Select the session name you originally labeled it with or you can choose the Default Settings option.
7. Click the Save button to save these settings.

You will now be able to use the programs that were having corrupted display issues or other issues due to the resizable session terminal windows. However, if you correct this issue and are still receiving messages about corrupt display, or your application simply will not work with these PuTTY options enabled, you may have a problem with the original program. If so try heading back to the site you downloaded it from and check for bug fixes or other issues such as those you are experiencing. Chances are, someone who has had the same issue has found a fix that can help you too.

Launch Frequently Used Sessions Quickly

1. Create a PuTTY windows shortcut and rename it.
2. Right-click on the shortcut and choose Properties.
3. In the end append of the Target Field, add -load putty-sessionname.

Anytime you click on the newly created shortcut it will automatically load the PuTTY session you set.

Start PuTTY in a Full Screen

1. Launch PuTTY and choose Select a Session.
2. Click Load. On the menu tree select Window, then Behavior.
3. On the right panel, check the box next to Full Screen on Alt Enter.

You will now be able to select Alt + Enter anytime you have a PuTTY session open and have full screen capability.

Launch PuTTY Session Window Maximized

1. Create shortcut for a PuTTY session.
2. Right-click on the shortcut and choose Properties.
3. Select the Run drop-down list and choose Maximized.

From now on each time you use this particular PuTTY session shortcut it will open in a maximized mode.

Delete All PuTTY Sessions Simultaneously

If you have recently upgraded to a new computer, you may need this command. You will need to execute a PuTTY cleanup session. Once you have transferred your PuTTY sessions to a new machine you may need to execute this command.

In the command line enter  C:>putty -cleanup

You will receive a warning message announcing that the procedure will remove all of your registry entries.

Click Yes to remove all of your PuTTY sessions as well as the random seed files from your Windows registry.

This is the quickest process to removing your PuTTY sessions. If you are a regular user, manual deletion of each session can take a significant amount of time.

There are ways around this issue, but in order to achieve them, you must have a bit of knowledge on how to manipulate SSH servers.

To begin you will need the PuTTY client. Once downloaded, execute the program.

Click on the Session tab and add the IP address of your SSH server and save the session.

Creating Tunnels

There are other servers you will need to gain access to. Select Tunnel and enter the values for each type of server. The mail server located at 192.168.0.5 and HTTP server with an IP destination of 192.168.0.60:80. Once entered click Add.

Test Your Connections

Open your SSH connection and select the session for the HTTP server. You should now be able to browse the available data.

Set Up the Mail Server

The correct location for your mail server is localhost. You are free to use any mail server you like. Microsoft Outlook, Postfix, Sendmail or Mozilla Thunderbird work for your purposes. You should notice the option to Leave messages on server. However, if you already have an email program on your computer, you may want to allow that mail server to remain default.

You will also need to assign an IP address to the adapter. The adapters will be supplied with consecutive address numbers. The first will be 10.0.0.1, the second will be 10.0.0.2 and so on. Be sure that you do not enter a default gateway.

Once you have completed the process you should reboot your computer and make sure you have no other instances of your mail server or HTTP access open.

For this reason those who have a bit of knowledge and the desire to monitor their own homes, regardless of their location, many have begun to use applications such as PuTTY, in combination with digital or web cameras, to remotely monitor their own properties.

Set Up

To begin you will need to install the PuTTY application on your PC and set it up for remote access and viewing. Once complete, locate your IP address by typing ipconfig in the command prompt box. Record the IP number and save it, as well as the PuTTY installation file onto a flash drive.

Before leaving the host computer location do a minor check for a few key issues.

1. Be certain you have set up your computer to allow remote connections.
2. Make sure you have an easy-to-access shortcut for your web cam hardware.
3. Check to be sure Windows Desktop Assistance is enabled.
4. Double-check that the area the cam points to is the desired one for remote viewing. Most users will have their camera pointing towards key entrances to their home, or secondary entrances such as garage or basement doors.
5. Be sure to leave your computer running. The monitor can be turned off to provide more covert coverage, however, you may than need to be certain there is an alternative light source for better quality viewing or recording.

Remote Monitoring

Once you arrive at the PC you will be using to view your home PC, you will also need to install PuTTY onto it as well.

Once installed open the PuTTY program and enter the destination IP, the one recorded previously, into the Host Name box on the configuration user interface. Select the SSH option and click Open.

Once you have the remote desktop open, you can than initiate the web cam program. If you left it on, you have only to simply begin viewing. If you plan to video record the coverage you can initiate the recording from the host computer, or from the one that is viewing it. However, if you run the recording program from the remote computer, you may be required to leave the remote desktop visible to ensure you have recorded the proper view.

One option for securing your connection is to use an SSH client as well as a remote computer that you can control and trust.

What You Will Need

1. You will need a remote host running an SSH
2. Firefox
3. Pidgin for your instant messenger needs
4. PuTTY installed and loaded on your local machine

Step One

Execute PuTTY and create a new session. Have the session connecting to the remote host running the SSH server. You will need to be sure to fill in the hostname, the port number and to check the SSH option. Give the session a name and then save.

Step Two

You will need to configure your secure tunnel. Select Tunnels on the left and set up the dynamic forwarding for the local port. Under the Add new forwarded port option, type 7070 as the source port. Leave the destination blank and check Dynamic and Auto. Now click the Add button.

That should create your tunnel. There is no need for more than one, but remember to save your session so you do not have to repeatedly configure the tunnel for this activity.

Step Three

You will need to double-click on the connection profile. Type in the username and password once prompted. This will connect you to the remote SSH box.

Step Four

The next step is to configure Firefox. Head to the Tools option, General, and the Connection Settings option to bring up the next set of options to configure.

Select Manual proxy configuration. While you will leave most of the empty fields blank, you do need to enter 127.0.0.1 into the SOCKS Host field. For the port number enter 7070.

Step Five

Start up Pidgin and select the Tools option, and click Preferences. Choose the Proxy option, and select SOCKS 5 as the proxy type. Enter the host as 127.0.0.1 and the port as 7070. Click on close.

You are done. From this point on, as long as you log into the remote SSH first with PuTTY, your Pidgin and Firefox traffic will be routed through a secure tunnel to the remote host, then out to the internet.

The junior administrator took the initiative to see what he could to do help the situation. He quickly searched the Internet for options on remote shell, telnet access to Cisco routers. The number one result turned out to be a remarkable Open Source program called PuTTY. The administrator downloaded PuTTY and launched it. He was surprised that there was no installation routine; PuTTY is a self-contained executable program and does not use registry entries or other supporting DLL files to run.

Once the program started, he input the IP address for the core network router; in this case it was also the default gateway address that was easily obtained. He then hit “Open” in PuTTY to connect to the core. To his amazement, the terminal session started without any delay. The junior administrator put in the network password and was instantly connected. The core terminal was reporting a problem with a failed power unit and was not able to boot because of the failed unit. He quickly notified the senior administrator and they worked quickly to remove the failed power supply. The unit would boot with it removed, but not with it installed. So after one additional reboot, the core network was running once again.

Thanks to PuTTY and the quick thinking of the junior administrator, this problem was resolved quickly and everyone was thankful to get back to work.

It took more than an hour on hold to reach the PBX vendor’s technician because the company didn’t fully support the old equipment any longer. But, they found a technician who had worked for the company for the last 20 years and he had some ideas. They first needed to find a laptop computer with a serial port. Most laptops built in the last few years don’t contain a serial port, so this was yet another challenge. Then they needed to search for and download an Open Source program called PuTTY. The technician explained that PuTTY is an Open Source terminal emulation program that tricks the PBX mainframe into thinking there is a physical terminal connected when, in actuality, it is just this little amazing piece of software.

The technicians found the serial port enabled laptop, the cable and easily downloaded and installed the PuTTY software. They were now ready to connect and see what was wrong. They started up PuTTY and connected quite easily to the PBX terminal session. As soon as they connected and logged into the console, they saw that the CPU board on the main PBX cabinet was failing. It was trapping errors and processing some requests, but deflecting others. Thankfully the PBX system was setup with a redundant spare CPU in another cabinet. All that needed to be done was deactivate the faulty CPU and then activate the backup CPU as the primary system board. As soon as the configuration was saved, all call traffic returned to normal conditions. PuTTY and the seasoned PBX technician helped resolve the problem quickly, once all the components were put together.