beberapa list dari no DNS Speedy yang bisa anda pakai:

203.130.196.5
202.134.0.155
202.134.1.10
202.134.0.62
202.158.20.1
202.158.40.1
202.159.32.2
202.159.33.2
202.155.30.227
202.155.0.10
203.130.196.5
203.130.196.155
202.134.2.5
202.134.1.10
202.152.254.246
202.154.1.2
202.152.254.245
202.73.99.8
61.247.0.8
202.138.224.2
4.2.2.1
131.161.247.231
63.226.12.96
207.225.209.66
202.73.99.8
202.158.3.6
202.134.0.62
202.158.20.1
202.158.40.1
202.159.32.2
202.159.33.2
202.155.30.227
202.134.2.5
202.138.224.2
202.155.0.15
202.146.255.5
202.155.0.10
202.155.0.15

Tips memperbaiki jaringan yg suka rto (request time out)

tip ini hanya tuk membantu jaringan yang kadang rto...paling tidak meringank
an..atau sedikit memperbaiki jaringan yang sering putus..
bener ngg teman2...inilah yang paling sering menyusahkan adalah koneksi yang
sering putus....
contoh apabila kita main poker tuh kalau time out biasanya kita langsung sta
ndup padahal pada saat itu kita yang mestinya memenangkan chip....hehehehe
trik ini kelihatannya banyak di google......cuma aku anjurin kalau bisa dili
hat2 trik saya.
PING KE 3 SERVER BESAR YAITU
1. OPEN DNS (208.67.222.222)
2. WWW.GOOGLE.COM

3. WWW,YAHOO.COM
usahakan jgn gunakan ping
esar itu.........
langkah awal
1. masuk menu run ketik :
2. masuk menu run ketik :
3. masuk menu run ketik :

cuma ke salah satu server...pakailah ke 3 server b

---> ping www.google.com -t -l 33
---> ping www.yahoo.com -t -l 33
---> ping 208.67.222.222 -t -l 33

nah apabila koneksi kita tiba2 di ke 3 server itu terbaca request time out
banyak contoh udah lebih dari 10 rto maka secara langsung kamu ngg perlu mat
ikan ping yg tadi
tapi :
langsung aja buat request 1000 bytes
aku anjurin buat request aja dulu ke --> ping www.google.com -t -l 1000
apabila belum respon ya ping lagi ke --> www.yahoo.com -t -l 1000
apabila belum respon lagi ya ping lagi ke --> www.yahoo.com -t -l 1000
ingat : jgn matikan dulu ping 1000 yg lain lakukan aja ping ke server selanj
utnya
ingat : range permintaan requestnya antara 32 - 1000
tapi kalau memang rto nya full usahakan pakai paket 1000
nah kalau udah mulai reply kembali alias di permintaan pingmu udah berjalan
normal ya sisa matikan aja yg ping 1000 nya.
pakai aja yg ping 33.
ke 3 server yg di ping 1000 dimatikan aja jika udah berjalan normal:
berikut contoh :
Pinging www.l.google.com [64.233.181.147] with 33 bytes of data:
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply

from
from
from
from
from
from
from
from
from
from
from
from

64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:

bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33
bytes=33

time=247ms
time=722ms
time=205ms
time=110ms
time=320ms
time=585ms
time=134ms
time=124ms
time=254ms
time=108ms
time=130ms
time=102ms

TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52

Pinging www.l.google.com [64.233.181.147] with 800 bytes of data:

Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply

from
from
from
from
from
from
from
from
from

64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:
64.233.181.147:

bytes=64
bytes=64
bytes=64
bytes=64
bytes=64
bytes=64
bytes=64
bytes=64
bytes=64

(sent
(sent
(sent
(sent
(sent
(sent
(sent
(sent
(sent

800)
800)
800)
800)
800)
800)
800)
800)
800)

time=182ms
time=131ms
time=141ms
time=138ms
time=131ms
time=135ms
time=174ms
time=134ms
time=149ms

TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52
TTL=52

diatas hasil modifikasi nilai ping yg rusak dan pada kondisi sudah tdk ada R

TO nya;
jadi ping bytes 33 tetap jalan tapi gunakan kembali ping besarnya untuk meng
embalikan nilai time ke arah yg semakin kecil.
di ping bytes 33 ada nilai time tertinggi yaitu = 722 ms artinya 7,22 detik
(ms ke detik itu dibagi 100)
pada waktu aku melakukan ping 400 bytes nilai time nya semakin jauh..ahirnya
aku coba ping 800 bytes nilainya mulai stabil kisaran 1,3 - 1,8 dtik nah pada k
ondisi ini kita biarkan dulu sampai pada bytes 33 itu nilai time nya turun sekit
ar 99 ms - 180 ms (0,99 detik-1,8 detik)
jadi jangan pernah menganggap nilai ping besar akan membuat kita lag....
tapi perhatikan aja nilai time yg ada ....buktinya bisa kita lihat di atas
cara untuk menghentikan ping : CTR C
Sumber: Tips memperbaiki jaringan yg suka rto (request time out) - IndoForum htt
p://www.indoforum.org/t138988/#ixzz1qiEZ88zi
Hak Cipta: www.indoforum.org
AKU BERITAHU KEPADA TEMAN2 AKU MENGGUNAKAN WIFI (RUMAHAN) HOTSPOT. YG SERVERNYA
SEKITAR 700 M DR RUMAH
DIDDAERAHKU BANYAK HOTSPOT....CUMA HOTSPOT YG AKU PAKAI ADALAH YG TERBAIK..KARNA
JARINGANNYA JRG PUTUS ........
BERKAT KEMAMPUANKU INI SAYA HANYA DISURUH BAYAR 100 RB SEBULAN......KARNA AKU YG
MEMBANTU MEMPERBAIKI JARINGAN HOTSPOT TERSE3BUT......
INI AKU KASIH GAMBRAN LAGI SUPAYA SEDIKIT MENGERTI::::::::::
kebetulan server google ahir2 ini mengalami masalah .......ahirnya kondisi speed
y kadang lemot.......jadi aku putuskan memakai server speeduguide tuk membantu j
aringan yg rto
...ini saya perlihatkan ping pada kondisi normal......kita lihat disana ada rto.
....nah ke 4 server ini akan saling menutup rto yg ada.......kalau ping normal n
ya ( ping -t ) mengalami rto semua maka..........pada hari ini kucoba tracert du
lu speedguide...dan seluruh jaringan ip yg ada di speedguide aku ping semua.....
..setelah itu yg di google aku pakai ping www.google.com -t -l 1326
pakai ping www.google.com -t -l 1450
pakai ping www.google.com -t -l 1024
begitupula
pakai ping
pakai ping
pakai ping

yang di open dns

208.67.222.222 -t -l 1326
208.67.222.222 -t -l 1450
208.67.222.222 -t -l 1024

( pada hari ini permintaan ping saya ada sekitar 16 buah mulai dari tracert spee
dguide sampe memberi nilai ping yg berbeda kepada 4 server itu........)
tracert www.speedguide.net
Tracing route to speedguide.net [68.67.73.20]
over a maximum of 30 hops:
1 5 ms 8 ms 26 ms hotspot-sahabat.net.id [10.1.11.1]
2 9 ms 7 ms 3 ms backbone.sahabat-sinjai.net.id [10.24.24.1]
3 45 ms 65 ms 52 ms 1.subnet110-139-200.speedy.telkom.net.id [110.13
9.200.1]
4 56 ms 49 ms 59 ms 125.160.1.173
5 153 ms 101 ms 98 ms if-13-0-1.core1.s9r-singapore.as6453.net [209.58
.82.185]
6 99 ms 107 ms 214 ms if-10-0-0.core2.s9r-singapore.as6453.net [209.58
.82.46]

7 430 ms 657 ms 637 ms if-3-1-0.mcore3.pdi-paloalto.as6453.net [216.6.2

9.125]
8 295 ms 467 ms 452 ms if-13-0-0-817.core3.sqn-sanjose.as6453.net [66.1
98.97.13]
9 * 297 ms 302 ms vlan1105.icore1.sqn-sanjose.as6453.net [66.198.9
7.42]
10 * 303 ms 358 ms ix-10-0.icore1.sqn-sanjose.as6453.net [209.58.11
6.14]
11 282 ms 278 ms 334 ms vlan69.csw1.sanjose1.level3.net [4.68.18.62]
12 300 ms 320 ms 294 ms ae-62-62.ebr2.sanjose1.level3.net [4.69.134.209]
13 313 ms 354 ms 319 ms ae-2-2.ebr2.losangeles1.level3.net [4.69.132.14]
14 484 ms * 375 ms ae-3-3.ebr3.dallas1.level3.net [4.69.132.78]
15 611 ms * 370 ms ae-7-7.ebr3.atlanta2.level3.net [4.69.134.22]
16 451 ms 360 ms 355 ms ae-16-51.car2.atlanta2.level3.net [4.68.103.11]
17 399 ms 348 ms 344 ms 4.71.254.74
18 353 ms 361 ms 370 ms speedguide.net [68.67.73.20]
Trace complete.
C:\Documents and Settings\PT. AMAL NUR>ping www.speedguide.net -t
Pinging speedguide.net [68.67.73.20] with 32 bytes of data:
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply

from
from
from
from
from
from
from
from
from
from
from
from
from
from

68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:
68.67.73.20:

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=1394ms TTL=44
time=810ms TTL=46
time=1896ms TTL=44
time=1122ms TTL=46
time=607ms TTL=46
time=806ms TTL=44
time=811ms TTL=44
time=899ms TTL=44
time=924ms TTL=44
time=937ms TTL=46
time=1029ms TTL=44
time=1077ms TTL=44
time=807ms TTL=46
time=824ms TTL=44

Ping statistics for 68.67.73.20:

Packets: Sent = 14, Received = 14, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 607ms, Maximum = 1896ms, Average = 995ms
Control-C
^C
C:\Documents and Settings\PT. AMAL NUR>ping www.google.com -t
Pinging www.l.google.com [209.85.132.104] with 32 bytes of data:
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply

from
from
from
from
from
from
from
from
from

209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:
209.85.132.104:

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=517ms
time=467ms
time=531ms
time=572ms
time=833ms
time=864ms
time=836ms
time=880ms
time=932ms

TTL=55
TTL=55
TTL=55
TTL=55
TTL=55
TTL=55
TTL=55
TTL=55
TTL=55

Reply from 209.85.132.104:

Reply from 209.85.132.104:
Reply from 209.85.132.104:
Request timed out.
Request timed out.
Reply from 209.85.132.104:
Request timed out.
Request timed out.
Request timed out.
Reply from 209.85.132.104:
Reply from 209.85.132.104:
Reply from 209.85.132.104:
Reply from 209.85.132.104:
Reply from 209.85.132.104:

bytes=32 time=902ms TTL=55

bytes=32 time=959ms TTL=55
bytes=32 time=998ms TTL=55
bytes=32 time=705ms TTL=55

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=96ms TTL=55
time=104ms TTL=55
time=110ms TTL=55
time=303ms TTL=55
time=352ms TTL=55

Ping statistics for 209.85.132.104:

Packets: Sent = 23, Received = 18, Lost = 5 (21% loss),
Approximate round trip times in milli-seconds:
Minimum = 96ms, Maximum = 998ms, Average = 608ms
Control-C
^C
C:\Documents and Settings\PT. AMAL NUR>ping www.yahoo.com -t
Pinging any-fp.wa1.b.yahoo.com [72.30.2.43] with 32 bytes of data:
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply
Reply

from
from
from
from
from
from
from
from
from
from
from
from
from
from
from
from
from

72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:
72.30.2.43:

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=373ms
time=421ms
time=416ms
time=415ms
time=463ms
time=285ms
time=410ms
time=278ms
time=320ms
time=418ms
time=420ms
time=562ms
time=736ms
time=599ms
time=452ms
time=758ms
time=480ms

TTL=51
TTL=51
TTL=51
TTL=51
TTL=51
TTL=51
TTL=49
TTL=51
TTL=49
TTL=49
TTL=49
TTL=51
TTL=51
TTL=51
TTL=51
TTL=51
TTL=49

Ping statistics for 72.30.2.43:

Packets: Sent = 17, Received = 17, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 278ms, Maximum = 758ms, Average = 459ms
Control-C
^C
C:\Documents and Settings\PT. AMAL NUR>ping 208.67.222.222 -t
Pinging 208.67.222.222 with 32 bytes of data:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Request timed out.

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=450ms
time=433ms
time=431ms
time=316ms
time=300ms
time=296ms

TTL=50
TTL=50
TTL=50
TTL=50
TTL=50
TTL=50

Reply from 208.67.222.222:

Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Request timed out.
Request timed out.
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:
Reply from 208.67.222.222:

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=834ms TTL=50
time=1014ms TTL=50
time=1058ms TTL=50
time=1583ms TTL=50
time=1376ms TTL=50

bytes=32
bytes=32
bytes=32
bytes=32
bytes=32

time=293ms
time=296ms
time=326ms
time=286ms
time=300ms

TTL=50
TTL=50
TTL=50
TTL=50
TTL=50

Ping statistics for 208.67.222.222:

Packets: Sent = 19, Received = 16, Lost = 3 (15% loss),
Approximate round trip times in milli-seconds:
Minimum = 286ms, Maximum = 1583ms, Average = 599ms
Control-C
^C
C:\Documents and Settings\PT. AMAL NUR>ping 208.67.222.222 -t
Sumber: Tips memperbaiki jaringan yg suka rto (request time out) - IndoForum htt
p://www.indoforum.org/t138988/#ixzz1qiEfD1Jd
Hak Cipta: www.indoforum.org