RE: Outgoing Port

[Brian Eckenrod <beckenrod@xxxxxxxxxxxxxxx>]

   Check to be sure their i5 is properly set up for DNS resolution.  You
   can confirm this by trying to ping the same hosts that Scott uses in
   the example programs.  If it can not resolve the IP on the ping, then
   they do not have the i5 using any DNS which would prevent any outbound
   connections from it.

   "Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
   Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx

   07/13/2007 10:42 AM

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

                                                                       To

   "'HTTPAPI and FTPAPI Projects'" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>

                                                                       cc

                                                                  Subject

   RE: Outgoing Port

   Thanks for the info Scott. I thought it would have to be PORT 80 for
   outbound requests, but I wanted to make sure.
   The IT folks here tell me that they do not have that port blocked
   coming
   from their network, and yet I still cannot get out using any of the
   example
   programs from LIBHTTP.
   I have played with your programs on other systems in the past and I
   know
   they work fine, so now I just have to try to figure out why I cannot
   get to
   the outside world from here.
   If you have any other suggestions on what I might ask their IT people
   or
   other things I could look at (maybe it's a DNS issue?), that would be
   great.
   I do not consider myself a networking guru at all so I kind of
   flounder on
   these types of problems.
   Thanks,
   Shannon O'Donnell
   -----Original Message-----
   From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Scott
   Klement
   Sent: Wednesday, July 11, 2007 4:00 PM
   To: HTTPAPI and FTPAPI Projects
   Subject: Re: Outgoing Port
   Yes, port 80 for plain text, and 443 for SSL, in accordance with the
   HTTP
   standard.
   (SOAP uses HTTP for it's networking.  SOAP itself is just the format
   of the
   data that's sent...)
   sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx wrote:
   >
   > Does your HTTPAPI use Port 80, by default, for outgoing SOAP
   > requests?   Reason I ask is because I was trying some of the
   examples
   > at a client and nothing was getting out. So then I started trying to
   > just ping some URLs and I cannot get out from the AS/400 because of
   > the client firewall on their network. I can have them open any port
   I
   > need for outbound, I just need to identify which ones it is.
   >
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -
   ----------------------------------------------------------------------
   -
   This is the FTPAPI mailing list.  To unsubscribe, please go to:
   http://www.scottklement.com/mailman/listinfo/ftpapi
   ----------------------------------------------------------------------
   -
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------