3ecommunications.net

Home > Return Code > Eza1735i Std Return Code = 10234, Error Code = 00010

Eza1735i Std Return Code = 10234, Error Code = 00010

Contents

If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). Follow-Ups: RE: FTP Secure (TLS/SSL) to BMC Support - TLS handshake failed From: Gray, Larry - Larry A References: RE: FTP Secure (TLS/SSL) to BMC Support - TLS handshake failed From: If you have received it in error, please notify the sender immediately and delete the original and any copy or printout. If you have received it in error, please notify the sender immediately and delete the original and any copy or printout. have a peek here

On the server? Unintended recipients are prohibited from making any other use of this e-mail. I downloaded it to the mainframe. This will give you debugging onthat level. directory

Eza1735i Std Return Code = 10234, Error Code = 00010

But, a search for ftp auth tls error codes lead > me to this IBM manual... SC0473 initConnection: entered SC0549 initConnection: Calling getaddrinfo() with partner- ftpssl.farecast.com SC0588 initConnection: getaddrinfo() returned. If you have erroneously received this communication, please notify the sender immediately by phone (704-758-1000) or by e-mail and destroy all copies of this message (electronic, paper, or otherwise). That would create a GSK trace.Then use the gsktrace command to format the .trc file.//FTPIT EXEC PGM=FTP, // PARM=('ENVAR("GSK_TRACE=0XFFFF","GSK_TRACE_FILE=/tmp/gskadp.trc")',// '/-r TLS (TRACE EXIT') Larry GrayLarge Systems EngineeringLowe's Companies Inc.336-658-7944-----Original Message-----From: IBM

Then I loaded it to RACF; RACDCERT CERTAUTH ADD('C602621.BINGCERT.B64') WITHLABEL('GTE CyberTrust Global Root') TRUST Then created a ring for my ID C602621 and connecting the Certificate: RACDCERT ID(C602621) ADDRING(MYBINGRING) RACDCERT ID(C602621) The output from gsktrace confirms that the CA isthe problem. I did find a GTE CyberTrust certificate as you suggested on my web browser. Fc1003 Authserver Secure_socket_init Failed With Rc 410 sounds like the > problem could be in the SYSFTPD DD statements... > Is something misconfigured?

If you have received it in error, please notify the sender immediately and delete the original and any copy or printout. Much > better :-) > > 17 means the same as above, 10 means "OPEN"... On the client? https://groups.google.com/d/topic/bit.listserv.ibm-main/_DoG1F6AeGs Larry GrayLarge Systems EngineeringLowe's Companies Inc.336-658-7944-----Original Message-----From: IBM Mainframe Discussion List [mailto:IBM-***@ibm-main.lstBehalf Of Steven WerthSent: Wednesday, March 21, 2007 2:42 PMTo: IBM-***@BAMA.UA.EDUSubject: Re: FTP Secure (TLS/SSL) to BMC Support - TLS

Although we have taken reasonable precautions to ensure no viruses are present in this e-mail, we accept no liability for any loss or damage arising from the use of this e-mail Although we have taken reasonable precautions to ensure no viruses are present in this e-mail, we accept no liability for any loss or damage arising from the use of this e-mail We are going to ask you 2 easy questions writing them in a way a robot wouldn't be able to see. Unintended recipients are prohibited from making any other use of this e-mail.

Std Return Code = 10220, Error Code = 00017

Here are the messageswe get:220 BMC FTP Server Ready EZA1701I >>> AUTH TLS 234 AUTH TLS successful EZA2897I Authentication negotiation failed EZA2898I Unable to successfully negotiate required authentication EZA1735I Std Return Thank you.Add "DEBUG SEC" to the SYSFTPD parms. Eza1735i Std Return Code = 10234, Error Code = 00010 I'd get > Authentication successful, and the transfer would continue with no > problems. > > > > Anyway, tracking down the root cause of the failure will probably > help. Secure_socket_init Failed With Rc = 420 I will tell you what the error is with the TLS handshake.

I'masking the list simply because BMC support has been extremely slow inresponding back to us (3+ days) and I thought I would see if anyonemight be able to point us in http://3ecommunications.net/return-code/program-ended-with-error-or-warning-return-code-4-scc1.html Communications Server IP User's Guide and > Commands > > which listed the error codes... > 17 FTP_AUTHENTICATION Security authentication or negotiation > failure, incorrect specification of security keywords. > > Any suggestion and comment are great appreciated! cipherspecs = FC0326 ftpAuth: environment_open () FC0444 ftpAuth: environment_init () FC0453 ftpAuth: environment initialization complete EZA1701I >>> AUTH TLS 234 Proceed with negotiation. Secure_socket_init Failed With Rc = 410 \

Is the > certificate bad? (Same cert is acceptable to a web browser for https > connections, though I do have to click past a warning when using IE) > > If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. Unintended recipients are prohibited from making any other use of this e-mail. Check This Out uga !

If you are not the sender's intended recipient, you are not authorized to intercept, read, print, retain, copy, forward, or disseminate this message. This will give you debugging on> that level. SC0759 initNamedConnection: entered SC0918 initIPv4Connection: entered CY3177 access_via_socks_server: entered EZA1554I Connecting to: partner-ftpssl.farecast.com 72.5.52.165 port: 21. 220 (vsFTPd 2.2.1) GU4887 ftpSetApplData: entered FC0238 ftpAuth: security values: mech=TLS, tlsmech=FTP, sFTP=R, sCC=C, sDC=C

If you are using a dynamic IP, the kind of IP that changes every time you re-start your router, maybe the only problem is that today you are using an IP

Is there any limition for the HSM CDS managed via RLS? Although we have taken reasonable precautions to ensure no viruses are present in this e-mail, we accept no liability for any loss or damage arising from the use of this e-mail FC0904 authServer: secure_socket_open () FC0971 authServer: secure_socket_init () FC0984 authServer: secure_socket_init failed with rc = 410 (SSL message format incorrect) FC1339 endSecureConn: entered EZA2897I Authentication negotiation failed FC1371 endSecureEnv: entered CZ0609 The request cannot be fulfilled by the server

We're just getting impatient with BMCsupport.Steve Werth> Add "DEBUG SEC" to the SYSFTPD parms. I think you need to > break this into mmnnn, where mm is a command code and nnn is the FTP > client reply code. Will continue to wait on BMC to straighten this out.Steve Werth Email Firewall made the following annotations------------------------------------------------------------------------ NOTICE ---This message is for the designated recipient only and may contain confidential, privileged this contact form Anyway, to test whether your computer is infected, and to remove any possible infection, we would recomend you to contact as soon as possible a computer technician and ask them to

Verifed with BING the start and end date and serial number ending with 1A5 with the one I found and that it match theirs.