I have had a problem connecting to battle.net from WC3 TFT AFTER I patched 1.23. I played on Bnet the day before so I don't think I am baned (also because a temporary ban would have been resolved by now and I don't have any wc3 addons(hax ect)). A few of my friends have patched and they can get on Bnet fine. I am the only one using WC3 at my IP. I have reinstalled and repatched but that did not resolve the problem. I think the problem is some how related to the gateway because it never stays the same. When I open WC3 it is blank and I have to reselect USeast even if I just press single player and go back.
I have run the Bnet diagnostic tool and here is the result (I have allowed it though my firewall)
http://i121.photobucket.com/albums/o218/magerunner55/345678.jpg
Ya crazy apparently 11001 means the host doesn't exist but I don't think this is true.
anyway thx ahead of time and IB4 hacker down
Sixen
USWest
1. Re: WC3 Bnet connection problem 04/19/2009 01:42:37 AM PDT
I suggest bypassing the router by plugging the modem in directly to your computer. That will tell us if the source of the problem is your router or not.
Ok I figured out the problem, when I install the patch some files in regedit. My friend with a ligit game had file Battle.net gateway I did not his contained this.
1007
00
uswest.battle.net
8
Lordaeron (U.S. West)
useast.battle.net
6
Azeroth (U.S. East)
asia.battle.net
-9
Kalimdor (Asia)
europe.battle.net
-1
Northrend (Europe)
beta.battle.net
8
Westfall (Beta)
I put this in and it still didnt work, Im thinking that more then that file is messed up in the regedit. anyway I can scan it or somthing because talking to my friend over the internet is a pain when he doesnt know what to do. (I reinstalled last night and repatched)
Ok so I got a copy of a friends WC3 that was patched 1.23 however when I opened it the patch number was 1.22 now after i patched it the same result happened and I have not been able to connect with Bnet diagnostic tool and with WC3. error 11001 on the tool still.
Like I have said before I think the registry is getting messed up when I patch to 1.23 but I don't know anyway of fixing it unless there is a scanner for the registry.
HALP?
Sixen
USWest
4. Re: WC3 Bnet connection problem 04/22/2009 10:57:44 PM PDT
I suggest bypassing the router by plugging the modem in directly to your computer. That will tell us if the source of the problem is your router or not.
Please run me a tracert. To run a tracert, follow the steps below:
1) Go to Start > Run
2) Type in "command" or "cmd" depending on your OS.
3) Make sure the directory you are in is your desktop. You can change directories using the "cd" command.
4) Type in "tracert *realm.battle.net > hi.txt".
5) You let the tracert run, and there should be a new .txt file on your desktop. (30 is the last run)
6) Post the contents of "hi.txt" in a reply.
*: Change this with your realm. For example, useast.battle.net.
(If you use a Mac, please let me know and I will tell you how to specifically run it on a Mac)
Can you try running in Selective Startup? This will stop other programs from running in the background. To run in Selective Startup, view the link below:
Windows:
(http://us.blizzard.com/support/article.xml?articleId=21052).
Macs:
(http://us.blizzard.com/support/article.xml?articleId=21123).
I deleted my folder and put on a friends who is patched to 1.23 but when i opened WC3 it said patch 1.22 even tho it said 1.23 before, so i tried DLing the patch from just going into Bnet but that didnt work so i deleted all WC3 again put on my friends then patched manually with (it was 1.22 before i manually patched)
Sixen is correct, using someone else's copy of the game and then trying to patch it with another patch is not a good idea.
I recommend uninstalling the game and reinstalling it then patching using one of the the links we have here:
http://us.blizzard.com/support/article.xml?articleId=21224
So I uninstalled and then reinstalled with my CD's and the keys on the CD's then I used that link to patch, I still cant connect to battle.net. It just gives the same reason, I may need to manually connect to the internet etc.
Well my registry (after the use of your manual patch thingy) has removed the server list from the registry so I'm guessing my registry is wrong, this was one of the problems I'm assuming that made me make this thread.
