QUOTE(hih @ Mar 20 2009, 11:15 PM)
Thanks for your reply tarpaucase.
I was thinking if somebody can prove that certain IPs are no good.
For example x.x.x.x are always disconnect IPs, or y.y.y. are log in only download NG IPs,
and known widely by all the user of TM.
Then if I complain to TM, I just need to tell them x.x.x.x are no good and is proved, I don't want it. Maybe the answer is simply "sorry sir, we will change it"
But now if I tell them which IP is no good and I don't want it,
The answer will be ----right click start ....... type cmd........ sir your report number.....
Bye.
For this problem to be solve, there's a way you can prove it to them. I've.. always wanted to do this because my new home? I'm stuck on 124.x.x.x which is extremely bad if you're a gamer. I suspect it could be due to a couple of things.. my guess is..
1) different IP routes you through different gateways that TM has. Some gateways are congested as hell, and the routing is just not good to where you want to go..
2) some block of IPs probably go through some (call me paranoid but..) packetshaper-like devices - and misconfiguration of these devices are more often than not, the culprit for most applications(the ones that don't use common ports) not behaving properly. to the people who sold these devices to TM, and misconfigured them, I hope you rot in hell for all eternity.
Calling the helpdesk won't do any good. I doubt they know what's going on with your connection - it's hard to blame them as I don't think they're also given the relevant information to help you in the first place.
What I plan to do (when I have the time) - or if anyone has the time to do so for that matter, set up something like a smokeping server, ping to each of the hops to.. say a destination to the US (not the actual US hops itself) and see which hop in the network is the packet loss happening, and this has to be done over a period of 24 hours and if possible, over a week - to see if it's a congestion issue or not(well it's more like to prove if it is, i highly doubt it's a congestion thing - because latency is normal, and with congestion, it's usually associated with a rise in latency... usually)
And this ping has to be done from good IPs and bad IPs so we can see the difference.
Once that's done, I plan to email it to TM somehow and hopefully get a response from them.
Take note when talking to TM you must stressed that this issue is DOMESTIC. If you tell them "oh I have packet loss when connecting to US" and they'll tell you that networks outside of their jurisdiction, is beyond their control - which is true, there's not much they can do about that. What you need to stress to them when handling this problem is that you need to inform them that this problem is local, it's not overseas. The problem is INSIDE your local network (if it can be proven).
It's a LOT of work.. which is why now I'm THINKING of resigning to the alternative. forking out RM500 bucks for a frickin 3G USB modem to do the job instead of screamyx.. :/