yusri 0 Report post Posted April 21, 2005 Did you taking too much time to access your favorite sites?Probably the problem is on the server used by those sites. To make sure that is the problem, use Windows PING facility.Ping is a small program, which sends a 32-bit signal to the Web site server. Next, Ping record the time needed by the server to answer it.To activate Ping:Click on the Start-Run menus, type command, and then click OK. Type PING "site name" in the MS-DOS prompt window, for example PING http://yahoo.com/.In a moment, the result will appear on the screen. A result less than 300ms is normal speed while a result more than 400ms is slow speed. If "Request timed out" message appears on the screen that means the Web site server is not responding in one second. Probably it happens because the server is too slow, or designed on purpose not to respond to the ping test, or you forgot to specify your name server addresses in the TCP/IP settings dialog box. Share this post Link to post Share on other sites
R0boT39 0 Report post Posted April 21, 2005 It takes me and average of 80ms to connect to Xisto, but when i am browsing it takes a lot longer...why is that? Share this post Link to post Share on other sites
CrashCore 0 Report post Posted April 22, 2005 I'm not a newbie to more advanced tools and utilities, but I found an odd problem. I am using Firefox 1.0.3 (latest version as of this post) and I have a 384kb/s cable internet connection: loads the average page within a second. The Xisto server responds to my ping in an average of 70 seconds, but it seems to load extremely slowly like traffic-heavy sites that can't handle it respond. Xisto has loaded slowly since the day I came here. It's not that bad, but it does get quite annoying sometimes. So, what is going on with Xisto? Share this post Link to post Share on other sites
Hamtaro 0 Report post Posted April 22, 2005 I don't know what the problem is. It doesn't seem to load slow to me, and I'm on dial-up. Anyway, I pinged a few random sites, and I got a pretty slow speed. I forgot how long it took. It was in the thousands...If only I didn't have dial-up... Share this post Link to post Share on other sites
googlue 0 Report post Posted April 22, 2005 My site, http://forums.xisto.com/no_longer_exists/ takes 773 ms! google.com takes only 143 ms!That's a huge difference, IMHO!CAn something be done to improve the response time by the server at the cpanel or by homepage coding? Share this post Link to post Share on other sites
no9t9 0 Report post Posted April 22, 2005 Let's clear one thing up. Ping time is NOT server response time! When you ping a server, it measures the time it takes to get to the server, the time it takes the server to respond, and the time it takes to get a message back. The route is by far the longest time in the process (unless Xisto servers are severely overloaded). The route is basically "hops" through the internet (servers). Each hop takes time, the more hops it takes to get to Xisto, the higher the ping time. To improve your ping time, you either physically move closer to the server or get all the hops between you and the server to upgrade their routers. Share this post Link to post Share on other sites
Adamrosso 0 Report post Posted August 8, 2005 It only takes me 50ms to get to T17 =D Share this post Link to post Share on other sites
bluhapp 0 Report post Posted September 9, 2005 T17 got me 296ms to reach..by the way... my brother doesnt use ping (site) at the run boxhe uses ping (site) -t whats the difference? Share this post Link to post Share on other sites
Dynomite 0 Report post Posted September 9, 2005 It took me .35 milliseconds for Xisto to respond.This is very good, Xisto always loads very quickly for me, as does my site, maybe I just have a good connection, but I had always thought I had a very slow connection.Also isn't pinging a site alot not good for servers? Share this post Link to post Share on other sites
mike_savoie 0 Report post Posted September 9, 2005 To expand a little on the ping tool. Think of ping like sonar, it was actually named after the ping sonar makes, but I digress. Your ping time is the amount of time your request takes to make a round trip to the server. Meaning, your packets leave your computer, travel across the net, hit the server, the server responds by sending packets back. Ping will not determine a slow server. Ping determines connection speed to the server. Speed is determined by the slowest connection in the loop, referred to as a 'bottleneck', the bottle neck could be caused by too many things to list here. Just think of it as the slowest part between you and the server. Slow loading sites could be caused by quite a few factors as well. That is material for another thread. by the way... my brother doesnt use ping (site) at the run box he uses ping (site) -t whats the difference? -t is an option with ping To answer this question, if at the command prompt you type ping /help you will notice a slew of options as well as the correct syntax for using the ping command. Here is a list of options, what they do and how to use them. Options -w timeout Timeout in milliseconds to wait for each reply. -i TTL Time To Live. -a Resolve addresses to hostnames. -n count Number of echo requests to send. -t Ping the destination host until interrupted. -l size Send buffer size. -f Set Don't Fragment flag in packet. -v TOS Type Of Service. -r count Record route for count hops. -s count Timestamp for count hops. -j host_list Loose source route along host_list. -k host_list Strict source route along host_list. destination_host The name of the remote host ( server ) I'll use https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl as the destination host. ping https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will simply ping google with 4 packets and return the results. ping -t https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will send infinite pings to google until you hit ctrl+c or close the window. ping -w 5000 https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will tell ping to wait up to 5000 miliseconds before timing out ping -i 12 https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will kill the packet in 12 miliseconds if it doesn't complete the ping ping -n 12 https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will send 12 pings to google ping -l 64 https://www.google.de/?gfe_rd=cr&ei=BwkjVKfAD8uH8QfckIGgCQ&gws_rd=ssl, will send packets with 64 bytes of data The options in red are ones I haven't experimented with. To find out what they do simply add a dash then the option to find out for yourself. Hope this clears up ping. Now try traceroute https://www.google.comnow/ that's a neat little tool. Share this post Link to post Share on other sites
jopak134 0 Report post Posted March 6, 2008 pinging a website can also help you check if your internet connection is good. example is your connected but cannot go to sites, this will help you recognize a problem Share this post Link to post Share on other sites