|
On 06/02/2006, at 8:12 AM, Dave Johnson wrote:
It's very peculiar that the connect( is not showing an error condition, when it should.
Add calls to getsockname() and getpeername() after the connect() supposedly completes.
getsockname() will show you the local (i.e., OS/400) IP address and port used by the kernel. Use netstat on OS/400 to see if that port is active.
getpeername() will show you the client IP address and port. Verify they are what you think they should be. Use netstat on the client to see if that port is active.
What release of OS/400 are you on and are you current on PTFs? I found a PTF to fix a timing problem in connect() where connect would return success before it was 100% complete. The implication in the PTF cover letter is that the connexion was successful but not all structures were updated as a result of the connect. However this was fixed back in VRM450.
Regards, Simon Coulter. -------------------------------------------------------------------- FlyByNight Software AS/400 Technical Specialists http://www.flybynight.com.au/ Phone: +61 3 9419 0175 Mobile: +61 0411 091 400 /"\ Fax: +61 3 9419 0175 \ / X ASCII Ribbon campaign against HTML E-Mail / \ --------------------------------------------------------------------
As an Amazon Associate we earn from qualifying purchases.
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.
midrange.com
