 | ERROR 3003(1) | Category: Technical SupportJuly-27-2016 5:08 AM PDT (8 years ago)  |
| I can't login to Battle.net since 3 days! Still this stupid error. Help! | ||
 | ERROR 3003(2) | July-27-2016 7:42 AM PDT (8 years ago) |
| Error 3003 generally means the client couldn't make contact with the server. If the issue started suddenly 3 days ago this will most likely be an Internet Service Provider issue but as with all connection issues it's worth quickly double checking: Complete the following steps back to back till completed then retest the game: Power Cycle FlushDNS Try GoogleDNS Check your Firewall/Ports If the issue continues reply back with a WinMTR: A WinMTR test shows your connection to our servers over time instead of a snap shot, that a pathping or tracert can offer us. This is great at picking up fluctuating connection issues such as your latency spiking up and down or why disconnects are occurring: 1. Download WinMTR 2. Unzip the file to your desktop 3. Open the WinMTR folder and select the 32 or 64 bit version. Choose whichever one corresponds to your version of Windows. Run the WinMTR. 4. Type the IP under “hostâ€: 185.60.112.157 5. Click “start†and open the game. Wait until you experience the latency and let the test run for another 10 minutes before clicking “stopâ€. 6. Click “Copy text to clipboard†and paste it to your comment. Make sure to post between the code blocks. | ||
| ERROR 3003(4) | July-27-2016 2:44 PM PDT (8 years ago) |
| 192.168.0.1 - 1 | 593 | 590 | 0 | 11 | 414 | 5 | Your first hop has minor packet loss that should be zero, but the big issue is your latency spike of 414ms! I'd forward this to your Internet Service Provider to ask them for help checking out the random latency spikes and packet loss. Thank you! | ||
