It's not the computers problem directly. It would fall on one of three things.
- The database is slow as snot and needs to be run accross multiple spindles to service the volume of requests. Work has been done to improve speed but, unless it's on more spindles the seek time will suffer and can cause timeouts. (This may be going on).
- Someones link is having issues. Be it provider or hosting side.
- DNS is having issues looking up some of the external or internally linked content. I am curious as to how the load balancing and fail-over is setup. If it's replicated to another server and request distribution is handled through round robin dns resolution, that can be a problem on machines running vista, xp sp3 and most other unix OSes.
- The database is slow as snot and needs to be run accross multiple spindles to service the volume of requests. Work has been done to improve speed but, unless it's on more spindles the seek time will suffer and can cause timeouts. (This may be going on).
- Someones link is having issues. Be it provider or hosting side.
- DNS is having issues looking up some of the external or internally linked content. I am curious as to how the load balancing and fail-over is setup. If it's replicated to another server and request distribution is handled through round robin dns resolution, that can be a problem on machines running vista, xp sp3 and most other unix OSes.