OFFICIAL /K/ "Army" V2, ISP Report Complete, available for dwnld Group
|
|
 Jul 6 2009, 11:19 PM
Return to original view | Post
#1
|
 
Senior Member
955 posts Joined: Sep 2008 From: Petaling Jaya  
|
nice lah! salute. can i join /k/ army? swear will dedicate to it!
you all should have included links to a few of broadband-user-to-user streamyx related thread in networking section of LYN as there is more hard-prove there, u could edit it and do that before sending it out to other agencies etc. nevertheless, nice job. This post has been edited by andrew9292: Jul 6 2009, 11:34 PM |
|
|
Jul 7 2009, 10:24 PM
Return to original view | Post
#2
|
|
Senior Member
955 posts Joined: Sep 2008 From: Petaling Jaya
|
No replies from The Star yet? Takan 3 working days to reply pula... =\
|
|
|
Jul 8 2009, 06:50 PM
Return to original view | Post
#3
|
|
Senior Member
955 posts Joined: Sep 2008 From: Petaling Jaya
|
Nice job on the email to InTech...it's quite understandable that they cant do much i guess =\
I think it's better to start gentle but firm, give indication that if they are going to brush the issue aside, we wont stand down anymore...  However if we start gently and they brush us aside, it will be quite hard and weird for us to suddenly go on rampage. Even today, a BASIC network infrastructure like DNS which is used to translate normal webpage request into "internet language" (IP address) does not seem to respond well. This problem seems to be fixed at around 6.38pm. Below is a ping comparison to TM's DNS and a free, open source and public DNS system OPEN DNS. PING TM DNS C:\Documents and Settings\Andrew>ping 202.188.0.133 -n 25 Pinging 202.188.0.133 with 32 bytes of data: Reply from 202.188.0.133: bytes=32 time=11ms TTL=247 Reply from 202.188.0.133: bytes=32 time=10ms TTL=247 Reply from 202.188.0.133: bytes=32 time=9ms TTL=247 Reply from 202.188.0.133: bytes=32 time=14ms TTL=247 Reply from 202.188.0.133: bytes=32 time=13ms TTL=247 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=21ms TTL=247 Reply from 202.188.0.133: bytes=32 time=17ms TTL=247 Reply from 202.188.0.133: bytes=32 time=16ms TTL=247 Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=9ms TTL=247 Request timed out. Request timed out. Request timed out. Request timed out. Request timed out. Reply from 202.188.0.133: bytes=32 time=9ms TTL=247 Request timed out. Request timed out. Request timed out. Ping statistics for 202.188.0.133: Packets: Sent = 25, Received = 10, Lost = 15 (60% loss), Approximate round trip times in milli-seconds: Minimum = 9ms, Maximum = 21ms, Average = 12ms PING OPEN DNS C:\Documents and Settings\Andrew>ping 208.67.222.222 -n 25 Pinging 208.67.222.222 with 32 bytes of data: Reply from 208.67.222.222: bytes=32 time=213ms TTL=55 Reply from 208.67.222.222: bytes=32 time=243ms TTL=55 Reply from 208.67.222.222: bytes=32 time=215ms TTL=55 Reply from 208.67.222.222: bytes=32 time=214ms TTL=55 Reply from 208.67.222.222: bytes=32 time=215ms TTL=55 Reply from 208.67.222.222: bytes=32 time=206ms TTL=55 Reply from 208.67.222.222: bytes=32 time=210ms TTL=55 Reply from 208.67.222.222: bytes=32 time=216ms TTL=55 Reply from 208.67.222.222: bytes=32 time=235ms TTL=55 Reply from 208.67.222.222: bytes=32 time=210ms TTL=55 Reply from 208.67.222.222: bytes=32 time=206ms TTL=55 Reply from 208.67.222.222: bytes=32 time=234ms TTL=55 Reply from 208.67.222.222: bytes=32 time=207ms TTL=55 Reply from 208.67.222.222: bytes=32 time=215ms TTL=55 Reply from 208.67.222.222: bytes=32 time=214ms TTL=55 Reply from 208.67.222.222: bytes=32 time=205ms TTL=55 Reply from 208.67.222.222: bytes=32 time=242ms TTL=55 Reply from 208.67.222.222: bytes=32 time=214ms TTL=55 Reply from 208.67.222.222: bytes=32 time=205ms TTL=55 Reply from 208.67.222.222: bytes=32 time=243ms TTL=55 Reply from 208.67.222.222: bytes=32 time=206ms TTL=55 Reply from 208.67.222.222: bytes=32 time=215ms TTL=55 Reply from 208.67.222.222: bytes=32 time=235ms TTL=55 Reply from 208.67.222.222: bytes=32 time=205ms TTL=55 Reply from 208.67.222.222: bytes=32 time=211ms TTL=55 Ping statistics for 208.67.222.222: Packets: Sent = 25, Received = 25, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 205ms, Maximum = 243ms, Average = 217ms ------------------------------------------------------------------------------------------------------------------------------------ Looks like there is some drunk ******* in TM wei QUOTE 08/07/2009 announcement title 8th july 2009, but in announcement write 7 july 2009 IPVPN SERVICE INTERRUPTION Dear Valued Customers, Telekom Malaysia Berhad ™ wishes to announce that there was a major disruption of IPVPN services nationwide due to equipment failure on IPVPN nodes at Putrajaya since 11.30 a.m. today, 7 July 2009. As a result, most of the services riding on the IPVPN network such as banking, government and enterprise segments are currently facing difficulties to be connected to their branches and customers. Restoration works on the affected nodes are already in progress. TM expects the complete recovery of its services by 11.00pm, the same day. TM apologizes for any inconvenience caused by this disruption, whilst at the same time, we would like to assure you that we are undertaking all necessary measures to restore our communications services as soon as possible. Customers can call TM at 1060 or e-mail us at help@tm.com.my for any related problems. Thank You.  This post has been edited by andrew9292: Jul 8 2009, 07:02 PM |
|
|
Jul 9 2009, 02:07 AM
Return to original view | Post
#4
|
|
Senior Member
955 posts Joined: Sep 2008 From: Petaling Jaya
|
QUOTE(Kinci @ Jul 9 2009, 01:12 AM) Dam, typical tm net reply. Maybe we should jz blast a few bazookas at them. i'm ready when you're ready   |
| Bump Topic Add ReplyOptions New Topic |
| Change to: |  0.0245sec
 0.58
 7 queries
 GZIP Disabled
Time is now: 4th December 2025 - 11:23 PM |
Quote