×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Arthur.Marino wrote:
I'm
curious though why, Client Access, which has to be aware of her Windows
credentials (Bypass SignOn), wouldn't be configured to pass those to QNTC
rather than her AS/400 (whoops) creds. Oh well, as long as it works now.
AFAIK, there is essentially no relationship between Client Access
and /QNTC.
Client Access is for the PC communicating with 'host servers' (plus
some telnet5250, ODBC type stuff and maybe one or two others) that
run on your "AS/400".
/QNTC is for your "AS/400" to communicate with Windows servers
through a Windows networking scheme.
Opposite directions from different platforms to different servers
using different password schemes. (Note that EIM/kerberos is one
part of bringing these schemes together.)
Client Access doesn't exactly use Windows credentials to 'Bypass
signon' for terminal access; it uses whatever credentials were
supplied for the signon to the server. If your Windows and "AS/400"
profile and password match, you can use them for both. It's
irrelevant for 'bypass signon' whether you use the same
profile/password or not.
If you have configured the connection to use your Windows
profile/password to signon to the server and it matches your
"AS/400" profile/password and you configure 'bypass signon', then in
effect your Windows credentials are used. But you can 'bypass
signon' even with a profile/password that's different from Windows.
To confuse matters more, /QNTC can be accessed by "AS/400" programs
even if Client Access isn't installed anywhere. This marks a clear
separation between /QNTC and any part of Client Access.
(And EIM/kerberos can go a bit beyond that by helping make the
"AS/400" password irrelevant.)
Note that 'Bypass Signon' is commonly understood to refer the
feature of the terminal emulator that allows a terminal session to
start without presenting a signon panel.
The feature of Client Access that allows connections to be made to
host servers without prompting, through use of the supplied Windows
profile/password, can be used in conjunction with 'Bypass Signon'.
Or a green-screen signon can still be requested. The two features --
no prompting and 'Bypass Signon' -- are separate. 'Bypass Signon'
can even work when telneting between two "AS/400s" with no PC or
Windows involved.
Tom Liotta
midrange.com
