Only some socket connections fail
Consider the following reasons that only some socket connections would fail:
-
If sites can be accessed by IP address but not by name, then your server's DNS is probably broken (for example, if http://131.107.93.65/ works but http://webtool.rte.microsoft.com/ does not).
Error messages in this case would be "unable to resolve hostname".
See How to force or override DNS lookups for possible workarounds.
-
If remote sites like http://www.yahoo.com/ can be accessed, but your local site cannot be accessed, then the problem is most likely a complex network configuration.
See How to force or override DNS lookups for possible workarounds.
-
If local sites can be accessed, but remote sites cannot, then the problem is most likely the network configuration or firewall. In these cases there is little you can do about the problem other than the extreme suggestions give at All socket connections fail.
-
If the socket connections fail intermittently with "network operation timed out", consider extending the network timeout. Control this setting by going to "Admin Page" => "General Settings" => "Network Timeout".
-
The web site that you wish to visit may be temporarily offline. Or the network between that web site and your web server (hosting the FDSE crawler) may be down. This can happen even if you are able to visit the site from your local computer.
Error messages in these cases may be "no route to host" or "connection timed out".
In these cases it is best to try to the socket connection later.
-
The web site may not exist yet. When new domains or subdomains are created, it can take a few days for their names to propagate. Different hosts will learn about the sites at different times. Your web server which hosts FDSE may not know about the site even if your local computer does.
Error messages in this case would be "unable to resolve hostname".
"Only some socket connections fail"
http://www.xav.com/scripts/search/help/1153.html