We are making soap call. The request namespace is 
"https://adwords.google.com/api/adwords/mcm/v201402.

Below are some of the traceroute.

tracert 74.125.25.138

 

Tracing route to pa-in-f138.1e100.net [74.125.25.138]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  10.28.76.3

  2     1 ms    <1 ms    <1 ms  port-channel33-569.ch1-x7x-1b.ntwk.msn.net 
[207.46.202.3]

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

10     *        *        *     Request timed out.

11     *        *        *     Request timed out.

12     *        *        *     Request timed out.

13     *        *        *     Request timed out.

14     *

 

 tracert 74.125.28.113

 

Tracing route to pc-in-f113.1e100.net [74.125.28.113]

over a maximum of 30 hops:

 

  1    <1 ms    <1 ms    <1 ms  10.28.76.3

  2    <1 ms    <1 ms    <1 ms  port-channel33-569.ch1-x7x-1b.ntwk.msn.net 
[207.46.202.3]

  3     *        *        *     Request timed out.

  4     *        *        *     Request timed out.

  5     *        *        *     Request timed out.

  6     *        *        *     Request timed out.

  7     *        *        *     Request timed out.

  8     *        *        *     Request timed out.

  9     *        *        *     Request timed out.

10     *        *        *     Request timed out.

 

portqry /n 74.125.25.138 /e 443

 

Querying target system called:

 

74.125.25.138

 

Attempting to resolve IP address to a name...

 

 

IP address resolved to pa-in-f138.1e100.net

 

 

TCP port 443 (https service): LISTENING

 

 

TCP port 443 (https service): LISTENING

portqry /n 74.125.28.113 /e 443

 

Querying target system called:

 

74.125.28.113

 

Attempting to resolve IP address to a name...

 

 

IP address resolved to pc-in-f113.1e100.net

 

 

TCP port 443 (https service): LISTENING


On Tuesday, July 8, 2014 1:23:35 PM UTC-7, Ray Tsang (AdWords API Team) 
wrote:
>
> Ashley,
>
> A follow up question - could I trouble you to confirm the DNS name that 
> it's trying to reach, and a traceroute to that particular IP address from 
> your server?
>
> Thanks,
>
> Ray
>
> On Tuesday, July 8, 2014 3:47:57 PM UTC-4, Ray Tsang (AdWords API Team) 
> wrote:
>>
>> Thanks - we'll look into this.
>>
>> Cheers,
>>
>> Ray
>>
>> On Tuesday, July 8, 2014 3:03:35 PM UTC-4, Ashley Xu wrote:
>>>
>>> Hi Ray,
>>>
>>> Yes, it's persistent. It starts happening around 2 or 3 weeks ago and 
>>> the frequency has been increasing. From our monitor, more than 10 % of our 
>>> daily requests have failed due to this.
>>>
>>> It either failed at getting access token for oauth or getting a list of 
>>> accounts or campaigns from adwords.
>>>
>>> However it's not happening continuously. Like if I manually retry, it 
>>> will succeed. 
>>>
>>> Please let me know what could be the cause and what can I do to mitigate.
>>>
>>> Thank you!
>>> Ashley
>>>
>>> On Tuesday, July 8, 2014 11:41:34 AM UTC-7, Ray Tsang (AdWords API Team) 
>>> wrote:
>>>
>>>> Ashley,
>>>>
>>>> Please let me know if the issue is persistent - and the frequency of 
>>>> the intermittent failure. Thanks!
>>>>
>>>> Ray
>>>>
>>>> On Tuesday, July 8, 2014 1:04:24 PM UTC-4, Ashley Xu wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>>
>>>>> We are currently using  AdWordsApiClient for oauth and calling AdWords 
>>>>> API.
>>>>>
>>>>> However just recently, we start seeing frequent failures of Unable to 
>>>>> connect to the remote server.
>>>>>
>>>>> Sync error: WebExceptionOther ---> System.Net.WebException: Unable to 
>>>>> connect to the remote server ---> System.Net.Sockets.SocketException: A 
>>>>> connection attempt failed because the connected party did not properly 
>>>>> respond after a period of time, or established connection failed because 
>>>>> connected host has failed to respond 74.125.25.138:443
>>>>>
>>>>>  
>>>>> Does anyone know what is going on? Why it starts failing 
>>>>> intermittently now?
>>>>>  
>>>>> Thanks!
>>>>>
>>>>

-- 
-- 
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~
Also find us on our blog and Google+:
https://googleadsdeveloper.blogspot.com/
https://plus.google.com/+GoogleAdsDevelopers/posts
=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~=~

You received this message because you are subscribed to the Google
Groups "AdWords API Forum" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/adwords-api?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"AdWords API Forum" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to