The other test node on the same subnet is not getting those socket timeout errors. We'll look again at the host that's giving them. There is a concrete test we can make using curl.
On May 7, 2010, at 4:46 AM, Marvin Addison wrote: > My money is on a firewall issue. Socket connect timeouts almost > always are caused by the sending host not being able to complete the > TCP handshake, which is a classic symptom of the recipient firewall > dropping the initial SYN. If your firewalls are configured to drop > instead of report a closed port, I think that's evidence for a > firewall problem. I believe Microsoft firewalls do this by default. > > M > > -- > You are currently subscribed to [email protected] as: > [email protected] > To unsubscribe, change settings or access archives, see > http://www.ja-sig.org/wiki/display/JSG/cas-dev -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-dev
