|
It also shows that the two machines are on the same subnet, or at least that routing between them is working.
That's true, but I often get messages from people saying "I know that my network is correct, because ping works." Unfortunately, that's not true... There are misconfigurations where ping will work, but TCP sessions won't. Ping is a good starting point, but just because it's working doesn't mean that all is well with your network.
I often talk to people who are learning how to use the sockets API to write their own TCP/IP software in RPG, and the same principle applies here. If you want to know whether your errors stem from mistakes in your code vs. a network setup problem, you should first try a ping. If that succeeds, try using TELNET. If TELNET works (or, at least connects) and your program doesn't, the errors in the RPG code somewhere.
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.