Hey ppl,

I'm just wandering if any of you had the same problem as i do. After the recent 2.03 patch i was unable to connect to the wow server. Everytime i put in my account name and password it says i'm unable to connect. I reinstall wow and even formatted my PC but still having the same problem. Wrote to WoW Tech support but the steps they given me i have tried all of them.

So you ppl out there that had the same problem and manage to solve it, Pls do let me know. Appreciate it and thanks

Yea i'm using XP SP2, No other firewalls except the default win firewall which i have set the port forwarding and even tried disabling them as well....none seems to work....sigh.

omg! u guys are right! yes my ip does starts with 124.82.* I tried to used the free proxy and reroute my connections but still unable to. Below is my results which is the same as you guys.

C:\Documents and Settings\Adrian>tracert us.logon.worldofwarcraft.com

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

1 14 ms 187 ms 15 ms 219.93.218.177
2 15 ms 15 ms 15 ms 219.93.218.69
3 15 ms 15 ms 15 ms 210.187.133.65
4 15 ms 15 ms 15 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
5 15 ms 15 ms 15 ms 219.94.12.134
6 234 ms 15 ms 15 ms 210.187.132.83
7 * * 15 ms 58.27.124.50
8 15 ms 15 ms 15 ms 219.93.174.67
9 12.118.124.101 reports: Destination net unreachable.


I have written to tmnut as well and hope they would respond quickly....seriously this suxs.

Anyway thanks to u all i'm aware of whats goin on here. I get more solutions here than posting in WoW forums....gosh.

And yes, if anyone of you get any replies from tmnut pls do update us here ok. Thanks a bunch!

Hey Aurora,

I'm surprised you are unable to do a tracert or log on to WoW with a 219 IP address. My friend who stays in subang that has a similar IP with yours are able to login with no problem. I suggest you to uninstall all your firewall or add in port forwarding with WoW ports to try and get to WoW.

Also those ppl that have the same pbm as i do, can you rougly tell me the area you are playing in or your house maybe which in my case i'm leaving in Putra Heights, Subang Jaya and my ip starts with 124.82.*.* I'm yet to get updates from tmnut yet. blardy hell taking soooo long to reply me....sucks man!

Hey Dewa,

Yeah i notice some areas but minor are using the 124.82.*.* IP address and we can never change the ip address to 219 or 218 or even 60. This 3 are considered a set which the users will get randomly everytime they reset their modems but for us with 124.82 we have no other choice! i tried resetting my modem for 9349264927654 times and it still wont work! i get 124.82 100% everytime. I'm seriously pissed and yet cant do anything about it.

I tried rerouting my proxies to god knows how many countries but from the start point if its still 124.82 its always gonna be 124.82 no matter what you do. This is the 5th day i cant play WoW and i'm getting pretty upset not because i cant play entirely but because i actually paid for both WoW and Streamyx.....sigh..

Also is there anyone or contacts to insiders ...ahem.....that could change areas IPs like mine to any other IPs? pls do let me know....gosh even willing to pay to get my dump IP change. arrghh....

I'll get the tracert for u later tonite. I have no pbm doin a tracert to www.worldofwarcraft.com website just to us.logon.worldofwarcraft.com IP. thats the IP u wanna get to to be able to logon to wow......sigh...depressing man..

Ok Guys, some updates from me.

Thanks to some of my friends i have manage to get hold of the tmnet OSC team, those are the ppl we are looking for and not those so called operators you are referring them as technician coz they are not. They only know how to give u simple intructions to check your connection and thats all however this OSC team are the ones that do the scripting and firewall rules for tmnet. This morning i hv check with them again and apparently according to them, this problem lies between tmnet and AT&T in US that is not accepting our 124. Ip address and not recognizing it that its coming from tmnet therefore unable to route our line to WoW servers. They have already submitted a request to them and awaiting their reply as of yesterday. So pls keep your fingers cross that they will notice it asap and fix our damn pbm soon.

Freaking BC is out and i cant play. How sad is that man. Will update you guys once i receive any news.

All this is bullshit if u ask me....everyone is just trying to point fingers at each other.

Ok this is WoW Tech Support's reply :-

"Hello Adrian,

You should be able to connect. Try contacting your ISP for more information on your connectivity issue and why you are receiving the "destination net unreachable" error message. I usually see "request timed out" messages when the ping hits our firewall. Let me know how it goes.

Feel free to reply to this email if any other technical issues arise.

Regards,
Mike L.
Tech Support
Blizzard Entertainment
http://www.blizzard.com/support"

And this is Streamyx's reply :-

Dear Mr. Adrian,

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, we would like to advise you to proceed with some basic troubleshooting, in order for us to streamline the issue that you are facing currently.

1) Clear Browser Cache.
2) Create new dialer, flush and reconfigure Domain Name Server (DNS).
- (Preferred DNS Server: 202.188.0.133 /Alternate DNS Server: 202.188.1.5)
3) Reboot computer and modem.
4) Try to connect and browse with 3 different IP address.
- (Switch off and switch on the modem to get different IP address each time).

Alternatively, you can contact our Technical Department at 1-300-88-9515 (select option 3 for Technical Assistance) if you need further assistance on the troubleshooting above and if the problem still persists, please provide us the following details for further action.


ALL steps done and still doesnt work! Step 4 above is not true for our case, we ONLY have 124.82.*.* IP address, we do not get 3 different IP address when we reset our modems each time. How many f***ing times must i tell them. If i get 1G each time i told Streamyx bout my IP i would be half there getting my epic flying mount!

Now my only hope to to wait for those OSC team's reply......sigh..

Fields,

Let me guess u had the same pbm coz your IP starts with 124.82.*.* ?? If it is, nothing could be done for now...

I really doubt its WoW's problem, if you think bout it, why would they put any blockage or firewall rules to stop ppl from getting in their servers, they have 8 million players as of today and still growing, why would they do something to jeapardize their business and create more pbms that they already have atm.

Yeah now i have to go to my shop and play at ss15. I prefer to play at home coz its more convenient....sigh...

So its true that tmnet have problem with AT&T as i mention earlier. Well will have to wait and see whats thier reply on this. At least they have been informed on this.....now the questions is that how long they will take to solve this problem.

I'm giving them till 20th and after that i'm seriously gonna go crazy. This is insane. They kept asking me to reset my modem will i get the IPs i want....whats the whole freaking point....124 is 124.....darnit....arrghhh!

This post has been edited by adrian79: Jan 19 2007, 09:51 AM

Hey Fields, thanks for the updates anyway. I did notice in wow forums that yes indeed they are facing the same Unable to connect errors however most of their problems are due to Anti virus softwares or some like u mention key loggers. After un-installing those softwares they are able to log in back. However for our case is pretty much different, for eg, i have ZERO software in my PC except. WIN OS, drivers and WoW. No anti virus, no firewall except Windows default firewall which all port forwarding and min security has been set. So how could there be a conflict in my case.

So back to Tmnet, yes its their issue with AT&T at least for our case in Malaysia players which uses IP starting with 124.82.*.*.

Fields do me a favour. Pls check whats your IP. Thanks

Nope not working for me too! Still same pbm same error msg....sigh..



This post has been edited by adrian79: Jan 21 2007, 09:12 PM

Yup same same! Earlier i edited the post coz i did a wrong tracert...lol this is the correct one


C:\Documents and Settings\Adrian>tracert 12.129.232.111

Tracing route to 12.129.232.111 over a maximum of 30 hops

1 12 ms 11 ms 11 ms 219.93.218.177
2 10 ms 9 ms 10 ms 219.93.218.69
3 11 ms 10 ms 10 ms 210.187.132.65
4 11 ms 11 ms 10 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
5 11 ms 11 ms 10 ms 219.94.12.142
6 11 ms 12 ms 11 ms 210.187.133.83
7 11 ms 11 ms 10 ms 58.27.124.54
8 11 ms 11 ms 11 ms 219.94.9.25
9 12.118.124.93 reports: Destination net unreachable.

Trace complete.

I got a called from tmnet, apparently they said they are aware of the problem and will get it solved by this coming Wednesday. Lets see if its true......sigh....been 2 weeks i cant logon from home....

deletus!!! u serious?!?! can u paste the tracert for us all to see! damn!! now i cant wait to go home and test it out.....omg! after all this waiting!

If its true, tmnet wasnt lying when they said they are fixing it and should be ok latest by Wednesday. Pls update deletus. Thanks bro!

Dewa, how bout u? can u login to WoW yet? how about a tracert since we are using the same IP range. Thanks

hahaha same! oh well...we would know later today then....all the best...

Its true bro....we are able to login now without any lag...


C:\Documents and Settings\Adrian>tracert us.logon.worldofwarcraft.com

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

1 24 ms 25 ms 25 ms 219.93.218.177
2 10 ms 23 ms 22 ms 219.93.218.77
3 23 ms 9 ms 23 ms 210.187.133.65
4 24 ms 23 ms 23 ms brf-odsy01-srp1-0.tm.net.my [210.187.135.1]
5 24 ms 11 ms 23 ms 219.94.12.142
6 11 ms 11 ms 24 ms 210.187.132.83
7 24 ms 25 ms 25 ms 58.27.124.58
8 25 ms 30 ms 25 ms 219.94.9.25
9 195 ms 206 ms 213 ms 12.118.124.41
10 215 ms 220 ms 217 ms tbr1-p012101.la2ca.ip.att.net [12.122.2.250]
11 209 ms 192 ms 206 ms 12.127.3.185
12 210 ms 211 ms 212 ms 12.122.255.74
13 212 ms 210 ms 205 ms mdf001c7613r0004-gig-12-1.lax1.attens.net [12.12
9.193.246]
14 * * * Request timed out.
15 * * * Request timed out.
16 * * * Request timed out.

And yes guys thanks for all the help during this period. Appreciate all your responds and tracerts and opinions given in this post. Well as for now i guess everything is back to normal. Thanks Lowyat for having this helpful forum and what a nice bunch of ppl we have in here! Thanks again and HAPPY LEVELLING! gosh....

LOL yeah Dewa, maintenance bro...no worries la...stuck in office also ok wat, but make sure u r not stuck in office tomolo! HAHA!