Re: Ping problems.
Tranc3r, Sun Feb 22 2009, 12:07AM

Google it.

Re: Ping problems.
LadyHellfire*, Sun Feb 22 2009, 12:23PM

First thing to check anytime there are connectivity issues is a simple traceroute. Mac=terminal, "traceroute fsk405.com" ; win=?(forget the name), "tracert fsk405.com"

Usually, if thre is a bad router/hop, it will show. Right now, an FSK member is sitting with issues due to bad router/hop just outside his provider's "care." Thus, his provider is not responsible, and resolution is more difficult to attain.

If a traceroute shows *clean*, then it comes down to your equipment... lots of fun to troubleshoot :D

After a traceroute, post back and the troubleshoot can continue (if necessary).

Re: Ping problems.
ZELLIS, Sun Feb 22 2009, 02:36PM

HERE is what it will look like

C:\Users\shawn>TRACERT FSK405.COM

Tracing route to FSK405.COM [74.53.204.82]
over a maximum of 30 hops:

1 35 ms 1 ms 1 ms xx.xx.xx.xx
2 * * * Request timed out.
3 10 ms 7 ms 9 ms 68.87.208.97
4 8 ms 8 ms 8 ms po-20-ur02.algonquin.il.chicago.comcast.net [68.87.231.73]
5 8 ms 11 ms 8 ms po-10-ur01.algonquin.il.chicago.comcast.net [68.87.230.21]
6 10 ms 8 ms 9 ms be-60-ar01.elmhurst.il.chicago.comcast.net [68.87.230.17]
7 12 ms 12 ms 11 ms be-10-ar01.area4.il.chicago.comcast.net [68.87.229.109]
8 39 ms 37 ms 35 ms pos-0-6-0-0-cr01.chicago.il.ibone.comcast.net [68.86.90.53]
9 38 ms 37 ms 38 ms pos-0-9-0-0-cr01.atlanta.ga.ibone.comcast.net [68.86.85.166]
10 55 ms 51 ms 51 ms pos-1-15-0-0-cr01.dallas.tx.ibone.comcast.net [68.86.85.149]
11 51 ms 51 ms 55 ms theplanet-cr01.dallas.tx.ibone.comcast.net [68.86.88.50]
12 51 ms 51 ms 67 ms te9-1.dsr01.dllstx3.theplanet.com [70.87.253.6]
13 52 ms 53 ms 53 ms 76.fd.5746.static.theplanet.com [70.87.253.118]
14 52 ms 58 ms 51 ms po1.car06.dllstx6.theplanet.com [12.96.160.8]
15 51 ms 51 ms 50 ms 52.cc.354a.static.theplanet.com [74.53.204.82]

Trace complete.
now i dont know what it means... maby some one could tell us why i have 3 sets of times example:

1 35 ms 1 ms 1 ms xx.xx.xx.xx

why , what does the 3 times mean? time in, delay, time out?

thanks.

Re: Ping problems.
LadyHellfire*, Sun Feb 22 2009, 03:02PM

AFAIK, default tracert/traceroute will *throw* X number packets at a point (router) three times, and show the round trip time (or is it one way time?). Each hop is from *you* to router Y; for you Zellis, it is Chicago origin (or close to Chicago), off to Atlanta, then Dallas, then the FSK405 server.

Packet loss happens, but should typically be negligible. By using other utilities and specifying variables (such as number of times to ping, with how many packets, etc), an adequate assessment of routing impact can be obtained.

BTW- #2 with the asterisks? That is your modem I believe, and will always show that. Zellis- why your initial one is 35ms.. don't know, and that is weird. No?

Each hop has a default max time before producing an asterisk. The asterisk (except for #2) means the send/return timed out.. took too long. If it takes THAT long IOW, it is a bad hop. Intermittent connection issues will typically show as a resultant time, asterisk, resultant time.. or something similar. If multiple attempts produce 3 asterisks across a single router point (hop), then it is a dead end (most likely. Else, it may be "clogged," and you will simply have a really, really bad ping, and probably lose alot of packets.

Setting a router, modem, and any computers up properly can be simple, or one can opt for the "art of networking" approach and fine tune and hone things.

Re: Ping problems.
LadyHellfire*, Sun Feb 22 2009, 03:03PM

Mine:

Last login: Thu Feb 19 22:05:56 on ttys000
nikkiks-macbook-pro-15:~ nikkik$ traceroute fsk405.com
traceroute to fsk405.com (74.53.204.82), 64 hops max, 40 byte packets
1 192.168.1.1 (192.168.1.1) 2.032 ms 1.481 ms 1.521 ms
2 * * *
3 ge-5-14-ur02.troutdale.or.bverton.comcast.net (68.85.242.241) 10.532 ms 14.848 ms 36.425 ms
4 te-5-2-ur01.hollywood.or.bverton.comcast.net (68.87.216.73) 24.037 ms 22.818 ms 15.918 ms
5 te-9-3-ar01.beaverton.or.bverton.comcast.net (68.87.216.33) 11.458 ms 12.784 ms 44.664 ms
6 te-0-4-0-1-cr01.portland.or.ibone.comcast.net (68.86.90.245) 38.653 ms 16.171 ms 13.900 ms
7 pos-1-13-0-0-cr01.sacramento.ca.ibone.comcast.net (68.86.85.162) 53.168 ms 58.996 ms 26.245 ms
8 pos-1-14-0-0-cr01.losangeles.ca.ibone.comcast.net (68.86.85.190) 59.187 ms 41.876 ms 38.902 ms
9 pos-0-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.146) 81.899 ms 73.424 ms 77.089 ms
10 theplanet-cr01.dallas.tx.ibone.comcast.net (68.86.88.50) 76.085 ms 72.491 ms 84.109 ms
11 te9-1.dsr01.dllstx3.theplanet.com (70.87.253.6) 79.850 ms te7-1.dsr01.dllstx3.theplanet.com (70.87.253.2) 88.071 ms te9-1.dsr01.dllstx3.theplanet.com (70.87.253.6) 84.651 ms
12 te1-3.dsr02.dllstx2.theplanet.com (70.87.253.122) 82.302 ms 86.919 ms 82.084 ms
13 po2.car06.dllstx6.theplanet.com (12.96.160.40) 98.836 ms 114.380 ms 92.761 ms
14 52.cc.354a.static.theplanet.com (74.53.204.82) 83.735 ms 75.808 ms 116.343 ms

wireless, using macbook pro (non-gaming)

Re: Ping problems.
Boogie Knight, Sun Feb 22 2009, 06:07PM

Since the game servers are in 3 different locations (?) would it be advantageous to tracert to the ip of a particular game server that may be lagging? If you tracert to the fsk405.com server, that's where this forum is, rt? Just, different locations may give different results.

Re: Ping problems.
LadyHellfire*, Sun Feb 22 2009, 10:56PM

FSK405.com is the main ip... the two main servers (pub and jump, sometimes jump is superman beta test, and is "Sunday Scrim" on SUndays) are simply different ports (27960, 27965).

fsk405.com and .org redirect to kickassctf.com, but it isi still the same ip.

Re: Ping problems.
LadyHellfire*, Sun Feb 22 2009, 10:57PM

oh- if ya want, you can launch UrT, drop console, and enter, "connect fsk405.com" and it will hit the pub server. "connect fsk405.com:27965" will get ya on the *private* server (jump, superman beta, sun scrim)

Re: Ping problems.
Mcflurry, Sun Feb 22 2009, 11:25PM

Broadbandreports.com has helped me fix some problems, they list about every isp. They have forums that alot of the technicians troll, which is much more helpful than most "customer support".

Re: Ping problems.
[$E]Heroine., Mon Feb 23 2009, 03:27PM

Wow. I have no idea what any of this means. But thanks anyways.. It's fine now..