Skip to main content

How to import Putty Saved Connections to mRemoteNG

Just started using mRemoteNG and its being very cool to connect to different remote connection with different protocols e.g Window Remote Desktop, VNC to Linux, SSH, HTTP connection etc. from a single application.

As new user I configured some remote desktop connection which was quite easy to figure out. But when I wanted to add SSH connections, it came in my mind to import all of the saved connections in the putty. But I couldn't figure it out how can it be done, though it was quite easy and here are the steps.


  • Open your mRemoteNG
  • Create a folder if you want segregation of multiple networks
  • Create a new connection
  • Enter the IP address of remote server under connection in Config pane
  • Under the config pane, select protocol "SSH version 2". 
Once you select protocol to SSH version 2 you are given option to import putty sessions, as shown in the snap below.


In the above snap, I have imported CSR-AWS session from my saved sessions in Putty.



Comments

Post a Comment

Popular posts from this blog

Understanding SRV vs NS Records in DNS

DNS (Domain Name System) is a crucial part of how the internet works, converting domain names into IP addresses and directing traffic. Within DNS, different types of records serve specific functions. Two key types are SRV (Service Records) and NS (Name Server Records) . SRV (Service) Records SRV records are used to define the location of specific services. These records are crucial when multiple servers can provide the same service (e.g., VoIP, messaging) and a specific server needs to be selected. They contain the following components: Service & Protocol : Defines the service (e.g., _sip , _xmpp ) and protocol ( _tcp , _udp ). Priority & Weight : Direct traffic to the most preferred server. Port & Target : Specify the server's port and hostname. Example: _sip._tcp.example.com SRV 10 60 5060 sipserver.example.com NS (Name Server) Records NS records delegate the authority for a domain to specific name servers. These name servers are responsible for answering DNS queries

BGP Local Preference Controlling Outbound Traffic in BGP

In BGP, Local Preference is used to control the outbound traffic path. It helps you decide which egress point (exit point) should be used when you have multiple connections to external networks, such as ISPs. Local Preference is an attribute that is local to your AS and is shared with all iBGP peers but not with eBGP neighbors. Higher Local Preference = More preferred outbound path. Example Scenario : You have two external links: ISP1 (via CE1) and ISP2 (via CE2). You want traffic to prefer ISP1 for all outbound traffic. Network Topology : CE1 (connected to ISP1): 10.0.1.1/30 CE2 (connected to ISP2): 10.0.2.1/30 iBGP Router (Internal) connected to both CE1 (10.0.1.2/30) and CE2 (10.0.2.2/30). Configuration on CE1 (Higher Local Preference) : Create a route map to set the local preference to 200 for routes learned from CE1: route-map SET_LOCAL_PREF permit 10 set local-preference 200 In the BGP configuration for CE1, apply this route map to the neighbor: router bgp 65001 ne