DiaryFolio

This article will show step by step instructions How to setup tunnelling in Putty . This is extremely useful if a port is not opened over firewall but you can hop to a server with access and from there you can hop to another and so on.. Essentially it forwards port if you have access to atleast one port. Create a new SSH session - and save it. And click on load to load the settings. Choose the server and port  where you have already got access and firewall works. (eg.  ServerA, Port: 22) Select Tunnels from the Left Menu, specify the Source Port and Destination: The tunnel is created between the REMOTE UNIX box and your local machine (localhost). So, the source port will be the port on the REMOTE UNIX box  to which you want to talk to at a specific port which you can't access (eg Port 37150). And the destination will be your localhost, which will act as the other end your tunnel session [ad#ad-3] Click Save after selecting the"Session" Open the saved sessi

Hope you all have "Putty" as your favourite ssh client? For me too..   But sometimes, I felt there are some issues when you are working with 100's of servers and multiple locations.  This article will guide you to achieve Putty portability: by storing sessions in files rather than in windows Registry Automate creation of Putty sessions:  No more manual entries one by one Consistent coloring of Putty sessions for team Consistent naming conventions for Putty sessions "Keepass" to putty integration: Password management and automated login Use "SuperPutty" to allow multiple putty sessions in a single Tab Pre-requisite   Full package available to download at end of this document Basic knowledge of coding. Overall understanding of tools Portable Putty: Ability to store sessions to file ( http://jakub.kotrla.net/putty/ ) Optional: AutoIT ( http://www.autoitscript.com/site/autoit/ ) : For automation purpose in Windows PC's. (Alternatively