× 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.




Thanks Scott, and everyone else who replied.

Just as an update, I've resolved the issue with IBM's help. It turned out to be something I would not have thought of.... We use a password management application called KeePass and this automatically associated all .kdb files on the PC with itself, including the local Client Access key database file. It also messed up the authority to this file and this was causing the IO error I was getting. There was no problem on the Power System side.

So, the solution was to:


1) Remove the .kdb association with KeePass

2) Set the authorities on the key database file correctly

3) Reboot

It worked perfectly after that.

Thanks

Adam Driver
IBM Certified Systems Administrator - System i
Consultant - Infrastructure Technician
Exacta Corporation
608.661.6697 ext 2581
adriver@xxxxxxxxxxxx<mailto:adriver@xxxxxxxxxxxx>
Please consider your environmental responsibility before printing this e-mail.


date: Thu, 10 Nov 2011 17:31:52 -0600

from: Scott Klement <midrange-l@xxxxxxxxxxxxxxxx<mailto:midrange-l@xxxxxxxxxxxxxxxx>>

subject: Re: Telnet SSL question



Hi Adam,



Just to clarify your final statement, is the QIBM_QTV_TELNET_CLIENT

application only for telnet from another system?



No. QIBM_QTV_TELNET_CLIENT is the Telnet *CLIENT*. It's not for telnets from another system... it's for telnets *TO* another system via the TELNET CL command.





In other words, does Client Access use this?



No. Client Access uses the telnet *SERVER*, not the client. Client Access is an example of "telnet from another system". (Whereas the telnet client is for telnetting *to* another system.)





And no, we wouldn't want to secure telnet from another system, the

only traffic using this is from other LPARs on the same system and is

all over the internal VLAN anyway.



As far as I know, LPARs are considered "other systems". Each one looks and feels like a different computer. I understand what you're saying, they're all running on the same physical hardware, you think of them as the same computer.



However, software generally does not. They appear to be completely different computers to most (if not all) software.





------------------------------



[Like us on Facebook!]<http://on.fb.me/t7A5KE>

- WEA Trust Confidentiality Notice -

This electronic mail message and any files transmitted with it are confidential and are intended solely for the use of the individual or entity to whom they are addressed. Dissemination, forwarding, printing, or copying of this electronic mail without the consent of the sender is strictly prohibited. If you are not the intended recipient or the person responsible for delivering the electronic mail to the intended recipient, be advised that you have received this electronic mail in error; please immediately notify the sender by return mail.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.