Windows: When the sessions were tiled, if the main window was resized, some of the tiled windows did not send a screen resize to the remote system.Windows: On a system that had two monitors with the primary monitor having a larger display resolution than the secondary monitor, when SecureCRT was maximized on the primary monitor and then restored, it used the resolution of the secondary monitor.Windows: If a laptop was docked such that a secondary monitor was used and then SecureCRT was moved to that monitor and closed, when the laptop was disconnected from the dock and SecureCRT was restarted, it was visible in the task bar, but not on the laptop display.If a session reconnected automatically in the background when a different session's tab had focus, the title bar was updated to display the reconnected session name.If a session's emulation was set to "Dumb", it continued to used dumb emulation after being changed to use a different emulation.If the protocol type was changed during authentication, SecureCRT crashed.Linux: Character encodings that cannot be used by SecureCRT are no longer shown in Terminal/Appearance category in the Session Options dialog.Mac: The look of text on Retina displays was improved.Mac: If a session prompted for a log file, after the file location was selected, focus did not return to the SecureCRT window.Mac: If the global option "Host key database location" was changed to a different path, the new path was not saved.Mac: The session option "Use ALT as meta key" was not always honored.Windows: If the global option "Minimize to Activator in system tray" was set and SecureCRT was closed, if "Connect" was selected from the Activator menu, the icons in the Connect dialog were not mapped to the correct actions.Windows: When switching between tiled and tabbed sessions in a maximized window, the terminal area was 24x80 instead of the full window area.SSH1/SSH2: If a session used a dynamic tunnel on port 10080 and another SSH1/SSH2 session went through the first session's SOCKS proxy and used a dynamic tunnel on port 1080, SecureCRT crashed when data went through the second tunnel.Serial: The stop bits were not logged correctly in the trace output.When enough tabs were open to require the scroll control on the tab bar, if the right-most tab was activated and renamed, the tab bar shifted to the left and the active tab was no longer visible.If a session that contained ANSI color text in the scrollback was disconnected and reconnected, the ANSI color attributes were no longer in the scrollback.If "/Serial" or "/Tapi" (Windows only) was specified on the command line, it was not honored.If the "Automate logon" items for a session were re-ordered, the changes were not saved.Opening the default session in a script caused SecureCRT to crash.In the Connect dialog, if a folder was renamed to a string that ended in one or more "." characters, the sessions in the folder were deleted.Once you are successfully connected, you can use the Select All and Copy options from within the Edit menu to transfer the information to the Windows clipboard, and then paste this information into a text editor and save the data as a file. With Trace Options enabled, you will notice debugging information displayed in the terminal window that isn't normally there by default when SecureCRT is attempting to establish a connection, and at certain times throughout the lifetime of the connection. If you click the File pull down menu again you should see a check mark next to Trace Options, indicating that trace options output is now enabled. ![]() ![]() ![]() To enable trace options output, click on the File pull down menu and select Trace Options. Would you manually connect to the device, capture trace options output and send it to me at with a subject of Attn Todd - Forum thread 10861? Code: "/SSH2 /L " & user & " /PASSWORD " & passwd & " /C 3DES /M MD5 /AcceptHostKeys " & ip
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |