anybody else experiencing much difficulties accessing the site?
March 29 2012 at 9:27 AM
(Login Robbe1675) VRF Member from IP address 22.214.171.124
Lately the website is very hard to access, sometimes I have to refresh at least 5 times for it to open.
Reading a complete posted thread is becoming a pain, when you need to refresh and hit the back button repeatedly for every line....
Is it my internet provider (I have witnessed it on several computers, so it is not the computer itself), or is it Network 54?
Hate to see the site getting influenced because of bad accessibility...
I am visiting the site already less often because of this.
Anybody else having the same problems?
I get the same errors from other N54 forums i visit. At times every third click results in an error page which is very frustrating. I have no idea how many concurrent users N54 have but the setup gives a very aged impression so maybe some renovation of both backend and frontend would be in order.
You can use Windows tracert applet to locate the bottleneck
March 29 2012, 10:16 PM
Open a command-prompt window (click Start->Run and enter "cmd" (w/o quotes). This will open a command-prompt window on your desktop.
Then, enter "tracert vintagerolexforum.com" (w/o quotes) and click the ENTER key on your keyboard to start the applet.
If all's well, each line should contain three sets of times (in ms) and the IP of each "hop" between you and the server running VRF.
An entry with asterisks (*) or which says "Request timed out" means a dropped/lost connection and these are the cause of your connection problems. The first entry at the top of the tracert list is your PC and the last entry is VRF's server. If the time-out is the last entry, that means VRF is down or inaccessible. If the time-out is somewhere in the middle, it means that one (or more) of the intervening servers is down or inaccessible. If the first entry at the top is timing-out, that means the problem's at your end. If you're able to perform a search on google when this happens, then the problem's probably at your ISP's end and you may need to check with them.
I hope this helps.