For Streamyx user.

Ok, today a girl from streamyx technical department have call me!

she said are you feeling ok for the connection right now? i said "yes" but at midnight time from 1am - 8am i still facing the same problem! that the ping to www.hinet.net is over 1k ping.

she said is my firewall all off, i said yes and i said the problem is not only from me but from other fren other state also.

she said how strong is my technical skill @@!! i said still ok lar... but at least i know the problem only from streamyx, if singapore ping to them and canada ping to them is not even over 200ms!!

so she ask me to get a trace route and ping from all user that proof that all having same problem!!!

player who playing WoW, Perfect world2, ro... whatever game connect to over from 1am - 8am time

please help me to get a trace route and ping report post to here then your email address too, i will forward whatever mail they reply me to you guy.

i will write a report if all person getting the same problem

so far my friend from JB, Sarawak few from KL, myself from Malacca getting nor 218,219,60 IP connect at this time sure GOD PING!!

Please help me out dude, i cannot tahan liao!!!

POOR IN ENGLISH DUN COMPLAIN ><

This post has been edited by kels83: Apr 27 2007, 01:46 PM

Did u ask for phone number? lolz
Why they picked u to call?

coz i report 2 days ago, i said the connection now is worst then last few week, last time is 1am - 8am last few days start from 3-4pm already sux! but yesterday i think is fix! and i said the 1am still the same problem! that the story!

by the way, are you facing this problem?

If that's the case i might help you out since i do play perfect world(taiwan)

but first you need to tell me how to get the trace route and ping report in TXT format????

This post has been edited by TimKen: Apr 27 2007, 08:01 PM

124.82.3.*

Pinging www.hinet.net [203.66.88.89] with 32 bytes of data:

Reply from 203.66.88.89: bytes=32 time=79ms TTL=244
Reply from 203.66.88.89: bytes=32 time=128ms TTL=244
Reply from 203.66.88.89: bytes=32 time=79ms TTL=244
Reply from 203.66.88.89: bytes=32 time=87ms TTL=244

Ping statistics for 203.66.88.89:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 128ms, Average = 93ms

Tracing route to www.hinet.net [203.66.88.89]
over a maximum of 30 hops:

1 54 ms 85 ms 20 ms 219.93.218.177
2 11 ms 49 ms 30 ms 219.93.218.77
3 16 ms 10 ms 18 ms 210.187.132.65
4 34 ms 43 ms 14 ms brf-odsy02-srp1-0.tm.net.my [210.187.135.2]
5 11 ms 10 ms 20 ms 210.187.143.1
6 22 ms 18 ms 38 ms 219.93.174.155
7 58 ms 46 ms 17 ms 210.187.129.167
8 85 ms 123 ms 94 ms 219.93.168.250
9 74 ms 84 ms 79 ms 220-128-2-166.HINET-IP.hinet.net [220.128.2.166]

10 76 ms 191 ms 144 ms 220-128-1-162.HINET-IP.hinet.net [220.128.1.162]

11 100 ms 73 ms 116 ms 220-128-1-237.HINET-IP.hinet.net [220.128.1.237]

12 75 ms 73 ms 74 ms tp-s2-c12r1.router.hinet.net [211.22.34.2]
13 133 ms 88 ms 75 ms tp-s2-c6r10.router.hinet.net [211.22.35.9]
14 95 ms 157 ms 138 ms www.hinet.net [203.66.88.89]

Trace complete.

PING www.hinet.net (61.219.38.89): 56 data bytes
64 bytes from 61.219.38.89: icmp_seq=0 ttl=233 time=447.966 ms
64 bytes from 61.219.38.89: icmp_seq=1 ttl=233 time=437.813 ms
64 bytes from 61.219.38.89: icmp_seq=2 ttl=233 time=367.707 ms
64 bytes from 61.219.38.89: icmp_seq=3 ttl=233 time=357.732 ms
^C
--- www.hinet.net ping statistics ---
4 packets transmitted, 4 packets received, 0% packet loss
round-trip min/avg/max/stddev = 357.732/402.804/447.966/40.400 ms


Traceroute

traceroute: Warning: www.hinet.net has multiple addresses; using 61.219.38.89
traceroute to www.hinet.net (61.219.38.89), 64 hops max, 40 byte packets
1 majulahsingapura.sg (192.168.1.1) 4.324 ms 3.463 ms 3.647 ms
2 wbb1.fwa4.jaring.my (202.190.131.1) 4.760 ms 4.446 ms 6.173 ms
3 * * *
4 10.128.0.10 (10.128.0.10) 108.961 ms 131.607 ms 110.017 ms
5 61.6.38.241 (61.6.38.241) 120.052 ms 150.831 ms 150.076 ms
6 fe4-1-0.bkj4.jaring.my (61.6.163.3) 119.999 ms 462.459 ms 120.001 ms
7 ge2-0-0.bkj92.jaring.my (161.142.173.7) 317.334 ms 508.118 ms 164.335 ms
8 pos6-0-mea90.jaring.my (61.6.9.82) 239.808 ms 133.483 ms 129.001 ms
9 flg90-pos3-0-0.jaring.my (61.6.13.158) 120.408 ms 212.247 ms 219.776 ms
10 62.216.145.65 (62.216.145.65) 390.330 ms 402.229 ms 319.038 ms
11 so-2-2-0.0.cjr04.hkg003.flagtel.com (62.216.128.5) 899.686 ms 322.080 ms 329.966 ms
12 * * *
13 tp-c12r5.router.hinet.net (211.75.91.206) 380.486 ms 372.175 ms 370.039 ms
14 * tp-s2-c12r11.router.hinet.net (220.128.1.70) 369.923 ms 372.144 ms
15 220-128-1-229.hinet-ip.hinet.net (220.128.1.229) 359.960 ms 352.100 ms 380.285 ms
16 * tp-s2-c12r1.router.hinet.net (211.22.34.78) 369.930 ms *
17 tp-s2-c6r9.router.hinet.net (211.22.35.1) 392.234 ms * 372.369 ms
18 * * *
19 * * *
20 * * *

Edited : blah....had to remove my IP !

This post has been edited by prasys: Apr 27 2007, 08:11 PM

thank you so much!!!

the command will be

tracert www.hinet.net > sample.txt
ping www.hinet.net > sample.txt

help me out, cause i dont think this is my problem, is the whole malaysia facing the same problem!

please help me to trace route after 1am, if you guy are free... PLEASE!!! i want report it to tmnutz!!!

This post has been edited by kels83: Apr 27 2007, 08:13 PM

I dont think my traceroute would help you , its on a JARING. Certainly they will not help you

Your trace route is help! because i can show them your trace route have reply and mine timeout!

then he ask me do trace route?

i thought you wanted the results on 1am~8am = =??

Yeah I will help you!!!

Attached my screenshot to them, and tell the hell them this is my ping to hinet, from Streamyx account name: yoyosdsl, from Bintulu Sarawak, subscription package Streamyx Enterprise SDSL 1.5M, 1.5Mbps Download and 1.5Mbps Upload, RM618 monthly pay for this shit.


Attached thumbnail(s)

don't worry i'll help you to defeat them
i will post tomorrow for IP 60.50 and 124.82
all do screenshot for him please

IP: 60.53.67.XX




This post has been edited by [W]HIT3_@NG3L: Apr 28 2007, 12:01 AM

mine:

Pinging www.hinet.net [61.219.38.89] with 32 bytes of data:



Reply from 61.219.38.89: bytes=32 time=539ms TTL=233

Reply from 61.219.38.89: bytes=32 time=546ms TTL=233

Reply from 61.219.38.89: bytes=32 time=512ms TTL=233

Reply from 61.219.38.89: bytes=32 time=527ms TTL=233



Ping statistics for 61.219.38.89:

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

Approximate round trip times in milli-seconds:

Minimum = 512ms, Maximum = 546ms, Average = 531ms

will try to trace route

cannot traceroute. i think tmnut blocked trace route.

Tmnet doesn't block traceroute.
Dont assume things.
It's your own router/firewall that blocked traceroute.

how to unblocked traceroute?? i using aztech dsl600ew.

there is no advanced setup or DMZ.

cannot also.