2. Setup the session into SecureCRT

3. Run the session: Connection Refused

Double Click on session:

Connection refused

4. Change localhost to 127.0.0.1

Double Click on session and I get nothing. No message, no error … it isn’t connecting.

5. Problem research

VMs works with named Pipe to provide console connectivity, and unfortunately SECURTCRT doesn’t support it. To do so, we need a Proxy , a Soft in th Middle to do the Mapping from Named Pipe to whatever SecureCRT can understand and connect to.
Source: http://www.noshutdown.ma/cisco-ios-xrv-securecrt/