Aces High Bulletin Board

General Forums => Aces High General Discussion => Topic started by: Mitsu on December 03, 1999, 04:46:00 PM

Title: New T1 Server is BAD for ME!
Post by: Mitsu on December 03, 1999, 04:46:00 PM
the following result is trace route to Arena from My ISP.

-----
TraceRoute 216.91.192.19 (216.91.192.19)
 1     54     54 210.130.2.9     nas.iij4u.or.jp
 2     54      0 210.130.5.195
 3     63      9 202.232.0.81    Osaka-bb2.IIJ.Net
 4     64      1 202.232.3.116   Osaka-ibb0.IIJ.Net
 5    242    178 202.232.0.226   NewYork-bb0.IIJ.Net
 6    239     -3 202.232.0.254   Pennsauken.IIJ.Net
 7    255     16 192.157.69.9    sl-nap1-pen-F0/0/0.sprintlink.net
 8    243    -12 144.232.5.61    sl-bb13-pen-2-3.sprintlink.net
 9    257     14 144.232.5.233   sl-bb12-pen-10-0.sprintlink.net
10    286     29 144.232.9.238   timed out
11      *      * timed out
12    292      6 144.232.11.66   timed out
13    296      4 144.228.137.6   timed out
14    301      5 216.90.2.66     applink-1.DllsTX.savvis.net
15    322     21 216.91.192.19   timed out
16    318     -4 216.91.192.19   beta.hitechcreations.com
host reached

PING 216.91.192.19 (216.91.192.19): 50 data bytes
50 bytes from 216.91.192.19: icmp_seq=0 time=326 ms
50 bytes from 216.91.192.19: icmp_seq=1 time=303 ms
50 bytes from 216.91.192.19: icmp_seq=2 time=329 ms
timed out
50 bytes from 216.91.192.19: icmp_seq=4 time=305 ms
50 bytes from 216.91.192.19: icmp_seq=5 time=302 ms
50 bytes from 216.91.192.19: icmp_seq=6 time=301 ms
50 bytes from 216.91.192.19: icmp_seq=7 time=313 ms
50 bytes from 216.91.192.19: icmp_seq=8 time=317 ms
timed out
 
PING Statistics for 216.91.192.19
10 packets transmitted, 8 packets received, 20% packet loss
round-trip (ms) min/avg/max = 301/312/329
-----

Yeah...this result is very bad.
actually, I can't fly Aces High pleasantly.  (http://bbs.hitechcreations.com/smf/Smileys/default/frown.gif)
there is lags, warps, and chat lags...
and I need 5-30 seconds for one time chatting!  (http://bbs.hitechcreations.com/smf/Smileys/default/frown.gif)

btw I think this cause is sprintlink.net, so I want to know this ISP.
anyone knows about "sprintlink.net"?

Cheers

-Mitsu

note: My English is baby talk - sorry
Title: New T1 Server is BAD for ME!
Post by: Glasses on December 03, 1999, 05:33:00 PM
Same here Mitsu my ISP routes me thru Sprint and messes up my connection to AH anyone got an idea on how to over come the sprint route
Title: New T1 Server is BAD for ME!
Post by: Minotaur on December 03, 1999, 09:08:00 PM
Mitsu;

I think I noticed something in your tracert.

You need to move your base station 7,000 miles to the east.  (http://bbs.hitechcreations.com/smf/Smileys/default/smile.gif)

Actually your ping times compare favorably to mine.  I am west coast USA.

<S>  Good luck!    (http://bbs.hitechcreations.com/smf/Smileys/default/smile.gif)

Mino

[This message has been edited by Minotaur (edited 12-03-1999).]
Title: New T1 Server is BAD for ME!
Post by: Mitsu on December 03, 1999, 11:46:00 PM
Hi Minotaur <S>

here is *NOW* result:

TraceRoute 216.91.192.19 (216.91.192.19)
58 bytes from 216.91.192.19: time=295 ms
 1     55     55 210.130.2.9     nas.iij4u.or.jp
 2     56      1 210.130.5.195
 3     63      7 202.232.0.81    Osaka-bb2.IIJ.Net
 4     63      0 202.232.3.97    Osaka-ibb0.IIJ.Net
 5    239    176 202.232.0.226   NewYork-bb0.IIJ.Net
 6    243      4 216.98.96.246   pennsauken.iij.net
 7    250      7 192.157.69.9    sl-nap1-pen-F0/0/0.sprintlink.net
 8    248     -2 144.232.5.61    sl-bb13-pen-2-3.sprintlink.net
 9    256      8 144.232.5.233   sl-bb12-pen-10-0.sprintlink.net
10    280     24 144.232.9.238   sl-bb11-fw-5-2.sprintlink.net
11    277     -3 144.232.11.166  sl-bb13-fw-8-0.sprintlink.net
12    276     -1 144.232.11.62   sl-gw13-fw-0-0-0.sprintlink.net
13    277      1 144.228.137.6   sl-dnetfw-1-0-T3.sprintlink.net
14    288     11 216.90.2.66     applink-1.DllsTX.savvis.net
15    299     11 216.91.192.19   beta.hitechcreations.com

PING 216.91.192.19 (216.91.192.19): 50 data bytes
50 bytes from 216.91.192.19: icmp_seq=0 time=290 ms
50 bytes from 216.91.192.19: icmp_seq=1 time=293 ms
50 bytes from 216.91.192.19: icmp_seq=2 time=284 ms
50 bytes from 216.91.192.19: icmp_seq=3 time=286 ms
50 bytes from 216.91.192.19: icmp_seq=4 time=285 ms
50 bytes from 216.91.192.19: icmp_seq=5 time=286 ms
50 bytes from 216.91.192.19: icmp_seq=6 time=287 ms
50 bytes from 216.91.192.19: icmp_seq=7 time=289 ms
50 bytes from 216.91.192.19: icmp_seq=8 time=286 ms
50 bytes from 216.91.192.19: icmp_seq=9 time=286 ms
 
PING Statistics for 216.91.192.19
10 packets transmitted, 10 packets received, 0% packet loss
round-trip (ms) min/avg/max = 284/287/293
-----

WOW...very very nice.  (http://bbs.hitechcreations.com/smf/Smileys/default/wink.gif)
however, this result is "ONLY NOW".(14:41 JST - GMT+09:00)

this result will be going to bad result AGAIN at MIDNIGHT.  (http://bbs.hitechcreations.com/smf/Smileys/default/frown.gif)

hmmm, OK - I endure it.
I'll change ISP to CABLE in early January.  (http://bbs.hitechcreations.com/smf/Smileys/default/smile.gif)

Thank you.
Title: New T1 Server is BAD for ME!
Post by: Thorns on December 04, 1999, 02:06:00 AM
Mitsu, The last ISP I had used sprint connections and lines.........I had to switch
ISP's cause my data loss was very bad(almost 10-13)and I live in Chicago suburbs.  I use Ameritech now and I have no data loss. :-)
Title: New T1 Server is BAD for ME!
Post by: TT on December 04, 1999, 02:21:00 AM
 I read a thing on cnet that said to get a local isp that it worked better than a national. To test this I got freewwweb. Not only did it work for the game but it is better than both my pay ISPs just serfing (http://bbs.hitechcreations.com/smf/Smileys/default/smile.gif).

 The article also said to call up your ISP and ask them to route you around problem hops. I hope this last part is some help to you mit.