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

RE: Cant ping address from 400 to use Httpapi example18 and example19.

From: "Craig Jacobsen" <CJacobsen@xxxxxxxxxxxxx>
To: "HTTPAPI and FTPAPI Projects" <ftpapi@xxxxxxxxxxxxxxxxxxxxxx>
Subject: RE: Cant ping address from 400 to use Httpapi example18 and example19.
Date: Thu, 9 Apr 2009 11:38:59 -0400

Try using TRACEROUTE RMTSYS('209.162.186.60') and then look in your
joblog to see where it is stopping. 


-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of Kavanagh,
Darrell - Bognor
Sent: Thursday, April 09, 2009 10:53 AM
To: HTTPAPI and FTPAPI Projects
Subject: RE: Cant ping address from 400 to use Httpapi example18 and
example19.

Is this the same result as pinging the URL (www.webservicex.net)? I just
tried from our iSeries, and it seems that this site does not like the
default ping packet size of 256 bytes used by the iSeries. I reduced the
packet size to 8 bytes and it responded.

Assuming you have the same issue, I would think that the next step is to
post the results of your httpapi call.

Darrell Kavanagh
UK IT
+44(0)1243 843389/+44(0)1243 770417
mobile +44(0)7780 696039
home +44(0)23 92 297524 


-----Original Message-----
From: ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx
[mailto:ftpapi-bounces@xxxxxxxxxxxxxxxxxxxxxx] On Behalf Of John Rusling
Sent: 09 April 2009 15:30
To: HTTPAPI and FTPAPI Projects
Subject: RE: Cant ping address from 400 to use Httpapi example18 and
example19.

Thanks for replying,

I tried it: PING '209.162.186.60'.

I got -

> PING '209.162.186.60'                                                 
  Verifying connection to host system 209.162.186.60.                   
  No response from host within 1 seconds for connection verification 1. 
  No response from host within 1 seconds for connection verification 2. 
  No response from host within 1 seconds for connection verification 3. 
  No response from host within 1 seconds for connection verification 4. 
  No response from host within 1 seconds for connection verification 5. 
  Connection verification statistics: 0 of 5 successful (0 %).

John


>Try pinging 209.162.186.60 from your 400. If successful you have a DNS
issue
>on the 400

>Go CFGTC option #12, and give the 400 the ip address of a DNS server.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------
------------------------------------------------------------------------
------------------------------------
This email (and any attachment) is confidential, may be legally
privileged and is intended solely for the use of the individual or
entity to whom it is addressed. If you are not the intended recipient
please do not disclose, copy or take any action in reliance on it. If
you have received this message in error please tell us by reply and
delete all copies on your system.
 
Although this email has been scanned for viruses you should rely on your
own virus check as the sender accepts no liability for any damage
arising out of any bug or virus infection. Please note that email
traffic data may be monitored and that emails may be viewed for security
reasons.

John Wiley & Sons Limited is a private limited company registered in
England with registered number 641132.

Registered office address: The Atrium, Southern Gate, Chichester, West
Sussex, PO19 8SQ.
------------------------------------------------------------------------
------------------------------------
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

Confidentiality Notice: This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message.  Unless expressly stated in this e-mail, nothing in this message or any attachment should be construed as a digital or electronic signature.
-----------------------------------------------------------------------
This is the FTPAPI mailing list.  To unsubscribe, please go to:
http://www.scottklement.com/mailman/listinfo/ftpapi
-----------------------------------------------------------------------

References:
- Problem with http_url_encoder_addvar or me?
  - From: Derik Blocker
- Re: Problem with http_url_encoder_addvar or me?
  - From: Scott Klement
- RE: Cant ping address from 400 to use Httpapi example18 and example19.
  - From: Elbert Cook
- RE: Cant ping address from 400 to use Httpapi example18 and example19.
  - From: John Rusling
- RE: Cant ping address from 400 to use Httpapi example18 and example19.
  - From: Kavanagh, Darrell - Bognor

Prev by Date: RE: Cant ping address from 400 to use Httpapi example18 and example19.
Next by Date: RE: Cant ping address from 400 to use Httpapi example18 and example19.
Previous by thread: RE: HTTPAPI returns a "Host name look up failed"
Next by thread: RE: Cant ping address from 400 to use Httpapi example18 and example19.
Index(es):
- Date
- Thread