Jump to content

Siryak

Members
  • Posts

    667
  • Joined

  • Last visited

  • Speed Test

    My Results

Posts posted by Siryak

  1. i beleive this is now a hostage situation.

    WATER YOU NEED TO LET CA3LE OUT OF YOUR CLOSET SO HE CAN GET SOME FRESH AIR!!!!!  :2funny::uglystupid2:

    Ok here is the plan. You stand outside her window and flex. While she is laughing at you uncontrollably I will sneak in and make the extraction. Then if she tries to make a chase we will get Shug to threaten her with his mad skills, making her again laugh uncontrollably and we make a clean get away. The plan is fool proof. :2funny:

  2. Value pack for download is 7.5, Select Pack 11 or 12 gigs...Pro Pack 17 Gigs. Do you not know how to check your FAP meter? If you signed up with Wildblue directly then go to wildblue.net and click on admintool I believe is what it's called. If you signed up at a coop then type in admintool.coopname.net

  3. [glow=red,2,300] :biggun::txt-wtf:[/glow]

    Exactly....Being a person that computers is my hobby it is down right torturous lol.

    Being a person that likes to do online gaming it is just cruel to have latency like this:

    Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

    Reply from 216.109.112.135: bytes=32 time=1004ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1376ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1193ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1214ms TTL=46

    Ping statistics for 216.109.112.135:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 1004ms, Maximum = 1376ms, Average = 1196ms

  4. Lol here are some more:

    Error 008: Interference detected. Remove aluminum foil and remote control devices.

    Error 8P: Unclear on whether your search is about money or monkeys. Please try again.

    Error: Insufficient conviction. Please clap hands 3 times, while chanting "I believe" and try again.

    Error 001: Weak or no signal detected. Upgrade transmitter and retry.(Lol this one was my favourite)

    Error 666: Multiple transmitters detected. Silence voices in your head and try again.

    Error: MentalPlex has determined that this is not your final answer. Please try again.

    Error 144: That information was lost with the Martian Lander. Please try again.

  5. Here is my tracert...Sizzling!!! lol.....Or maybe I am just the one sizzling... :lol:

    Tracing route to google.com [64.233.187.99]

    over a maximum of 30 hops:

      1    1 ms    1 ms    <1 ms  192.168.1.1

      2  1193 ms  1641 ms  1198 ms  10.10.0.1

      3  1163 ms  1604 ms  1067 ms  10.245.20.1

      4    *    1975 ms  1239 ms  10.245.30.27

      5  1455 ms  1100 ms  2719 ms  10.245.30.1

      6  1518 ms  1115 ms  708 ms  10.245.100.2

      7  1127 ms  707 ms  1406 ms  10.245.110.2

      8  1250 ms  1098 ms  1269 ms  12.124.219.17

      9  1992 ms  1260 ms  2540 ms  gbr1-p70.auttx.ip.att.net [12.123.133.162]

    10  1839 ms  1220 ms  2927 ms  tbr2-p012301.dlstx.ip.att.net [12.122.10.109]

    11  1295 ms  1410 ms  1276 ms  ggr3-ge90.dlstx.ip.att.net [12.123.16.197]

    12  1531 ms  1240 ms  1465 ms  br2-a340s4.dlstx.ip.att.net [192.205.33.142]

    13  1206 ms  1816 ms  1310 ms  40.icore1.DTX-Dallas.teleglobe.net [66.198.1.10]

    14  1705 ms  1584 ms  1190 ms  3.icore1.A56-Atlanta.teleglobe.net [209.58.47.2]

    15  1196 ms  3204 ms  1721 ms  if-5-0-0.har1.A56-Atlanta.teleglobe.net [64.86.9

    .13]

    16  1167 ms  1180 ms  1187 ms  ix-2-0.har1.A56-Atlanta.teleglobe.net [64.86.9.6

    ]

    17  1721 ms  1392 ms  1266 ms  64.233.174.84

    18  1207 ms    *    1569 ms  72.14.236.173

    19  1445 ms  1730 ms  1195 ms  216.239.49.222

    20  1589 ms  1274 ms  1336 ms  jc-in-f99.google.com [64.233.187.99]

    Trace complete.

  6. If you think about it ping times with satletite are going to be high no matter what. I mean everything is going to space.

    Not this high...The signal going through space only accounts for about 500ms of the latency. The rest is in their gateways.

    Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

    Reply from 216.109.112.135: bytes=32 time=2045ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1210ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1893ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1250ms TTL=46

    Ping statistics for 216.109.112.135:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 1210ms, Maximum = 2045ms, Average = 1599ms

  7. The reason there aren't any positive comments about Wildblue, is because there isn't really anything positive to say. Have you looked into "Sprint" EVDO? Have you checked for WISPs in your area? As it stands right now I would say Hughesnet is putting out the better product as far as satellite internet goes. Wildblue is still having major growing pains that Hughesnet has already been through and put behind them. I would not recommend EDGE. It is a horrible technology and your dial-up will literally outperform it.

    Here is the latency you can expect from Wildblue. It doesn't get any better than this either.

    Pinging yahoo.com [216.109.112.135] with 32 bytes of data:

    Reply from 216.109.112.135: bytes=32 time=2989ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1300ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1212ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1208ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1215ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1237ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1191ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1351ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1256ms TTL=46

    Reply from 216.109.112.135: bytes=32 time=1554ms TTL=46

    Ping statistics for 216.109.112.135:

        Packets: Sent = 10, Received = 10, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 1191ms, Maximum = 2989ms, Average = 1451ms

  8. C:Documents and SettingsTim>ping google.com

    Pinging google.com [64.233.167.99] with 32 bytes of data:

    Reply from 64.233.167.99: bytes=32 time=6ms TTL=247

    Reply from 64.233.167.99: bytes=32 time=5ms TTL=247

    Reply from 64.233.167.99: bytes=32 time=5ms TTL=247

    Reply from 64.233.167.99: bytes=32 time=5ms TTL=247

    Ping statistics for 64.233.167.99:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 5ms, Maximum = 6ms, Average = 5ms

    C:Documents and SettingsTim>tracert google.com

    Tracing route to google.com [64.233.167.99]

    over a maximum of 30 hops:

      1    4 ms    5 ms    6 ms  74-132-30-1.dhcp.insightbb.com [74.132.30.1]

      2    6 ms    5 ms    6 ms  74-132-0-189.dhcp.insightbb.com [74.132.0.189]

      3    7 ms    6 ms    7 ms  74.128.8.205

      4    6 ms    5 ms      *    so-7-1.car2.Chicago1.Level3.net [4.71.182.25]

      5    4 ms    5 ms    4 ms  4.79.66.30

      6    5 ms    6 ms    5 ms  72.14.232.57

      7    5 ms    15 ms  6 ms  72.14.232.70

      8    6 ms    7 ms    4 ms  py-in-f99.google.com [64.233.167.99]

    Trace complete.

    What did you do, break into the Google warehouse and plug directly into their server?!?!?!?!

  9. Nos your latency is absolutely outstanding!!! You make me want to throw something at you!!! lol

    Bet you can't top this!!! I know it's probably hard to believe how somebody could get such great ping times. :buck2:

    Pinging google.com [64.233.167.99] with 32 bytes of data:

    Reply from 64.233.167.99: bytes=32 time=1481ms TTL=237

    Reply from 64.233.167.99: bytes=32 time=1342ms TTL=237

    Reply from 64.233.167.99: bytes=32 time=1159ms TTL=237

    Reply from 64.233.167.99: bytes=32 time=1879ms TTL=237

    Ping statistics for 64.233.167.99:

        Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

    Approximate round trip times in milli-seconds:

        Minimum = 1159ms, Maximum = 1879ms, Average = 1465ms

  10. It is true. The pings on the new satellite which doesn't have hardly anybody on it is averaging in the 1100-1200ms range. This is just ridiculous. This IS NOT normal satellite latency. In fact the Hughesnet system which is supposed to have worse latency actually cuts Wildblue's latency in half. So it CAN be done.

×
×
  • Create New...