Ahh.. a friend who is also hving the same problem like me... and on a 124 IP as well...
Been hving this problem since patch day, and its not WoW fault..

TM did a bad way of re-routing our internet connection... right now I cant get any other IP.. all 124 IP.. manual way or even script way to get 128, 129 or 60 IP..

I did a tracert to us.logon.worldofwarcraft.com and it stops at a 12.xxx IP, see below :

Tracing route to us.logon.worldofwarcraft.com [12.129.232.111] over a maximum of 30 hops:

1 59 ms 67 ms 113 ms 219.93.218.177
2 57 ms 58 ms 58 ms 219.93.218.77
3 57 ms 57 ms 58 ms 210.187.133.65
4 57 ms 59 ms 57 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
5 58 ms 58 ms 57 ms 219.94.12.142
6 58 ms 59 ms 58 ms 210.187.132.83
7 58 ms 59 ms 58 ms 58.27.124.58
8 58 ms 58 ms 57 ms 219.94.9.25
9 12.118.124.41 reports: Destination net unreachable.

Trace complete.

Whats weird is that if I traceroute to one of the game server name listed in the support forum, it is ok..

Tracing route to mdf1-bi8k-1-ve-114.lax1.attens.net [12.129.207.193] over a maximum of 30 hops:

1 61 ms 59 ms 58 ms 219.93.218.177
2 57 ms 57 ms 57 ms 219.93.218.77
3 57 ms 56 ms 57 ms 210.187.132.65
4 58 ms 57 ms 58 ms brf-odsy02-srp1-0.tm.net.my [210.187.135.2]
5 58 ms 58 ms 58 ms 210.187.143.1
6 58 ms 58 ms 59 ms 219.93.174.155
7 57 ms 70 ms 64 ms 203.106.6.154
8 318 ms 320 ms 319 ms if-3-0.core2.LXE-LosAngeles.teleglobe.net [216.6.125.1]
9 441 ms 321 ms 321 ms if-1-2.mcore4.LAA-LosAngeles.teleglobe.net [216.6.85.9]
10 313 ms * 314 ms if-10-0.core2.LAA-LosAngeles.teleglobe.net [66.198.112.29]
11 458 ms 461 ms 468 ms ix-2-0.core2.LAA-LosAngeles.teleglobe.net [66.198.112.14]
12 468 ms 465 ms 463 ms 12.127.3.218
13 * 461 ms 461 ms gar4-p300.la2ca.ip.att.net [12.123.222.89]
14 459 ms * 459 ms 12.122.255.58
15 488 ms 831 ms 490 ms mdf1-bi8k-2-eth-2-1.lax1.attens.net [12.129.192.246]
16 464 ms 462 ms 455 ms mdf1-bi8k-1-ve-114.lax1.attens.net [12.129.207.193]

Trace complete.

To anyone that can play, can you help me.. can you connect to my server, Malygos and get me a netstat report for the server IP.. I need it to do a traceroute and then go punch TMNut in the face with all these numbers.. thx in advance

-Dewa-

Adrian,

same problem..?? me me me !!! Shah Alam.. 124.82* or 124.* as well.. playing from home..
give tmnuts my share of the boots please..

Can someone who is using a 124 IP right now help another fellow WoW player out please..

Need a tracert done from anyone on a 124 IP to :

1) us.logon.worldofwarcraft.com
2) www.worldofwarcraft.com
3) your game server host name if u know

Trying to get TMnuts to work on it ... I want my WoW fix !!!! Coffee and Dunhill doesnt work anymore !!!!

Yep..

The problem is coz of our routing to us.logon.worldofwarcraft.com for authentication..

Somehow $^&*^* doesnt know how to read the damn tracert I sent them.. grrr...

dey say I sent tracert result of 2 separate destination/domain/server..

I finally got a reply from TMnet... via email ...

Dear Sir/Madam,

Thank you for your feedback. Our automated feedback system has forwarded to us for our attention and reply. Firstly, we would like to apologise for the late reply.

With regards to your e-mail, please note that the allocation of IP Address for Home Package users is random and therefore is dynamic everytime you login to Streamyx. Also note that dynamic IP is temporary, and only serve you when you connect to Internet at that particular time. It could be different when the next time you connect. "However, we would like to inform you that if you are facing some problem in playing online game, you should first consult the game server administrator." (added the quotes)

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,

no it does not.. its the way the connection being routed..

right now m hoping for some more / any news from adrian79..

adrian....,
if dey tell u dey dunno how to configure the firewall etc, tell them to come here in the forum n learn la weii.. hehehe

ps: damn la. .BC out oredi.. how to sell my 500 stacks of Thorium bar and make loads of money la like this..??

As for me.. I dont any problem with browsing websites in US.

All thanks to LYN for providing proxy servers info which I use on my secondary browser.

On another note, I got another response from TMNET, see below:
"With regards to your e-mail, please be informed again that to consult with the game server administrator first. This is because, upon checking your tracert result to us.logon.worldofwarcraft.com, it is showed that the tracert is stuck at the 12.118.124.41 IP address which is belonging to US based IP. It is advisable if you could contact the game server administrator for further assistance and they will revert to us should the lagging is from TM Net routing.

On behalf of TM Net, we apologise for any inconveniences caused. Your understanding on this matter is highly appreciated."

They still insist that I should contact the game server administrator to check the game server status and connectivity...

So how was my response to the email? Well.. if you know how the contents of the books ".. for Dummies" that's how I reply back to them..

networking 101.. !sigh

I guess the article that I read in the papers a few days back about our country is lacking of competent Network Njin-near is 95% true lorrr..

Below is an updated tracert with more info of me trying to connect to WoW using the 124 IP (only IP I could get.. )

Tracing route to us.logon.worldofwarcraft.com [ 12.129.232.111] over a maximum of 30 hops:

1 59 ms 67 ms 113 ms 219.93.218.177 (Subang Jaya, Selangor)
2 57 ms 58 ms 58 ms 219.93.218.77 (Subang Jaya, Selangor)
3 57 ms 57 ms 58 ms 210.187.133.65 (Labuan, Sabah)
4 57 ms 59 ms 57 ms brf-odsy01-srp1-0.tm.net.my [ 210.187.135.1] (Kuantan, Pahang)
5 58 ms 58 ms 57 ms 219.94.12.142 (Unknown, Malaysia)
6 58 ms 59 ms 58 ms 210.187.132.83 (Unknown, Malaysia)
7 58 ms 59 ms 58 ms 58.27.124.58 (Kuala Lumpur, Wilayah Persekutuan)
8 58 ms 58 ms 57 ms 219.94.9.25 (Unknown, Malaysia)
9 12.118.124.41 reports: Destination net unreachable. (AT&T WorldNet Services Morristown, New Jersey)
Trace complete.

WTF kind of routing is this?????? who's the f**king genius network engineer in TM (sarcasm included) who did the damn re-routing after Taiwan's earthquake anyway?

Great.. Shah Alam -> Subang -> Labuan -> Kuantan -> (Unknown??) -> KL -> (Unknown??) again? -> AT&T WorldNet Services Morristown, New Jersey.

All the IPs from hop 1 - 8 are owned and registered under TM and they tell me that I must check with the game server administrator to see if there is a block on Blizzard's side???

so damn marah right now.. coz TM's staff are so damn stoopid.. especially the person who did the routing..

BAKA !!!

Sorry Field but I think you are referring to the wrong problem thats not related to us who are on the 124 IP right now... I've gone thru 15 pages in the wow technical support forum and none are related to the current problem that we have

if u look at the previous posts in this thread, you can actually c that the problem for those who are on the 124 IP range is not being able to connect to the WoW authentication server.

i do appreciate your help..

k thx.

Not sure if anyone have seen this latest update so I'm putting it here..

btw.. its from jaring.. cudnt bother with TMNet anymore since they dont event know how to do a proper routing..

Excerpt from Jaring's website:
-------------------------------------------------------------------------------------
Recovery is On Track

Our International traffic is now almost back to normal. A lot of traffic has been diverted through whatever spare capacity that can be made available to us. However, there is no circuit diversity and we still see some packet losses to certain locations. This is to be expected as certain routes are still congested.

The latest info from the cable operator indicated that our main circuit will be repaired by 24 Jan 2007. This is after 10 days delay from the original schedule because the first repair ship was having some problems. It was eventually replaced with another one from Batam. A few more damaged cables will be repaired in stages until 11 Feb 2007. By then we would expect full recovery with circuit diversity to be in place.

Thank you.

Dr Mohamed b. Awang Lah (mal@jaring.my)
Chief Executive Officer
JARING Communications Sdn Bhd

16 January 2007
-----------------------------------------------------------------------------------

!sigh

yay!! TM just changed the date again..

from 23rd to 29th Jan now...

"mind share with us how u know some of the location based on the IP address like for instance 219.94.12.142 is in sabah. which web did u refer to? thanx."

Nitrofang,

I use http://www.dnsstuff.com/
Put the ip that you want to check in the "WHOIS Lookup" box and click the button.. it will tell u the location of the IP, country and state and who owns the ip range that you are searching for.

Deletus dude/dudette,

Yes we could use a tracert result to confirm whether it has been fix or not since TMNet just update their website saying that connection will be back to normal on Jan 29th instead of today..





This post has been edited by dewadurjana: Jan 23 2007, 03:21 PM

at work... cant test..

Deletus better not joke man...

Dying oredi not playing WoW for almost 3 weeks.. tried playing @Autosurf.. but getting 3k latency..

grrrrr...

dont just say can login already la fren...

tracert.. need the tracert to us.logon.worldofwarcraft.com from any 124.xx IP range..

No !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

not on the day I got stuck to stay in the office !!!!!!!!!!!!!

LOL... taking leave tomorrow.. thats for sure..