Reply to Re: Server problems?
If you don't have an account, just leave the password field blank.
It's probably a routing problem. That is, your request - and the data returned - goes through usually at least 10 computers before reaching the server you want, and back. If one server is down somewhere, the routers will try to find a different path to the server you want. If an alternative route can't be found (quickly enough) - BAM - server error. Your request, or the returned data, is dropped.
This is why connecting to certain websites sometimes takes very long - or even craps out on you. Refreshing sometimes helps because an alternative route COULD be found at that point (or a server that was too busy before is now available).
It also matters what ISP you use - the internet consists of "zones" of ISPs sorta, and some of them block out each other, meaning it becomes more difficult for your ISP to be able to contact certain websites because they can't use that ISP's servers/routers.
I said a lot here, but my point is: the server obviously isn't offline as some people have constant access to it (including me) (and unless it IS offline for bits during the times we don't visit, coincidentally). Otherwise, it's a routing problem.
This is why connecting to certain websites sometimes takes very long - or even craps out on you. Refreshing sometimes helps because an alternative route COULD be found at that point (or a server that was too busy before is now available).
It also matters what ISP you use - the internet consists of "zones" of ISPs sorta, and some of them block out each other, meaning it becomes more difficult for your ISP to be able to contact certain websites because they can't use that ISP's servers/routers.
I said a lot here, but my point is: the server obviously isn't offline as some people have constant access to it (including me) (and unless it IS offline for bits during the times we don't visit, coincidentally). Otherwise, it's a routing problem.
