#1
|
|||
|
|||
SecureCRT login issue
I'm using SecureCRT Version 7.3.6 (x64 build 963) on a Windows 7 Enterprise machine. Invariably, I will start up the program and can click on a link in the Session Manager which immediately brings up the log in window. I can sometimes even open up another connection with the same result. However, it us usually the third attempt to open a connection that gives me a very long delay before the log in window appears. In fact, on the top of the page it will even say "Not responding" until the window pops up. I would really like to remove this hesitation before the window appears. Any help would be greatly appreciated.
|
#2
|
|||
|
|||
Hi MHorton,
Thanks for the post. We will need to get more data about this situation. Is this a completely new installation of SecureCRT on this machine? Is your configuration folder stored locally or remotely? Is your Windows 7 machine physical or virtual? How many sessions and folders do you have in the Session Manager? |
#3
|
|||
|
|||
This is an update to a previous version. I've been using SecureCRT for quite some time and have updated it multiple times.
The configuration folder is stored locally on a physical machine. I have over 50 folders w/subfolders that I use to group my devices by location. There are probably better than 200 device address in total. Hope this helps. |
#4
|
|||
|
|||
Hi MHorton,
Thanks for the information. What version of SecureCRT were you using prior to the update? Did you start to see the slowness just after upgrading? Did anything else in the environment change at the time you started to see the slowness? |
#5
|
|||
|
|||
I was using the release just before this one, 7.3.5. I did not have any issues with it or any prior versions.
|
#6
|
|||
|
|||
Hi MHorton,
Could you clarify the behavior you have noticed as far as pattern? Is it *always* the third session you connect where you see delay? Or is the delay in a specific session to a particular server *anytime* you connect that session? Quote:
By "window pops up", do you mean until you are prompted for authentication? (I assume these are SSH2 sessions.) Until the tab is finally connected? Something else?
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
#7
|
|||
|
|||
Hi MHorton,
We should probably get trace options output if you find it's a particular session (or sessions) that are non-responsive. It's often useful to see trace options output which provides debugging information that may help us better understand the problem that you're experiencing. To enable trace options output:
NOTICE: The requested troubleshooting data may include sensitive information (usernames, passwords, publicly-accessible host names or IP addresses, etc.).If you don't believe it's related to a particular session, there is other information to be collected. We will provide instructions for that when we receive your email.
__________________
Thanks, --Brenda VanDyke Software Technical Support support@vandyke.com (505) 332-5730 |
![]() |
Tags |
log in delay |
Thread Tools | |
Display Modes | |
|
|