Hey Adam, Thanks for the reply. Here is my DF command: df Filesystem 1K-blocks Used Available Use% Mounted on
/dev/dasda1 139368 127316 12052 92% / tmpfs 63040 0 63040 0% /dev/shm /dev/dasdb1 656 32 592 6% /opt/vmssl/parms Is 92 % ok? How should I clean up the log files? As far as PROFILE TCPIP errors, I did notice yesterday I had misspelled the PORT 9999 statement for my SSLSERV admin : 9999 TCP SSLSERV SERCUR ALCERT ; SSL SERVER - ADMINISTRATION so I corrected with obeyfile : 9999 TCP SSLSERV SECURE ALCERT ; SSL SERVER - ADMINISTRATION If this is the problem, I do not understand why it would have worked before the IPL. And, if this was the issue, shouldn't the corrected obeyfile have resolved this, or will I need to wait until I can cycle the TCPIP stack this weekend? Thanks, Tim ________________________________ From: The IBM z/VM Operating System [mailto:[EMAIL PROTECTED] On Behalf Of Adam Thornton Sent: Wednesday, August 06, 2008 9:55 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: SSL connection problem after IPL On Aug 6, 2008, at 7:37 AM, Tim Joyce wrote: Hey guys, I've been using secure telnet through a SSLSERV for many months now. After we IPLed over the weekend, it stopped working. The SSLSERV machine is up a communicating with SSLADMIN commands. The certificate looks correct. NETSTAT CO shows the SSLSERV in a listen status. But, if I try to start up a secure telnet session, I get : SSLv2 handshake failure: Socket error 1: SSL_ERROR_SSL. Can anyone point me in the right direction? Log into the console of the SSLSERV machine. Run "df" and see if maybe your log files have filled up the whole disk. Also check your PROFILE TCPIP and make sure that you really are wrapping the ports you think you're wrapping. Adam
