Disable the "X" in CRT?

[DennisT]

Is there a way to disable the "X" (close window) in CRT? My users are causing problems with a legacy application when they don't log out via the application interface.

[mekanik]

What about using the option: "Show confirm disconnect dialog" under "Global Options > General"

This will display a pop-up box advising "Do you wish to disconnect from [session name]?". If the user clicks on Yes, then SecureCRT should send a TCP packet with the FIN flag set to the host on which the session is trying to be closed on, thus closing the TCP socket correctly instead of leaving it hung (since it sounds like your legacy app doesn't support TCP keepalives). If the user clicks on No, then the session will resume as normal. [If memory serves me]

/mekanik/

[DennisT]

Actually the application is dumber than that. If the session is cut off the application still thinks someone is in the various files which causes problems with other users. It isn't that the host OS is leaving the session hung, it is the application. The "confirm disconnect" would help somewhat but not eliminate this problem.

Disabling the "X" would stop it for everything except Windows log off/reboots.

[mekanik]

Originally Posted by DennisT

Actually the application is dumber than that. If the session is cut off the application still thinks someone is in the various files which causes problems with other users. It isn't that the host OS is leaving the session hung, it is the application. The "confirm disconnect" would help somewhat but not eliminate this problem.

Disabling the "X" would stop it for everything except Windows log off/reboots.

So are you saying that the application will not close the socket even when a TCP packet with the FIN flag set is sent? If that is the case, then you have a pretty poorly written application on your hands (sounds like you know that already though). The application should acknowledge the TCP/FIN packet and release the socket (again, you know this already).

I do not know your environment, but what about "task manager", TASKKILL and all the other options there are to terminate an application. Disabling the "X" is not the true solution, I would say an enforced policy would be more of a solution, but then you have to ensure that the political parties that be back you up on the enforcement. Still, "confirm disconnect" assists in this situation pretty well IMHO.

/mekanik/

[DennisT]

The application is a character based Unix app (ERP system). All TCP activity is handled by the OS (telnetd). The problem we have is that users close the CRT session via the "X" and not by exiting the app. When they click on the "X" CRT closes the session and Unix/telnetd kills the application. Unfortunately this leaves the app in a state where it still thinks files are in use (archaic design). This causes problems for other users later on.

[jdev]

Originally Posted by DennisT

Is there a way to disable the "X" (close window) in CRT? My users are causing problems with a legacy application when they don't log out via the application interface.

There is a configuration that can be used to prevent users from closing the CRT/SecureCRT window via the 'X' button.

For more information on how to accomplish this task, please submit your request to our technical support department.

--Jake

[DennisT]

Jake,
Yes, that is exactly what I was looking for. Thanks

[mekanik]

Nice, thanks for the info Jake.

/mekanik/