Hi, I can’t log into my account in SC2. I’m logged into the battle.net app in windows 10, hitting play, then after the game loads and tries to authenticate, i get “error, an error has occurred”. I then try to log in through the game again, but it just sits on the “Connecting to Blizzard services” screen. I’ve tried reinstalling the game, reinstalling the battle.net client, switching to beta, and looking for the public test.exe file (which I didn’t have) and rebooting my computer in between every attempted fix, and nothing has worked. I’m in Eastern Canada with version 5.0.2.81102 SCII installed trying to log into the Americas server.
Hey, rEEldEEdlEEr! Thank you for the details here. The game is up to date and should be working. By chance, does SC2 work when you switch the region above the play button to something else like Europe?
If so, this does indicate connection issues to the Americas region, could you gather a WinMTR test? Run the test until the problem occurs for 5 to 10 minutes. Copy and paste the text file created and paste it between two ~~~ like so:
~~~
WinMTR Here
~~~
If you have issues pasting here, use Pastebin and post the end of the link. (ie. 123456 for pastebin.com/123456)
Hello, thanks for the reply. The game behaves the same for all 3 regions (error, then gets stuck on the “Connecting to Blizzard services” screen). Please find the WinMTR file below. I let the game try to connect for about 10 minutes.
|------------------------------------------------------------------------------------------|
| WinMTR statistics |
| Host - % | Sent | Recv | Best | Avrg | Wrst | Last |
|------------------------------------------------|------|------|------|------|------|------|
| mynetwork - 50 | 204 | 104 | 0 | 56 | 2808 | 1 |
| 10.11.16.225 - 50 | 204 | 104 | 0 | 61 | 2810 | 3 |
| No response from host - 100 | 121 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 121 | 0 | 0 | 0 | 0 | 0 |
|tcore3x-ottawa23_bundle-ether12.net.bell.ca - 50 | 204 | 104 | 0 | 63 | 2818 | 5 |
| dis32-ottawa23_ae0.net.bell.ca - 50 | 204 | 104 | 0 | 60 | 2831 | 3 |
|tcore3x-ottawa23_bundle-ether7.net.bell.ca - 50 | 204 | 104 | 0 | 73 | 2824 | 15 |
| tcore4-montreal01_0-14-0-0.net.bell.ca - 50 | 204 | 104 | 0 | 71 | 2824 | 17 |
|tcore4-newyorkaa_hundredgige0-4-0-0.net.bell.ca - 49 | 203 | 104 | 14 | 73 | 2829 | 17 |
| bx10-newyork83_ae1.net.bell.ca - 49 | 203 | 104 | 17 | 74 | 2824 | 17 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| ae1-br01-eqny8.as57976.net - 50 | 202 | 103 | 81 | 208 | 3414 | 82 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| No response from host - 100 | 120 | 0 | 0 | 0 | 0 | 0 |
| et-0-0-0-pe02-swlv10.as57976.net - 51 | 199 | 99 | 80 | 139 | 2888 | 81 |
| las-swlv10-ia-bons-02.as57976.net - 49 | 203 | 104 | 82 | 137 | 2891 | 83 |
| 137.221.105.15 - 49 | 203 | 104 | 80 | 138 | 2894 | 81 |
| 137.221.106.104 - 51 | 199 | 99 | 80 | 137 | 2888 | 81 |
|________________________________________________|______|______|______|______|______|______|
WinMTR v0.92 GPL V2 by Appnor MSP - Fully Managed Hosting & Cloud Provider
Thank you for the details and WinMTR test, rEEldEEdlEEr! The WinMTR is test is consistently showing 49-51% packet loss throughout the test. The problem is starting on the home network.
| mynetwork -
50 | 204 | 104 | 0 |
In addition to the home network showing packet loss, the average latency is at 56ms, which is extraordinarily high for the home network. This should typically be under 10ms for a wireless connection or 1ms for a wired connection. At it’s worst latency, it’s showing reaching up to 2800+ms.
These steps may help with the situation, but it’s strongly recommended to have the internet provider take a look at the connection and home network a bit further.
-
If on Windows 10, try resetting the network settings.
- Click on the Start Menu
- Select on the Settings
option. - In the Windows Settings, click on “Network & Internet”
- Near the bottom of the new window, click on “Network Reset”
Try again, and if it persists, try rebooting to help with the changes made from the Network Reset.
-
If wireless, it may help to try a wired connection if possible. If wired is not an option and you have a dual band connection, then it may help to switch between the 2.4Ghz and 5Ghz bands.
-
If you have a separate router and modem, try bypassing the router to see if this helps with the connection. If it works, there may be a setting or something going awry with the router.
-
If bypassing the router works or isn’t possible, disabling the mitigation settings on the device may help with the issue.
- QoS (Quality of Service)
- WMM (Wireless Multimedia)
- UPnP (Universal Plug and Play)
The settings for these can vary from depending on the device model. It’s not something that we help with directly because the settings and locations can vary. The router manufacturer or Internet Service Provider (if the router/modem was provided by them) can help look for these settings.
Hopefully, one of these suggestions helps with the issue! If the problem does continue, you’ll want to check with the ISP on the device, signal/lines near by, and have them take a look at the connection test.
Ok, this is weird, because I don’t get any latency or packet loss until I try to run the game. I also don’t get latency or packet loss when connected to any other site. I also can run the game perfectly from my other computer connected to the same network. I never had an issue running the game until the latest patch was installed. I tried turning off my firewall as well and it didn’t help.
Hi Caterpepi, Something weird is still happening. If I interrupt the game as it loads by opening the task manager then go back to the game, I’m all logged in. Otherwise, if I just let the game run normally, I get the same error and the game won’t log me in. I’m also noticing that Starcraft 1 can’t authenticate either. Both applications have full permissions to pass through the firewall and my internet works fine except when the game is running in full screen. I also noticed the packet loss only occurs when the game is running in full screen and the packet loss stops when the game is minimized.
I discovered that there was a BIOS update available for my computer. That fixed the issue.
Thanks for the update, rEEldEEdlEEr! Glad to hear you were able to find a resolution to the issue 
It’s interesting that the BIOS update seemed to help with the error.