[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
RE: Outgoing Port
It does not need to be an outside DNS server. They may have their own
internal one that serves up their local DNS resolution as well as
reaches out to the internet servers to get internet addresses. Or,
they could use an outside server for their only DNS.
You are correct though about the menu option. It is under CFGTCP
option 12 and is labeled "Domain Name Server:"
For our i5, we have our own internal DNS server as the first entry.
That server is configured to hand out IPs of all of our local (LAN)
equipment. Our local server is also linked to the servers of our
provider to handle external addresses as well. We do also have
secondary DNS servers set up on our i5 though in the event our main
DNS server was down. Those secondary servers are just the servers of
our provider and would only be good for resolving external addresses,
but most of what we'd need to reolve would be external anyway so they
act as a good backup in the event that our main DNS server on our LAN
is down.
In short, yes, they need DNS set up in CFGTCP, option 12.
"Shannon ODonnell" <sodonnell@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx>
Sent by: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
07/13/2007 12:07 PM
Please respond to
HTTPAPI and FTPAPI Projects <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
To
"'HTTPAPI and FTPAPI Projects'" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
cc
Subject
RE: Outgoing Port
Thanks Brian.
Are you saying that the iseries needs to point to an outside DNS
Server IP
address? (from option 12 on the CFGTCP menu)
-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Brian
Eckenrod
Sent: Friday, July 13, 2007 10:26 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Outgoing Port
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
----------------------------------------------------------------------
-
----------------------------------------------------------------------
-
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
-----------------------------------------------------------------------