Open new sessions on the same instance

[Portugal]

Hello.

I've been using SecureCRT for a while, great product
Now that I'm using eve-ng to emulate some routers, every time I click on a router it opens a new session on a new SecureCRT instance, instead of opening that session in a new tab on the same instance.
That's a problem, because if I've 20 routers on the topology, I'll have 20 instances of SecureCRT opened.

Is there a way to force SecureCRT to open new sessions on an already running instance.

I'm using SecureCRT 7.3.7 (x64 build 1034) on Windows 10 1803

Best regards.

[berdmann]

Hi Portugal,

If you navigate to Options > Global Options > Terminal, do you have the "Connect sessions in tabs" option enabled?

If not, please enable "Connect sessions in tabs".

Does enabling this option provide you with the desired behavior?

[Portugal]

Originally Posted by berdmann

Hi Portugal,

If you navigate to Options > Global Options > Terminal, do you have the "Connect sessions in tabs" option enabled?

If not, please enable "Connect sessions in tabs".

Does enabling this option provide you with the desired behavior?

Hello berdmann.
Yes, that option is already enabled.
It's strange that this behavior is exclusive of eve-ng. It doesn't happen with GNS 3.
Do you have any other suggestions?

Best regards.

[Portugal]

No other suggestions?
I've made a small video showing the issue --> https://mega.nz/#!qTAjzKgC!Rl6lyXMMK...HQ1B4KWA9xZ_aY
Does SecureCRT version 8 solve this issue? If so, I'll upgrade.

Best regards.

[Portugal]

Hello.

I've found a solution on comment made on a Youtube video.
In order to force SecureCRT to open a new tab instead of a new session, open the Global.ini file located on \Users\<username>\AppData\Roaming\VanDyke\Config, locate the line:
D: "Single Instance" = 00000000
and change it to:
D: "Single Instance" = 00000001

[berdmann]

Hi Portugal,

I am happy to hear that you were able to find a work-around by forcing SecureCRT to use a single instance!

Have a great day!

[Manjinder]

Solution Worked for me as well.

Thank you for the solution !!.

In order to force SecureCRT to open a new tab instead of a new session, open the Global.ini file located on \Users\<username>\AppData\Roaming\VanDyke\Config, locate the line:
D: "Single Instance" = 00000000
and change it to:
D: "Single Instance" = 00000001

[MRAQAMKL]

Changing - D: "Single Instance" = 00000001
did not work for me.. not sure why EVE opens an instance of Secure CRT for each session. I do hope there is a better solution..

[berdmann]

Hi MRAQAMKL,

I am not familiar with EVE. Do you mind elaborating on EVE and how you are launching your SecureCRT sessions?

[stefan13]

Hello,

I'm facing the same problem - was there any solution in the meantime?

SecureCRT does open a new window for each SSH/Telnet session for device in EVE-NG.

When I use SecureCRT for Windows, the new session is opened as a Tab.

For both Windows and MacOS the single instance is activated.

D: "Single Instance" = 00000001

Thanks a lot for your support.

brgds
Stefan

[jdev]

Originally Posted by stefan13

I'm facing the same problem - was there any solution in the meantime?

SecureCRT does open a new window for each SSH/Telnet session for device in EVE-NG.

When I use SecureCRT for Windows, the new session is opened as a Tab.

For both Windows and MacOS the single instance is activated.

D: "Single Instance" = 00000001

Dear stefan13,

Would you be so kind as to provide some clarification?

1. Does your comment, "SecureCRT does open a new window for each SSH/Telnet session for device in EVE-NG" apply only your macOS machine?
   
2. What is the exact version of SecureCRT (from the About SecureCRT... window) running on your macOS machine?
   
3. What version of macOS are you running on that machine?

--Jake

[stefan13]

Originally Posted by jdev

Dear stefan13,

Would you be so kind as to provide some clarification?

1. Does your comment, "SecureCRT does open a new window for each SSH/Telnet session for device in EVE-NG" apply only your macOS machine?
   
2. What is the exact version of SecureCRT (from the About SecureCRT... window) running on your macOS machine?
   
3. What version of macOS are you running on that machine?

--Jake

Hello Jake,

the issue occurs only on my MacBook. The Windows version works fine.
I use the latest SecureCRT beta v9.0 on MacOS BigSur.

Thanks
Stefan

[jdev]

Originally Posted by stefan13

the issue occurs only on my MacBook. The Windows version works fine.
I use the latest SecureCRT beta v9.0 on MacOS BigSur.

Stefan,

Thanks for the clarification!

Some earlier versions of SecureCRT v9.0 on macOS platforms introduced a problem where Single Instance functionality was broken.

The next public release of SecureCRT v9.0 (any build v9.0.0.2389 or newer) should resolve the problem you're experiencing on supported macOS platforms. Big Sur is not yet supported, so your mileage may vary.

If you'd like to try out a pre-release version of SecureCRT v9.0 for macOS that's newer than the one you currently have and might resolve the issue, then:
Please send an email message...

• To: support@vandyke.com
• From: the email address which corresponds to your VanDyke Software download account
• Subject: ATTN Forum Thread #13243 - Single Instance Fix for SecureCRT v9 on macOS

If you send the email from your VanDyke Software download account email address (or at least provide the address in your email body), we can make a newer version available to you that may resolve the problem for you in SecureCRT v9.0 on your macOS system.

--Jake