Skip to main content

Putty Tunnels and Accessing remote IP blocked via firewall

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)

  • Putty Create Session

  • 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 session for which you just created the Tunnel and login to it.  This is because tunnels are created only when you login successfully . (eg. Access ServerA via port 22)

  •  To test Connectivity: Open a command prompt and try TELNET connection on the port   "C:/> telnet localhost 37150"   . If the tunnel is successfully created a telnet connection should establish. Exit out of it.

  •  Access the URL of your application (or dmgr console) by replacing the IP address of the server with ‘localhost’. From the above example:
    http://serverA:37150/ would become http://localhost:37150/

Popular posts from this blog

Syslog Standards: A simple Comparison between RFC3164 & RFC5424

Syslog Standards: A simple Comparison between RFC3164 (old format) & RFC5424 (new format) Though syslog standards have been for quite long time, lot of people still doesn't understand the formats in detail. The original standard document is quite lengthy to read and purpose of this article is to explain with examples Some of things you might need to understand The RFC standards can be used in any syslog daemon (syslog-ng, rsyslog etc.) Always try to capture the data in these standards. Especially when you have log aggregation like Splunk or Elastic, these templates are built-in which makes your life simple. Syslog can work with both UDP & TCP  Link to the documents the original BSD format ( RFC3164 ) the “new” format ( RFC5424 ) RFC3164 (the old format) RFC3164 originated from combining multiple implementations (Year 2001)

Create your own Passport Photo using GIMP

This tutorial is for semi-techies who knows a bit of GIMP (image editing).   This tutorial is for UK style passport photo ( 45mm x 35 mm ) which is widely used in UK, Australia, New Zealand, India etc.  This is a quick and easy process and one can create Passport photos at home If you are non-technical, use this link   .  If you want to create United States (USA) Passport photo or Overseas Citizen of India (OCI) photo, please follow this link How to Make your own Passport Photo - Prerequisite GIMP - One of the best image editing tools and its completely Free USB stick or any memory device to store and take to nearby shop A quality Digital camera Local Shops where you can print. Normally it costs (£0.15 or 25 US cents) to print 8 photos Steps (Video Tutorial attached blow of this page) Ask one of your colleague to take a photo  of you with a light background. Further details of how to take a photo  yourself       Take multiple pictures so that you can choose from th

Elastic Beats on pfSense : Installation and configuration

Summary Though in many cases syslog is preferred to transport the pfSense logs to external system, Elastic beats provides quite a niche way to send the logs while modelling the data alongside. This makes it ready-made to send to ElasticSearch directly and get ready-made outcomes like SIEM, performance etc. Pre-reqs A build server (preferably Ubuntu or Fedora) with internet connectivity shell access to pfsense server Basic knowledge of Elastic Stack (filebeat.yml configurations etc) Ensure connectivity is allowed from pfsense machine to your Elastic Stack receiver Setup Summary Connectivity tests Install dependencies in build server (vagrant, virtualbox, gmake, go etc) Download Elastic Beats source Make elastic Beats package for FreeBSD Copy binary packages to pfsense server Configure Beats to send to destination Configure ElasticSearch to view the data Installation Steps Connectivity tests Logon to pfsense server via Shel