Windows terminals

FileKit & 3270 Terminal Emulation Software Most users today rarely connect to IBM Mainframe systems using actual hardware 3270 terminals but do so using emulated 3270 terminals running on a PC workstation. Many of these 3270 terminal emulation products contain features and functionality that exceed that of a standard hardware 3270 terminal and keyboard. This allows tailoring of the look and feel of the individual's IBM Mainframe environment. FileKit provides the user with a windowing environment within a 3270 session (i.e. supports multiple window display, window repositioning, resizing, maximising, etc.) As such, CBL has identified certain features offered by 3270 emulator packages that facilitate use of the FileKit environment. The following table identifies commercially available 3270 emulation software products that have been tested at CBL and their ability to support those features pertinent to usage of FileKit. It does not, however, reflect the vast range of other facilities available in each product. Large Screen Sizes TN3270 terminals, served by the host TELNET server, may reference VTAM LOGMODEs that support non-standard screen sizes (i.e. indicate that a read partition query is to be issued by a host application to determine the capabilities of the device.) Standard screen size LOGMODEs are often referred to as Model 2/3/4/5 terminals and correspond to actual hardware 3270 terminals. Comprehensive 3270 emulator support of IBM-DYNAMIC TN3270 terminals will allow the user to specify the desired 3270 screen size (rows x columns) e.g. 40 x 132, 62 x 160 (maximum supported by ISPF), 86 x 190, etc. Starting FileKit in a 3270 terminal of larger than standard dimensions allows the user to view more windows concurrently and to display more information within each window. Note that, when using terminals with large dimensions, it may be necessary to reduce the font size and/or increase the resolution of the

INFORMATION:I have a situation where I am forced to use a server (Windows 2012 R2) that is NOT part of a domain, and does NOT have AD. This is not my choice, is not optimal, but out of my control. I also have local users that connect to this server through RDP, and the local users have a password expiration policy.Since AD/Exchange is not part of the picture, the users receive no notification that their passwords are about to expire. PROBLEM:The problem is when a user's password has expired and they try to login using a Remote Desktop Connection. It does not allow them to change their password. I have unchecked the "Allow connections ONLY from computers running Remote Desktop with Network Level Authentication" from the server side, so the server is NOT requiring NLA from incoming RDP sessions.However, when using Windows Remote Desktop Connection Manager, it seems to be forcing NLA.If I am using the "Terminals" Remote Desktop Client, there is an option on the client side, to disable using "Network Level Authentication". If I disable NLA through the Terminals client, and I connect to the server, it allows me to change the users expired password.QUESTION:I am making the assumption, perhaps incorrectly, that the Terminals program is just sitting on top of Windows Remote Desktop Connection protocols, and that if you can disable Network Level Authentication client side through the Terminals program, then you should also be able to disable this through Windows built-in Remote Desktop Connection Manager. Unfortunately, I do not see this option in the connection managers GUI, and I do not see any parameters in ".RDP" files specific to NLA.If I click "About" on the client side Remote Desktop Connection Manager, it tells me that "Network Level Authentication supported". The wording leads me to believe that using it is optional, but again, I see no way to turn it off in the connection manager. BTW, this particular connection manager is v10.

Provided by: gnome-terminal_3.44.0-1ubuntu1_amd64 NAME gnome-terminal - A terminal emulator for GNOMESYNOPSIS gnome-terminal [OPTION...] [-- PROGRAM [ARG...]]DESCRIPTION gnome-terminal is a terminal emulator application for accessing a UNIX shell environment which can be used to run programs available on your system. It supports several profiles, multiple tabs and implements several keyboard shortcuts.OPTIONS --help, -h Show a brief overview of all the options. --help-all Show all the options in detail. --help-gtk Show all the GTK options. --help-terminal Show all the options to select between new terminal tabs or windows. --help-terminal-options Show all the options to change the attributes of terminals regardless of whether they are in separate tabs or windows. --help-window-options Show all the options to change the attributes of windows containing terminals. --load-config=FILE Restore the application to a previously saved state by loading it from a configuration file. --preferences Show the preferences window. --print-environment, -p Print the environment variables to interact with newly created terminals. --quiet, -q Suppress diagnostics. --verbose, -v Increase diagnostic verbosity. --tab Open a new tab containing a terminal in the last-opened window with the default profile. --window Open a new window with a tab containing a terminal with the default profile. --command, -e=COMMAND Split the argument to this option into a program and arguments in the same way a shell would, and execute the resulting command-line inside the terminal. This option is deprecated. Instead, use -- to terminate the options, and put the program and arguments to execute after it: for example, instead of gnome-terminal -e "python3 -q", prefer to use gnome-terminal -- python3 -q. Note that the COMMAND is not run via a shell: it is split into words and executed as a program. If shell syntax is required, use the form gnome-terminal -- sh -c '...'. --execute PROGRAM [ARGS], -x PROGRAM [ARGS] Stop parsing options at this point, and interpret all subsequent options as a program and arguments to execute inside the terminal. This option is deprecated: use -- instead. For example, instead of gnome-terminal -x python3 -q, prefer to use gnome-terminal -- python3 -q. --fd=FD Forward file descriptor. --profile=PROFILE-NAME Use the given profile instead of