StarCraft 2 Can not connect to B-net servers

So, this is a fresh install of the game. I can sign into battlenet and select Play for StarCraft 2. I get a message that says ‘Can not connect to Blizzard Services’. Then I get the login screen. I type in my id and password (yes, I verified that I am using the correct id and password) and I get another message saying Error. Blizzard network is down for maintenance. please try again. This is for all three regions.

I have run the scan to verify the install and have run the patch to make sure I am up to date. I have run in Admin mode and have made sure that the firewall isn’t blocking anything. it took me 4 plus hours to download the game, so I am not uninstalling and reinstalling. I just want to play. Even offline if that is all that is available until a solution can be made.

Edit: This has been going on for 2 days. I am POSITIVE the problem is not the Blizzard server. It has to be something with the authentication process, which is really stupid considering it is a free to play game, that I paid for years ago.

4 Likes

Hey thespyder,

Lets try this to see if it works:

Delete the PTR executable.

  1. On the Blizzard Application, go to the StarCraft II tab.
  2. Click on Options :gear: then Show in Explorer
  3. Under the Starcraft II folder, delete the StarCraft II Public Test(.exe) file.
  4. Try launching StarCraft II again.
1 Like

I have the same issue. Once battle.net is launched, I can see the promo content from the main screen but my user status on the top right just says “Connecting…”. I’ve verified my firewall is allowing all traffic from my computer to pass through and I can see connections to BN servers on port 1119 are passing. When pinging the servers I’m getting responses in ~16ms.

The proposed solution doesn’t seem to apply to me. There is no “StarCraft II Public Test.exe” file in that path. I suppose I can try deleting and re-installing SC and see if that helps.

1 Like

I uninstalled and re-installed both StarCraft 2 and Battle.net to no avail. However, now upon launching I’m getting a different error message:

Could not log in to Battle.net
More help: BLZBNTBGS80000011 (2) <— which links to the following article:

Before it seemed as if I was able to log in to Battle.net, or at least launch it even if the list of users just said “Connecting…” but now I’m not even able to get that far.

Here are the results of my WinMTR. Note that I’m using 137.221.106.102 as the target host in WinMTR because that’s where Battle.net seems to be trying to connect to. There’s not much use of running WinMTR against the NA SC2 servers (as per an article I found in the Knowledge Base) given I can’t get past the Battle.net authentication screen.

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                 ----- redacted -----    0 |   59 |   59 |    0 |    0 |    0 |    0 |
|                 ----- redacted -----    0 |   59 |   59 |    0 |    0 |    1 |    0 |
|                           71.148.149.60 -    0 |   59 |   59 |    1 |    1 |    1 |    1 |
|                           12.123.15.178 -    0 |   59 |   59 |    4 |    8 |   12 |   11 |
|                           12.122.163.34 -    0 |   59 |   59 |    4 |    8 |   12 |    9 |
|                   cr83.sj2ca.ip.att.net -    0 |   59 |   59 |    4 |    4 |    5 |    5 |
|                          12.245.169.126 -    0 |   59 |   59 |    5 |    7 |   50 |    5 |
|              ae1-br02-eqsv5.as57976.net -    0 |   59 |   59 |   15 |   16 |   62 |   15 |
|       xe-0-0-1-1-br02-eqla1.as57976.net -    0 |   59 |   59 |   15 |   19 |   65 |   16 |
|        et-0-0-29-br01-eqla1.as57976.net -    0 |   59 |   59 |   20 |  158 |  584 |  157 |
|                   No response from host -  100 |   12 |    0 |    0 |    0 |    0 |    0 |
|        et-0-0-0-pe04-swlv10.as57976.net -    0 |   59 |   59 |   16 |   16 |   23 |   16 |
|       las-swlv10-ia-bons-04.as57976.net -    0 |   59 |   59 |   16 |   16 |   17 |   17 |
|                          137.221.105.15 -    0 |   59 |   59 |   15 |   15 |   19 |   15 |
|                         137.221.106.102 -    0 |   59 |   59 |   16 |   16 |   17 |   16 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

Hey there MrJohnBBQ,

Your issue is definitely different than what the OP was encountering, since yours is happening on the Battle.net app itself rather than after launching the game.

It sounds like either a firewall is blocking the connection, or perhaps your internet provider is having issues connecting you to the Battle.net servers. You mentioned configuring the firewall, is that the built in Windows firewall you checked? Or are you using a third-party or hardware firewall?

If you are able to try connecting through a mobile data connection or through a VPN to see if that allows Battle.net to connect, that might help narrow things down further to determine if the problem is only happening on your home network with the main ISP connection.

Hey Jambrix,

I’m behind an actual hardware firewall. Your suggestion of trying a different route of access worked! The firewall was upgraded recently and something must have changed. Either that or my wired internet provider is blocking something and my cel provider isn’t (less likely). At least now we’ve ruled out something on Blizzard’s side.

Thanks again for the insight!

There is no SCII tab with this error.

Good to hear MrJohnBBQ!

SiegeGodz - In the Battle.net app you would click on the Starcraft II icon at the top in the list of games. This is what I meant by Starcraft II “tab”, apologies for the confusion.

From there, the Options button is to the right of the Play button.

Had the same issue. and it worked perfectly.
deleting the test.exe file did the trick

Hey I’m having a similar issue connecting to the americas server… I ran WinMTR on both uswest and useast, and I believe I saw an issue on useast:

|------------------------------------------------------------------------------------------|
|                                      WinMTR statistics                                   |
|                       Host              -   %  | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
|                          GT-AC5300-5D40 -    0 |   65 |   65 |    0 |    0 |    6 |    0 |
|                               70.77.0.1 -    0 |   65 |   65 |    7 |   11 |   20 |    8 |
|          rc3no-be116-1.cg.shawcable.net -    0 |   65 |   65 |    8 |   13 |   22 |   13 |
|                           24.244.57.181 -    0 |   65 |   65 |    8 |   19 |  168 |   10 |
|                             24.244.57.5 -    0 |   65 |   65 |    8 |   14 |   23 |   12 |
|            rc3no-be214.cg.shawcable.net -    0 |   65 |   65 |    6 |   15 |   24 |   15 |
|            rc2wt-be100.wa.shawcable.net -    0 |   65 |   65 |   23 |   27 |   37 |   26 |
|     rc6wt-tge0-10-0-11.wa.shawcable.net -    0 |   65 |   65 |   28 |   37 |   85 |   36 |
|              ae1-br02-eqse2.as57976.net -    0 |   65 |   65 |   55 |   63 |  137 |  137 |
|                   No response from host -  100 |   13 |    0 |    0 |    0 |    0 |    0 |
|         et-0-0-1-pe01-eqch2.as57976.net -    0 |   65 |   65 |   56 |   60 |   72 |   68 |
|                           24.105.62.129 -    0 |   65 |   65 |   55 |   59 |   71 |   69 |
|________________________________________________|______|______|______|______|______|______|
   WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider

The uswest seemed fine. I am not sure if this is an ISP issue or if the router is on blizzard’s end.

Edit: I also don’t have any test executables in my install folder.

And just as a side note… I live in Western Canada, so why would the server try to route me to the useast IP?

I had this exact same issue, and deleting “StarCraft II Public Test.exe” file resolved it. Thanks Jambrix!

Same problem here, no PTR.exe file to delete, ran WinMTR (using the Americas IP), and instantly got “no response from host”. I just changed over my firewall and antivirus, but I’m not sure what’s stopping it; seemingly nothing that I can fix on my end.

I changed over the firewall and antivirus because several times in the past, some updates have changed obscure settings that appears to mess with my Logitech speakers (they will not turn on at all despite being plugged in and working earlier today). They stopped before the changes though. The issues with the speakers has happened probably 4-5 times prior to today.

Edit1-add relevant tests.
Edit2-update: turning off the vpn allowed it to login instantly.

PING:
PING 103.77.232.60 (103.77.232.60) 56(84) bytes of data.
64 bytes from 103.77.232.60: icmp_seq=1 ttl=47 time=201 ms
64 bytes from 103.77.232.60: icmp_seq=2 ttl=47 time=201 ms
64 bytes from 103.77.232.60: icmp_seq=3 ttl=47 time=201 ms
64 bytes from 103.77.232.60: icmp_seq=4 ttl=47 time=201 ms

— 103.77.232.60 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2998ms
rtt min/avg/max/mdev = 201.430/201.606/201.902/0.177 ms

12/01/2022 11:52:48 UTC

TRACEROUTE:
traceroute to 103.77.232.60 (103.77.232.60), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.249 ms 0.257 ms 0.259 ms
2 37.244.23.131 (37.244.23.131) 0.481 ms 0.501 ms 0.564 ms
3 24.105.62.152 (24.105.62.152) 0.870 ms 0.886 ms 0.953 ms
4 137.221.66.14 (137.221.66.14) 0.953 ms 1.040 ms 1.051 ms
5 137.221.69.76 (137.221.69.76) 43.700 ms 43.708 ms 43.710 ms
6 * * *
7 * * *
8 137.221.68.32 (137.221.68.32) 46.617 ms 46.824 ms 46.835 ms
9 * * *
10 45.112.244.182 (45.112.244.182) 201.196 ms 202.863 ms 202.838 ms
11 203.209.194.154 (203.209.194.154) 202.754 ms 207.618 ms 206.799 ms
12 203.209.194.155 (203.209.194.155) 206.715 ms 206.695 ms 201.456 ms
13 103.192.173.244 (103.192.173.244) 201.440 ms 201.447 ms 201.407 ms
14 103.77.232.60 (103.77.232.60) 201.495 ms * 205.924 ms

12/01/2022 11:52:48 UTC

TRACEROUTE:
traceroute to 103.77.232.60 (103.77.232.60), 15 hops max, 60 byte packets
1 Blizzard Blizzard 0.327 ms 0.311 ms 0.309 ms
2 37.244.23.131 (37.244.23.131) 0.452 ms 0.513 ms 0.560 ms
3 24.105.62.152 (24.105.62.152) 1.124 ms 1.128 ms 1.128 ms
4 137.221.66.14 (137.221.66.14) 0.992 ms 1.000 ms 1.050 ms
5 137.221.69.76 (137.221.69.76) 43.950 ms 43.986 ms 43.985 ms
6 * * *
7 * * *
8 137.221.68.32 (137.221.68.32) 46.959 ms 46.991 ms 46.988 ms
9 * * *
10 45.112.244.182 (45.112.244.182) 201.265 ms 202.120 ms 202.120 ms
11 203.209.194.154 (203.209.194.154) 202.898 ms 201.009 ms 200.996 ms
12 203.209.194.155 (203.209.194.155) 201.438 ms 201.445 ms 201.471 ms
13 103.192.173.244 (103.192.173.244) 201.454 ms 201.360 ms 201.394 ms
14 103.77.232.60 (103.77.232.60) 201.457 ms 201.434 ms 201.508 ms

12/01/2022 11:52:48 UTC

PING:
PING 103.77.232.60 (103.77.232.60) 56(84) bytes of data.
64 bytes from 103.77.232.60: icmp_seq=1 ttl=47 time=203 ms
64 bytes from 103.77.232.60: icmp_seq=2 ttl=47 time=202 ms
64 bytes from 103.77.232.60: icmp_seq=3 ttl=47 time=202 ms
64 bytes from 103.77.232.60: icmp_seq=4 ttl=47 time=203 ms

— 103.77.232.60 ping statistics —
4 packets transmitted, 4 received, 0% packet loss, time 2999ms
rtt min/avg/max/mdev = 202.204/203.030/203.805/0.731 ms

12/01/2022 11:52:49 UTC

MTR:
Start: Wed Jan 12 11:52:48 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.4 0.0
2.|-- 37.244.23.131 0.0% 10 0.4 0.5 0.4 0.7 0.0
3.|-- 24.105.62.152 0.0% 10 1.0 0.9 0.7 1.1 0.0
4.|-- 137.221.66.14 0.0% 10 1.3 1.6 1.0 5.9 1.3
5.|-- 137.221.69.76 0.0% 10 74.5 135.1 43.5 486.5 138.1
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 137.221.68.32 0.0% 10 46.7 47.6 46.5 55.3 2.6
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 45.112.244.182 0.0% 10 201.4 201.6 201.3 202.3 0.0
11.|-- 203.209.194.154 0.0% 10 201.1 201.5 201.0 203.5 0.7
12.|-- 203.209.194.155 0.0% 10 201.5 202.0 201.4 207.1 1.6
13.|-- 103.192.173.244 0.0% 10 201.5 201.5 201.4 201.6 0.0
14.|-- 103.77.232.60 0.0% 10 203.1 202.0 201.4 203.8 0.6

12/01/2022 11:52:48 UTC

MTR:
Start: Wed Jan 12 11:52:48 2022 Blizzard 1.|-- Blizzard 0.0% 10 0.2 0.3 0.2 0.6 0.0
2.|-- 37.244.23.131 0.0% 10 0.5 0.5 0.4 0.6 0.0
3.|-- 24.105.62.152 0.0% 10 1.1 1.0 0.7 1.1 0.0
4.|-- 137.221.66.14 0.0% 10 1.2 2.2 1.0 10.2 2.8
5.|-- 137.221.69.76 0.0% 10 43.6 108.1 43.5 282.5 93.7
6.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
7.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
8.|-- 137.221.68.32 0.0% 10 101.3 56.5 46.5 101.3 17.2
9.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0
10.|-- 45.112.244.182 0.0% 10 202.8 201.6 201.2 202.8 0.3
11.|-- 203.209.194.154 0.0% 10 201.0 201.1 201.0 201.2 0.0
12.|-- 203.209.194.155 0.0% 10 201.4 201.5 201.4 201.6 0.0
13.|-- 103.192.173.244 0.0% 10 201.6 201.5 201.4 201.7 0.0
14.|-- 103.77.232.60 0.0% 10 202.2 202.5 201.5 205.9 1.3

12/01/2022 11:52:48 UTC

Does this mean your problem was resolved by turning your VPN off? Unfortunately for me, I’ve tried with and without a VPN to no avail.

Edit: Here’s everything that I remember trying so far…

  • Reinstalled SC2
  • Reinstalled bnet client
  • Used beta version of bnet client
  • Checked SC2 dir for any test-related executables (none exist)
  • Attempted using multiple PCs (I’m using a new win11 pc + tried on my old win10 pc that had previously worked)
  • Restarted all hardware (including router and modem)
  • Updated drivers and firmware of all hardware
  • Tried using a vpn to route through a different way
  • Disabled firewalls (both PC and router firewalls)
  • I have no antivirus software other than windows defender (which I also tried to disable)
  • I have tethered to my mobile device (off of my LAN and router/modem)

As an additional note… I’ve managed to connect twice since I started having issues several days ago. Both of those times it was close to timing out (timing just based on eyeballing it). I can also connect to the other servers fine (but my coop progress isn’t on them).

Edit 2:
I think I was reading the trace wrong; it seems to be arriving at the destination… so I’m not sure what else would be causing the issue.

I’ve also tried using my router’s game radar to ping SC2 server IPs, and it strangely doesn’t return a ping for uswest on the first pass. But before I updated the firmware for my router (as a result of attempting to fix this issue), it was running firmware that had previously worked fine. So because of that I still don’t think it could be my router… I just don’t have a stable connection going to uswest or useast specifically.

I am having the same issue it seems as MrJohnBBQ (no file to delete), but I am lost at how to reroute a VPN or firewall? My CPU has not had recent updates, so not sure why this is happening.

I am not very tech savvy, but need assistance. Please help!!

I’m just downloaded SC2 and I can log into the battle.net interface but when I launch the game and have to relog into the SC2 server I get an error that says there is a temporary outage of the battle.net server please try again later. I have got this error for 5 days now. I looked at some similar solutions and I don’t see a starcraft II public test(.exe) file to delete in the starcraft II folder. Any ideas how to fix?

Forgot to add in that I re-install battle.net and ran repair on SC II with still no luck.

Hey PopeaDope,

The issue in this thread is old and isn’t related to the recent connections issues.

There is a main thread for this recent issue that you can follow here.

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.