Hop 14 should be your final hop to the recaptcha.net server, right after
ge-2-0-0.r1.nyc.swishmail.com. If you are getting behavior that isn't
always consistent with the traceroute you produced here can you show
those or describe where the variation is? The fact that you are seeing
similar behavior here and on a Comcast connection would indicate there
is some kind of routing issue on their end, but I can't re-create it on
any of the IP ranges from my building. Or you have a common
mis-configuration between your home system and this server like the TTL
being set very very low?
-----Original Message-----
From: MSU Network Administrators Group [mailto:[log in to unmask]] On
Behalf Of Gene Willacker
Sent: Friday, August 29, 2008 12:50 PM
To: [log in to unmask]
Subject: Re: reCAPTCHA
The name resolves OK. Here is a traceroute below. The first group of
hops pops up quickly. Sometimes it gets through 17 or 18 hops before it
times out. I get similar results from a machine I have at home on
Comcast.
The script on our server posts a few fields to the recaptcha.net server
via http and gets a response code back. Fairly simple stuff. Nothing
that a firewall is blocking.
Gene
[root@hfs root]# traceroute api-verify.recaptcha.net
traceroute to api-verify.recaptcha.net (69.12.97.166), 30 hops max, 38
byte packets
1 foodstores-rtr-ve2.net.msu.edu (35.8.78.1) 0.370 ms 0.334 ms
0.390 ms
2 powerplant-rtr-ge18.net.msu.edu (35.9.103.22) 0.501 ms 0.417 ms
0.393 ms
3 com2-rtr-ge22.net.msu.edu (35.9.103.6) 2.281 ms 0.292 ms 0.267 ms
4 cc2-rtr-ge14.net.msu.edu (35.9.101.5) 0.459 ms 0.315 ms 0.319 ms
5 cc-t1-ge-1-41.net.msu.edu (35.9.101.198) 5.844 ms 8.884 ms 13.458
ms
6 cc-t1-ge1-3.net.msu.edu (35.9.101.210) 6.444 ms 9.452 ms 9.031 ms
7 xe-0-1-0x257.msu6.mich.net (192.122.183.225) 31.957 ms 2.093 ms
1.340 ms
8 xe-0-1-0x14.eq-chi2.mich.net (198.108.22.9) 7.128 ms 7.343 ms
7.592 ms
9 xe-0.equinix.chcgil09.us.bb.gin.ntt.net (206.223.119.12) 8.189 ms
8.234 ms 7.959 ms
10 p64-0-0-0.r21.nycmny01.us.bb.gin.ntt.net (129.250.5.5) 51.674 ms
35.443 ms 36.530 ms
MPLS Label=245280 CoS=0 TTL=1 S=1
11 p16-3-0-0.r01.nycmny03.us.bb.gin.ntt.net (129.250.3.85) 35.645 ms
36.259 ms 35.260 ms
12 po-2.r02.nycmny03.us.bb.gin.ntt.net (129.250.5.102) 35.171 ms
36.849 ms 35.876 ms
13 trca (129.250.192.86) 33.702 ms 80.592
ms 34.416 ms
14 * * *
15 * * *
16 * * *
17 * * *
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *
[root@hfs root]#
on 8/29/2008 12:30 PM Graff, Dave said the following:
> Where is the traceroute failing? Name resolution for
> api-verify.recaptcha.net works correctly off MSU's dns servers and a
> traceroute from where I am sitting completes without issue. Are you
> running any kind firewall or IDP equipment on your network assuming
the
> name resolves and the first hop fails?
>
> -----Original Message-----
> From: MSU Network Administrators Group [mailto:[log in to unmask]] On
> Behalf Of Gene Willacker
> Sent: Friday, August 29, 2008 12:04 PM
> To: [log in to unmask]
> Subject: reCAPTCHA
>
> Is anyone out there using reCAPTCHA to validate web forms? We are
> testing it and seeing 20 to 45 second delays to validate the input
from
> their servers. We don't see this slow response from other sites on the
> Internet that use reCAPTCHA. Traceroute from our app server to their
> servers (api-verify.recaptcha.net) does not succeed. The support
people
> at reCAPTCHA have no problem tracerouting to us.
>
> We are using reCAPTCHA on PHP pages. Any suggestions are welcome.
>
> Thanks, Gene
>
