[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Error Code



   Hi all,
   Thanks Scott, will be going through all of the points that you have
   listed and hopefully get it working - will keep you posted :)
   Kind regards,
   Prevesh Kuni
   RPG Developer
     _________________________________________________________________

   Atlas Copco ASAP Southern Africa
   P.O. Box 14110
   Witfield
   1467
   South Africa
   Phone: +27 (0)11 821 9000 - Phone dir.: +27 (0)11 821 9245 - Mobile:
   +27 (0)83 679 8197 - Fax: +27 (0)11 821 9523
   E-mail:  [1]prevesh.kuni@xxxxxxxxxxxxxxxxx
   Visit Atlas Copco at: [2]www.atlascopco.com
     _________________________________________________________________

   We are committed to your superior productivity through interaction and
   innovation
   
   Scott Klement <sk@xxxxxxxxxxxxxxxx>
   Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx

   2008/10/08 07:48 PM

                             Please respond to
        HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>

                                                                       To

   HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>

                                                                       cc

                                                                  Subject

   Re: Error Code

   Hello,
   > I'm getting the following error when calling the programs:
   > "connect(): A route to the remote host is not available."
   I guess the obvious question is this:  Is there a route to the remote
   host?
   Type 'CFGTCP' <enter>  choose option #2.  Is there a route that tells
   the TCP/IP support in OS/400 how to get to the host?  Or to another
   router that, in turn, knows how to get to the host?
   Or are you supposed to go through a proxy? (which knows how to get to
   the host..?)
   > Judging by most of the other posts I'm guessing a firewall issue?
   It seems unlikely that your firewall would return a 'no route to host'
   error message to HTTPAPI.  It'd be more likely to either discard the
   connection attempt entirely (in which case HTTPAPI would time out) or
   send back a "connection refused" error.
   Returning "no route" would be a very bizarre and misleading thing for
   a
   firewall to return.
   > Although I do not have the faintest idea of how and where to start
   > looking? Any help would be greatly appreciated - thanks.
   IMHO, the starting point is to know how your network is supposed to
   work.  How is your system supposed to send data to the Internet?  Does
   it send data to a router?  Does it send data to a proxy?
   Once you know the answer to that, then you can ask your self "have I
   configured OS/400 to send data to that router?" or "have I told
   HTTPAPI
   to use that proxy?"
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -

References

   1. mailto:prevesh.kuni@xxxxxxxxxxxxxxxxx
   2. http://www.atlascopco.com/
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------