RE: Outgoing Port

["Bob P. Roche" <BRoche@xxxxxxxxxxxxxxxxx>]

   Does your local PC have any proxy settings setup on it? That may
   account for being able to access from the PC and not the iSeries? Just
   an idea,

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

   07/13/2007 02:26 PM

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

                                                                       To

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

                                                                       cc

                                                                  Subject

   RE: Outgoing Port

   Yeah,  I cannot get a response with an IP address or a
   www.whatever.com.   I
   can ping any system on their VPN from the iSeries, and there are a lot
   of
   other iSeries on the VPN in other cities even, but nothing that is not
   on
   the VPN.
   If I am on a workstation (PC) inside the VPN, I can browse to any web
   page,
   ftp to any site in the world, etc.., but I cannot get to anything from
   an
   iSeries session on the same VPN as that workstation.
   -----Original Message-----
   From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Mike Krebs
   Sent: Friday, July 13, 2007 11:10 AM
   To: 'HTTPAPI and FTPAPI Projects'
   Subject: RE: Outgoing Port
   Shannon,
   You know these things almost always are firewall configuration
   problems. I'd
   start with the basics...
   PING and TRACEROUTE from the iSeries. Start with names and try IP if
   names
   don't work. If they resolve correctly and get out (and back), then
   half the
   battle is done. If you don't resolve the name but IP works, problem
   with DNS
   on the iSeries (CHGTCPDMN). We changed out name servers a while back
   and
   forgot to fix the iSeries. It caused problems for certain functions.
   The other question to ask of the IT folks is if they use a transparent
   proxy. That would put a kind of a firewall between the iSeries and the
   world. So, port 80 isn't "blocked", but everything gets routed, NATed,
   etc
   through the proxy.
   Finally, you can get to a website using telnet. TELNET
   RMTSYS(YAHOO.COM)
   PORT(80)  This will do the same thing as the programs basically, but
   you
   could try it from your workstation and from the iSeries and compare
   notes on
   responses.
   Good luck.
   Mike Krebs
   -----Original Message-----
   From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
   [mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Shannon
   ODonnell
   Sent: Friday, July 13, 2007 9:43 AM
   To: 'HTTPAPI and FTPAPI Projects'
   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
   ----------------------------------------------------------------------
   -
   ----------------------------------------------------------------------
   -
   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
-----------------------------------------------------------------------