Downtime who playing online games that connect to oversea, help me out, mod dun close pls!
|
|
 Apr 28 2007, 01:49 AM
|
 
Senior Member
1,253 posts Joined: Jan 2007 From: Columbus, Ohio 
|
QUOTE(soongteck @ Apr 28 2007, 01:47 AM) not sure abt the EW firmware.. but my E EU and ER are the same... oh. u didn't tell me it in port forwarding. then now what to do?at advanced setup have port forwarding.. then inside it got DMZ  |
|
|
|
|
|
Apr 28 2007, 08:01 AM
|
Senior Member
547 posts Joined: Jan 2003 From: Malacca 
|
swt my stupid zyxel have to use CI command to unblock traceroute!!!
  any expert to use it? |
|
|
Apr 28 2007, 10:51 AM
|
VIP
727 posts Joined: Nov 2006
|
QUOTE(soongteck @ Apr 28 2007, 01:22 AM) Tracing route to www.hinet.net [61.219.38.89] Actually this, tracert already shows that the problem lies with TMNet. I've also been bombarding tmnet with my own tracerts and pings and it is very important to highlight to them that the problem lies in their own routing. I've also spoken with follow up as well who claim to have forwarded my case number to the highest level of tech support. That was on Wednesday, 25 April and I'm still waiting for a responseover a maximum of 30 hops: 1 17 ms 17 ms 16 ms 219.93.218.177 2 15 ms 15 ms 40 ms 219.93.216.197 3 16 ms 14 ms 15 ms 210.187.142.1 4 17 ms 15 ms 15 ms 219.93.174.147 5 16 ms 19 ms 16 ms 210.187.129.167 6 987 ms 987 ms 997 ms 219.93.168.250 7 1409 ms 1419 ms 1386 ms 220.128.2.166 8 1397 ms 1402 ms 1407 ms 220.128.1.98 9 1402 ms 1386 ms 1396 ms 220.128.1.113 10 1381 ms 1417 ms 1382 ms 211.22.35.185 11 1385 ms 1356 ms 1382 ms 61.219.38.89 Trace complete. Back to your tracert, the problem obviously doesn't lie with your connection to your local exchange, so no amount of flushing your dns, resetting modem or whatever will help. The problem appears to start at hop 6 which I've bolded. A quick search of the APNIC (Asia Pacific Network Information Center) who is database shows that this IP address is owned by guess who... TMnet. This means that they can't really use their excuse of inter ISP connectivity.. ie blame the Taiwan ISP for the bad connection. And really you shouldn't expect latency to go up to 900+ before it's even left the tmnet network at 219.93.168.250. Pings are useful, but only for showing dropped packets. Unfortunately, pings don't highlight where the problem where the dropped packets arise. You can do a search for yourself at http://wq.apnic.net/apnic-bin/whois.pl to help TMnet do the job that they're supposed to be doing. So careful about giving them tracerts, ie. make sure that only the relevant traceroutes highlighting the problem you're facing go through to them. This post has been edited by Kidicarus: Apr 28 2007, 10:52 AM |
|
|
May 1 2007, 01:14 AM
|
|
Senior Member
547 posts Joined: Jan 2003 From: Malacca
|
A SUPER NOOB PERSON THAT REPLY ME!!! NOW I KNOW THE WHOLE MALAYSIA IS AFTER 1AM QUALITY OF PHONE LINE WILL BECOME SUX! IS IT STUPID??? REMEMBER THIS GUY NAME... NOOB LIKE SH IT!
Dear Mr. Yeong, Thank you for your e-mail to TM Net. Firstly, we would like to apologise for the late reply. With regards to your high latency issue, upon checking the tracert result, please be informed that the result show that it is a latency problem. However, if you are facing this problem after 1.00 am, we suspect that you are experiencing intremittent problem. We suggest you to proceed with the basic steps as below in order to streamline the problem occurred. 1. Check the phone line quality (Ensure clear tone without any noise). 2. Off and on the modem. 3. Bypass splitter/ micro filter/ fax machine/ lightning protector. 4. Stand alone connection, from wall socket to modem (No parallel line). If problem still persists, please provide us the following details for further action. 1) User name: kels 2) Contact Person: Mr. Kelvin 3) Contact Number - Home/Office: - Mobile phone: 4) Operating System: 5) Modem Brand: 6) Modem Light Status: 7) Service Number: 8) Streamyx Package: 9) Latest Tracert and ping result 9) When the problem occurred: 10) When is the best time to call you? Should you require further assistance or would like to submit any enquiry/feedback, kindly visit www.tm.net.my and click "Need Help? Contact our Customer Service". We thank you for taking the time to write to us and look forward to serve you better. Regards, Punitha Balakrishnan Customer Care Support, Internet Services, Customer Service Management, TM Retails. |
|
|
May 1 2007, 01:19 AM
|
Junior Member
256 posts Joined: Sep 2006 From: Britannia
|
QUOTE(kels83 @ May 1 2007, 01:14 AM) A SUPER NOOB PERSON THAT REPLY ME!!! NOW I KNOW THE WHOLE MALAYSIA IS AFTER 1AM QUALITY OF PHONE LINE WILL BECOME SUX! IS IT STUPID??? REMEMBER THIS GUY NAME... NOOB LIKE SH IT! this super noob person who answer you is just a tmnut support robot. they are all like that. what do you expect? did you really think they will help you? like vince mcmahon will say "NO CHANCE IN HELL!!!" You have better chance of calling 100 and ask for a tmnut technician to talk to you. then maybe he will help you and give you some answers.....Dear Mr. Yeong, Thank you for your e-mail to TM Net. Firstly, we would like to apologise for the late reply. With regards to your high latency issue, upon checking the tracert result, please be informed that the result show that it is a latency problem. However, if you are facing this problem after 1.00 am, we suspect that you are experiencing intremittent problem. We suggest you to proceed with the basic steps as below in order to streamline the problem occurred. 1. Check the phone line quality (Ensure clear tone without any noise). 2. Off and on the modem. 3. Bypass splitter/ micro filter/ fax machine/ lightning protector. 4. Stand alone connection, from wall socket to modem (No parallel line). If problem still persists, please provide us the following details for further action. 1) User name: kels 2) Contact Person: Mr. Kelvin 3) Contact Number - Home/Office: - Mobile phone: 4) Operating System: 5) Modem Brand: 6) Modem Light Status: 7) Service Number: 8) Streamyx Package: 9) Latest Tracert and ping result 9) When the problem occurred: 10) When is the best time to call you? Should you require further assistance or would like to submit any enquiry/feedback, kindly visit www.tm.net.my and click "Need Help? Contact our Customer Service". We thank you for taking the time to write to us and look forward to serve you better. Regards, Punitha Balakrishnan Customer Care Support, Internet Services, Customer Service Management, TM Retails. |
|
|
May 2 2007, 10:58 AM
|
|
Senior Member
547 posts Joined: Jan 2003 From: Malacca
|
i have some reply from other forumer! they blame TNB having problem at this time and effect them!!!
 |
|
|
|
|
|
May 3 2007, 06:30 PM
|
Junior Member
6 posts Joined: Apr 2007
|
Now I know why I no longer can play this game smoothly
CODE Pinging www.flyff.gpotato.com [38.112.59.148] with 32 bytes of data: Request timed out. Request timed out. Request timed out. Request timed out. Ping statistics for 38.112.59.148: Packets: Sent = 4, Received = 0, Lost = 4 (100% loss), D:\Documents and Settings\HansHeaven>tracert www.flyff.gpotato.com Tracing route to www.flyff.gpotato.com [38.112.59.148] over a maximum of 30 hops: 1 <1 ms <1 ms <1 ms . [218.111.2.1] 2 42 ms 21 ms 32 ms 219.93.218.177 3 8 ms 8 ms 8 ms 219.93.216.109 4 15 ms 18 ms 18 ms 210.187.133.83 5 7 ms 8 ms 8 ms 210.187.133.81 6 8 ms 8 ms 15 ms 219.94.12.133 7 10 ms 10 ms 19 ms 210.187.15.254 8 163 ms 240 ms 49 ms 202.188.126.132 9 39 ms 10 ms 11 ms 58.27.124.34 10 10 ms 10 ms 11 ms 219.93.173.37 11 209 ms 208 ms 216 ms 219.93.153.150 12 239 ms * 237 ms g1-14.mpd01.sjc03.atlas.cogentco.com [154.54.12. 1] 13 323 ms 231 ms 235 ms v3490.mpd01.sjc01.atlas.cogentco.com [154.54.6.8 1] 14 241 ms * 240 ms t4-1.mpd01.sjc05.atlas.cogentco.com [154.54.6.70 ] 15 * * * Request timed out. 16 * * * Request timed out. 17 * * * Request timed out. 18 * * * Request timed out. 19 * * * Request timed out. 20 * * * Request timed out. 21 * * * Request timed out. 22 * * * Request timed out. 23 * * * Request timed out. 24 * * * Request timed out. 25 * * * Request timed out. 26 * * * Request timed out. 27 * * * Request timed out. 28 * * * Request timed out. 29 * * * Request timed out. 30 * * * Request timed out. Trace complete. |
|
|
May 3 2007, 06:35 PM
|
Senior Member
914 posts Joined: Jan 2003
|
ping to perth used to be like 120ms or so, bestest was about 70ms but didnt last long (this due to singnet hop) now its like 200ms. shhhesh! btw tmnut dont care about this issue at all. as long as u can surf/email tmnut is satisfied!
|
|
|
May 4 2007, 05:44 PM
|
|
Junior Member
287 posts Joined: Oct 2006
|
CODE Pinging www.hinet.net [61.219.38.89] with 32 bytes of data: Reply from 61.219.38.89: bytes=32 time=1687ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1754ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1641ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1563ms TTL=243 Ping statistics for 61.219.38.89: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1563ms, Maximum = 1754ms, Average = 1661ms CODE Tracing route to www.hinet.net [61.219.38.89] over a maximum of 30 hops: 1 * * * Request timed out. 2 1628 ms 1699 ms 1649 ms 219.93.218.177 3 1667 ms * 1472 ms 219.93.216.117 4 1504 ms 1615 ms 1420 ms 210.187.133.83 5 1374 ms 1194 ms 1355 ms 210.187.133.82 6 1353 ms 1419 ms 1362 ms 219.94.12.141 7 1406 ms 1469 ms 1682 ms 210.187.143.1 8 1458 ms 1482 ms 1512 ms 219.93.174.154 9 1552 ms 1589 ms 1474 ms 202.188.0.22 10 1556 ms 1536 ms 1623 ms 219.93.168.250 11 1274 ms 1291 ms 1404 ms 220-128-2-166.HINET-IP.hinet.net [220.128.2.166 12 1381 ms 1260 ms 1398 ms tp-s2-c12r11.router.hinet.net [220.128.1.86] 13 1297 ms 1311 ms 1379 ms tp-s2-c12r1.router.hinet.net [220.128.1.113] 14 1455 ms 1441 ms 1440 ms tp-s2-c6r9.router.hinet.net [211.22.35.1] 15 1589 ms 1671 ms 1687 ms www.hinet.net [61.219.38.89] Trace complete.    |
|
|
May 8 2007, 01:34 PM
|
|
Senior Member
547 posts Joined: Jan 2003 From: Malacca
|
QUOTE(chan01 @ May 4 2007, 05:44 PM) CODE Pinging www.hinet.net [61.219.38.89] with 32 bytes of data: Reply from 61.219.38.89: bytes=32 time=1687ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1754ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1641ms TTL=243 Reply from 61.219.38.89: bytes=32 time=1563ms TTL=243 Ping statistics for 61.219.38.89: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 1563ms, Maximum = 1754ms, Average = 1661ms CODE Tracing route to www.hinet.net [61.219.38.89] over a maximum of 30 hops: 1 * * * Request timed out. 2 1628 ms 1699 ms 1649 ms 219.93.218.177 3 1667 ms * 1472 ms 219.93.216.117 4 1504 ms 1615 ms 1420 ms 210.187.133.83 5 1374 ms 1194 ms 1355 ms 210.187.133.82 6 1353 ms 1419 ms 1362 ms 219.94.12.141 7 1406 ms 1469 ms 1682 ms 210.187.143.1 8 1458 ms 1482 ms 1512 ms 219.93.174.154 9 1552 ms 1589 ms 1474 ms 202.188.0.22 10 1556 ms 1536 ms 1623 ms 219.93.168.250 11 1274 ms 1291 ms 1404 ms 220-128-2-166.HINET-IP.hinet.net [220.128.2.166 12 1381 ms 1260 ms 1398 ms tp-s2-c12r11.router.hinet.net [220.128.1.86] 13 1297 ms 1311 ms 1379 ms tp-s2-c12r1.router.hinet.net [220.128.1.113] 14 1455 ms 1441 ms 1440 ms tp-s2-c6r9.router.hinet.net [211.22.35.1] 15 1589 ms 1671 ms 1687 ms www.hinet.net [61.219.38.89] Trace complete.  |
|
|
May 8 2007, 03:04 PM
|
Senior Member
2,702 posts Joined: Dec 2004 From: P8X-86A
|
Dang, how do to traceroute? what is the command code?
|
|
|
May 8 2007, 04:29 PM
|
|
Senior Member
547 posts Joined: Jan 2003 From: Malacca
|
QUOTE(nightzstar @ May 8 2007, 03:04 PM) Dang, how do to traceroute? what is the command code? tracert www.tmnutz.nutz.my |
|
|
May 8 2007, 04:40 PM
|
Senior Member
852 posts Joined: Jan 2003  
|
Still having lots of timeouts, even for lcoal IP, ping is low but lots of timeouts. Can't even play online games.
|
| Change to: |  0.0217sec
 0.78
 6 queries
 GZIP Disabled
Time is now: 25th November 2025 - 09:25 PM |
Quote