No connection could be made because the target machine actively refused it 74.125.227.18:80

[Ec...@coastalfcu.org]

It looks like this IP address belongs to google.

We migrated our primary domain to a new vendor last night. Although
we have not changed the domain name, recpatcha is not working and
instead users get the message in the subject line on a successful
submit. I generated new public and private keys, but it did not help
the problem.

I was wondering if this could be a DNS propagation issue? Perhaps
googles california servers havent got the DNS updates yet?

[Dom Sekotill]

It's likely your new vendor has a firewall that's blocking access to Google's
servers.

I'd suggest you contact them to find out and discuss your options.

Dom

[Ec...@coastalfcu.org]

Ive been assured that isn't the case.

The reCaptcha tool draws correctly, and we are using the apsx control
for it. You can click the help icon for it and regenerate the words,
but on successful submission we still get the error.

[Dom Sekotill]

On Wednesday 01 February 2012 15:03:47 Ec...@Coastalfcu.org wrote:
> The reCaptcha tool draws correctly, and we are using the apsx control
> for it. You can click the help icon for it and regenerate the words,
> but on successful submission we still get the error.

Tool drawing and regeneration is client side and won't be affected by firewalls
on your server.

I'm not familiar with the ASPX plugin but that error looks similar to the PHP
"could not open socket" error. The two most common causes of that error are
firewalls that block outbound HTTP ports at the server and app
servers/frameworks that have been configured not to allow outbound connections.

If you have access to the server can you open http://74.125.227.18/ in a
browser or run "telnet 74.125.227.18 80" in a terminal? If so, does it
connect?

Dom