Beta Forum for the new SCRT?

[toloughlin]

Dusting off the 'old account here.

Saw there was a *beta* going on -- and had to install it.

Where can we discuss the look? Comments etc?

Thanks!

[Maureen]

You can discuss here (feel free to create new threads) or you can send your feedback to me at Maureen.Jett@vandyke.com.

Maureen

[bgagnon]

Hi toloughlin,

And of course, you can always use the forms provided on our website in the Support tab / Feedback section:

Submit a Bug Report
Ask a Question
Request a Feature

Or send an email directly to support@vandyke.com.

[toloughlin]

Hey guys! Thanks!

The new session list icons -- look like shortcuts to RDP sessions.

As a sanity check, I had some people at work check it out & they thought they were for connections to Windows boxes.

I have -0- UI creativity, so I can't recommend an alternative look -- but perhaps something less "BSOD"

[bgagnon]

Hi Tom,

I found a couple feature requests I thought might be fitting.

I have added this thread to the following feature requests in our product enhancement database:

• Ability to customize Connect Dialog and session manager icons
  
  
• Add ability to change session icon for protocol type

Should a future release of SecureCRT include either feature, notification will be posted here.

If you prefer direct email notification, send an email to support@vandyke.com and include "Feature Request - Forum Thread #12235" in the subject line or use this form from the support page of our website.

[elementxrs]

i love the new themes, it really updates the look and feel.
I agree with the session icons looking like RDP icons.

Maybe we could have the generic network icons for routers/switches available?
And a generic linux ssh icon?

[rguente]

Hi,

I use the actual Beta Version 8.0.0 (x64 build 1055) which looks very nice!

We use a jumphost which I start via firwalled (tunneled) session for the ssh-connection to our routers.
Sometimes SCRT starts the jumphost session in the background and then it's finish, which means it stops connecting to the router.
To connect to a router I then have to close/restart SCRT.
Is this already an already known bug?
Just contact me if you need more information.

Regards,
Robert

[bgagnon]

Hi Robert,

Sometimes SCRT starts the jumphost session in the background and then it's finish, which means it stops connecting to the router.

What do you mean by "finish"? Is the port forwarding session disconnected?

Do you have any anti-idle options configured in the Terminal category of Session Options?

Also, please clarify your port forwarding setup. Hopefully, you are taking advantage of this feature introduced in v7.1.x:

Changes in SecureCRT 7.1 (Beta 1) -- February 26, 2013
------------------------------------------------------

New features:

• Added support for dependent sessions so that a connection can be made to a jump host or SSH gateway before the session is connected.

As long as the "jump server" is capable of dynamic port forwarding this *dependent session* functionality should work.

[rguente]

Hi Brenda,

What do you mean by "finish"? Is the port forwarding session disconnected?

It starts the session on the jump host and then it hangs. There is no further session possible until a restart of SCRT.

Anti-idle

Yes. But only "send string".

I use the option from 7.1 (you helped my in the past with this )

Best regards,
Robert

[bgagnon]

Hi Robert,

Let's get timestamped trace options of the session that hangs and see if we can figure out why.

• Edit session to include custom data on each line of logging in the Terminal / Log File category of Session Options (%h:%m:%s:%t -- will give us format similar to shown below)
  
• Choose Log Session from File menu (supply name and location)
  
  The log file name can also be configured in same category mentioned above but start logging from the File menu instead of choosing Start log upon connect because the Session Options way does not include the initial negotiation information (including remote identifier).
  
  
• Choose Trace Options from the File menu
  
• Double-check there are checkmarks next to Trace Options and Log Session
  
• Connect session and take steps that cause issue
  
• Supply log file as an attachment to your response
  
  The timestamps will not appear in the terminal window, but should be logged.
  
  The output should look similar to:
  
  08:24:32:709 -- [LOCAL] : SSH2Core version 7.0.0.537
  08:24:32:709 -- [LOCAL] : Connecting to ###.###.###.###:22 ...
  08:24:32:709 -- SecureCRT - Version 7.0.4 (build 537)
  08:24:32:709 -- [LOCAL] : Changing state from STATE_NOT_CONNECTED to STATE_EXPECT_KEX_INIT
  08:24:32:709 -- [LOCAL] : Using protocol SSH2
  08:24:32:709 -- [LOCAL] : RECV : Remote Identifier = 'SSH-2.0-VShell_3_8_0_131 VShell'

Since trace options can contain sensitive information, feel free to send it as an attachment via email to support@vandyke.com. Please reference "Attn Brenda - Forum Thread #12235" in the subject line.

NOTICE: The requested troubleshooting data may include sensitive information (usernames, passwords, publicly-accessible host names or IP addresses, etc.).

Please redact sensitive information that would not be appropriate for email communication prior to sending the requested information.

If there is sensitive information that must be conveyed in order to provide a complete picture of the scenario you're facing, please let us know and we will set up a secure upload mechanism that can be used.

[rguente]

Hi Brenda

I can now reproduce the problem and (I guess) I've found the reason.
- The first session start --> always perfect.
- Starting 7 sessions with Alt+B --> always perfect

The problem is related to Cisco-routers running IOS-XR.
When I start a single session is afterwards a message-box with the text "The server refused to start a shell." displayed.
(this is nerving, but seems to be XR-related)

If I don't klick "OK" then the next session will not start until I clicked "OK".

This wasn't the case in the Version 7.

Regards,
Robert