 | error code 3007 and random dc's in game (plz post here)(1) | Category: Technical SupportApril-25-2016 11:29 AM PDT (9 years ago)  |
| Dear blizz, Been having the error 3007 and random dc's for days now. Game is unplayable. Every 20 min i get kicked. I dont use wifi and tested my internet speed. Did all of your troubleshooting thingies ( sec logon and so on....) and no luck. Updated all my drivers. Seems that the US servers have it too. http://us.battle.net/d3/en/forum/topic/20742950517 Seems strange to me that i can play perfectly for months and suddenly i have this problem. Pll with the same problem plz post here. Ty in advance, Vaevictis | ||
 | error code 3007 and random dc's in game (plz post here)(4) | April-27-2016 5:46 AM PDT (9 years ago) |
| Hello all, I am sorry to hear about your problem. Have you both tried the help give in this article, including the advanced steps? If so, could i both ask you to post a dxdiag and MSInfo, traceroute and a pathping here? If the data is too big to be posted on the forum directly, you can use a page like pastebin.com and post the link to it here then. Kind regards _______________________________________ What's your opinion? https://www.surveymonkey.com/r/Kiemmaki | ||
| error code 3007 and random dc's in game (plz post here)(7) | April-27-2016 12:04 PM PDT (9 years ago) |
| Hello everybody, In order to possibly help all of you, could you all please post a dxdiag and MSInfo, traceroute and a pathping in this thread? If the data is too big to be posted on the forum directly, you can use a page like pastebin.com and post the link to it here then. Kind regards _______________________________________ What's your opinion? https://www.surveymonkey.com/r/Kiemmaki | ||
 | error code 3007 and random dc's in game (plz post here)(12) | April-30-2016 9:10 AM PDT (9 years ago) |
| Hello all, If you're having trouble connecting to Diablo III, please provide us with the following information: - Details of issue: - Date/time it started: - City/Country: - Internet Provider: - Traceroute (right after a disconnection or whenever you're experiencing the issue) - Pathping (right after a disconnection or whenever you're experiencing the issue) - Looking Glass report (right after a disconnection or whenever you're experiencing the issue) Even if the issue ends up being in out network, we do need the data to investigate and escalate to the technicians, should it be necessary. @Konduur Your pathping seems to show packet loss since very early in your connection: 1 0ms 30/ 100 = 30% 1/ 100 = 1% B78100 [192.168.1.1] 0/ 100 = 0% | 2 38ms 29/ 100 = 29% 0/ 100 = 0% sge78-1-82-228-23-254.fbx.proxad.net [82.228.23.254] 1/ 100 = 1% | 3 36ms 30/ 100 = 30% 0/ 100 = 0% 213.228.18.254 0/ 100 = 0% | 4 39ms 30/ 100 = 30% 0/ 100 = 0% bzn-crs16-2-be1009.intf.routers.proxad.net [194.149.161.9] 0/ 100 = 0% | 5 49ms 30/ 100 = 30% 0/ 100 = 0% amsterdam-9k-1-be1004.intf.routers.proxad.net [194.149.163.50] If you haven't yet, please make sure you follow all the steps in this article, including advanced, and see if it makes any difference: battle.net/support/article/611 ______________________________________________________ Got feedback about the support I'm providing? Leave your comments here! | ||
