Local-only account not connecting to local game server - Resolved

DawieS · 30th December 09, 12:40 AM

I have my children here for the holidays. They have been playing Dota on my prepaid local-only account up to 27 December. Since 28 December it only works with WA international bandwidth. I had to put a stop to it since it could be very expensive.

The game server is war3.co.za. The admin guys on the server say that it is only WA gamers that have this problem, since other ISP's local accounts can connect. They also say that they have not made any changes on the server in the past few days.

Can someone from WA please investigate and correct the problem? Any help would be much appreciated!!

AcidRaZor · 31st December 09, 10:14 AM

It's best if you launch a support ticket (and post this under the gaming section) where Johnathan can have a look at it.

I fear some monkey must have thrown in a wrench or two ****ing up the routing on the gaming protocols severely

DawieS · 7th January 10, 09:55 PM

Don't bother, the children have left...

NeoN · 13th January 10, 04:43 PM

lol... The rest of us are still living with this issue. :/

@AcidRaZor - Can you plz provide me a link to said gaming section, as I'm not 100% sure where to correctly re-create this thread. ty.

DawieS · 13th January 10, 05:35 PM

This is the correct sub-forum to ask for support. Dota is not hosted on the WA gaming service. I was just overwhelmed by the WA response!!!

If nobody from WA even cared to reply in more than a week, how long do you think it will take to fix the problem? If you ask me, it seems that WA now only caters for the resellers market, and are no longer interested in small customers like us!!!

Angelo · 13th January 10, 05:48 PM

Hi guys

I apologize for the delay but I have now escalated this to our engineers to investigate.

I will update this post as soon as I receive feedback on the matter.

Thank you.

NeoN · 14th January 10, 11:53 AM

Thanks Angelo, it's greatly appreciated.

wamatt · 15th January 10, 01:17 PM

Hi Neon, Sorry most guys were on leave. I've asked the relevant people to make sure we get it resolved ASAP for you.

NeoN · 15th January 10, 03:36 PM

Awesome, thanks Matt. ^_^

Angelo · 18th January 10, 09:32 AM

Hi Guys

Our engineers are still attending to the matter.

I will update this post as soon as I have an update.

Thank you.

waJohnathan · 18th January 10, 11:11 AM

I was able to successfully connect to the twilight server however I am still conducting testing. Please could try again and either send me a pm or mail to gamesmaster@webafrica.co.za?

Please include the exact error message when trying to connect to the "Twilight" server and please also include a tracert to war3.co.za while using the local only connection

NeoN · 18th January 10, 11:17 AM

Awesome, ty. I'll test it this evening when I get home from work.

waJohnathan · 20th January 10, 10:43 AM

Hi Neon

Thanks for the updates, I will do some further checking and see where the issue may be

waJohnathan · 25th January 10, 08:03 PM

Hi guys,

Just an update - seems for some reason connecting to the DOTA server seems to also a connection to a limewire server (international) - seems that it may have been used to distribute patches previously although I'm not sure however we will be conducting further in depth analysis and see what we come up with

Slobber · 26th January 10, 12:39 PM

Pretty sure there isn't any connection going out to limewire as this would cause any local service provider to not work (currently saix/is/vodacom all work, it's just WA that doesn't).

I've done some testing and it definitely looks to be some sort of shaping/blocking on your side.

I can telnet the twilight server on TCP 22 (SSH), TCP 80(HTTP), TCP 64738 (Mumble).

I can also confirm that we are not blocking TCP 6112 from any WA range.

Please can you look at this with a little more urgency as a lot of users are complaining. Not resolving this issue is going to lead to people moving back to a saix/IS service.

waJohnathan · 26th January 10, 04:12 PM

The issue is being checked into with urgency. We will be arranging a scheduled test and network log dump for super in depth analysis during the course of tomorrow and trace the connection piece by piece

Slobber · 26th January 10, 04:23 PM

Thanks. If there is anything twilight can do to help, drop myself or Nitrate a note.

Pada · 27th January 10, 12:58 AM

Hi Johnathan,

It could be that Warcraft III is attempting to connect to one of the following AD servers that Blizzard included in their Warcraft III patches (since like v1.21 of like 1 year ago):
madserver.net
OR ad.madserver.net
OR imp.madserver.net
OR media.madserver.net
OR locate.madserver.net

If these AD servers are causing the problem, downloading & running the following batchfile in Windows should resolve the issue: http://www.quickshare.co.za/files/bd...mover.bat.html
All it does is it lets those AD server addresses resolve to 127.0.0.1 by adding the entries in %windir%\system32\drivers\etc\hosts

Regards
Chris

Slobber · 27th January 10, 01:08 AM

I doubt it's that Pada. As I said in my post above, even if you telnet the port it's giving you no result, (just sits with SYN_Sent).

Pada · 27th January 10, 01:13 AM

Sorry, I missed that. My post was simply to state that its not associated with Limewire.
From your posts, I would say that its definitely a port blocking rule from WA's side