May 03 2011, 10:32 PM
Due to some people experiencing the issue and others not, it sounds to me like the possibility of a problem with one of the routers along the route to the server. For those experiencing this issue, can you run a trace route to the particular server and either paste the results or identify the last several routers in the trace? This would help in tracking down the issue.
A trace route can be performed by using the command "tracert [ip here]"
A trace route can be performed by using the command "tracert [ip here]"