|
Yes, if your server is working, it should show up in netstat as being in 'Listen' state on port 7000. I've done many socket programs, so if you're stuck, post your code and I'll try to help. On Mon, 9 Jul 2001, Chuck Morehead wrote: > In trying to learn more about sockets I started playing with an example > News/400 had published. This utilized a service program SCKTPROC that could > be bound to a module to give socket functionality to your program. I > thought I understood the article and the concepts behind it. However, when > I tried out the examples, with minor tweaking for my system (e.g. the IP > address for the client example had to be changed to match my AS/400), the > client fails to connect. I have confirmed that the server job is running, > and in fact, appears to be working correctly according to the call stack. > However, when I do NETSTAT and check connections, I do not see anything on > port 7000 (the port I've assigned the server). If a program is really > listening on the port for a connection, shouldn't it show up here? > > Chuck Morehead > +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.