|
Jim Langston wrote: > > My only guess... You're trying to read the socket before the host has sent > any, or the host is still establishing the connection. > > To test this, put a delay of like 5 seconds after you establish connection > before you read. This is just to test if this is what is happening, not the > final solution (I would hope, but sometimes it is). Thanks. I'll try that. I should have thought of it myself; I need more sleep. I've also been advised that there's a small but definite possibility that port 992 isn't the secure telnet port at all, but is in fact something else; fortunately, the client can talk to other ports. (Although I don't remember ever finding a way to reassign port numbers for the OS/400 Telnet server.) -- James H. H. Lampert Professional Dilettante http://www.hb.quik.com/jamesl http://members.hostedscripts.com/antispam.html http://www.thehungersite.com Read My Lips: No More Atrocities!
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.