Diablo® III

coming back and now constant d/c

I haven't played for a bit and just now wanted to sit down and play. Im getting a d/c nonstop when trying to enter a game. I managed once to get in a game but every time I tried to use the wp I got a d/c. It goes back to the character screen so maybe its something on blizzards end??

Any help would be appreciated, would like to play again.
Reply Quote
I haven't played for a bit and just now wanted to sit down and play. Im getting a d/c nonstop when trying to enter a game. I managed once to get in a game but every time I tried to use the wp I got a d/c. It goes back to the character screen so maybe its something on blizzards end??

Any help would be appreciated, would like to play again.


I just got d/c too. I hope they fix this tomorrow.
Reply Quote
http://us.battle.net/d3/en/forum/topic/10433523645#1

pathping as well as updating and editing your network card settings may help. Directions+links in "Lag Spikes/High Latency Issues/Game Disconnects (DC's):" section.
Reply Quote
I've tried all the fixes and yet it remains. I get into a game, use a wp, disconnect. Everytime. I've upgraded my firmware, second logon, tracert/pingpath, opened ports, and properly set firewall.

I did move recently and not sure I have tried to play since I moved. I also bought a new router and new network card(usb). But I have 0 issues with all other games and net.

I really want to play the game but its not just annoying rubberbanding or lag, its d/cing and I cannot even play!

Whats odd is I can use the AH, I can run around in town, the second I try to go out of town bam.
Reply Quote
deleting the battle.net cache and even a fresh install of the game?
Reply Quote
working on a reinstall now. I can't get passed the updating blizzard launcher or agent
Reply Quote
After you have uninstalled make sure to delete the Blizzard Entertainment folders.
C:\ProgramData\Blizzard Entertainment AND C:\ProgramData\Battle.net
Restart the computer, then try another installation. Make sure to run the install as administrator, directions here: https://us.battle.net/support/en/article/diablo-iii-installation-troubleshooting
Reply Quote
I finally got d3 to reinstall. I took some drivers from my laptop and got it to work.

Now that being said, my laptop works with d3, at least on my wifes account. Have not tried to sign on mine with it.

But now after reinstalling I get an auto disconnect when trying to enter a game.

I've updated all I could. Windows, network card, internet explorer, router..etc. I've opened every port required, turned off all antivirus stuff and any programs running in the background. I've done tracert and pings but if that were the case why does my laptop work just fine with it??
Reply Quote
11/12/2013 05:18 PMPosted by Odinn
I took some drivers from my laptop and got it to work.


What exactly does that mean? You should install drivers for the equipment you are currently working with, and be retrieving them either directly from the manufacturer or through the windows hardware manager. Copy/Pasting over drivers from one computer to another generally isn't a good idea, especially if they are on a completely separate platform (tower vs. laptop).

If you could post the msinfo32 file here for the computer you are trying to fix, that would be helpful. (please put it in the PRE code block button)
Edited by runit3#1931 on 11/12/2013 6:38 PM PST
Reply Quote
That should have said I took some battle.net files (for the agent) from the laptop lol

before I post the msinfo, what could that help to discover?
Reply Quote
That should have said I took some battle.net files (for the agent) from the laptop lol

before I post the msinfo, what could that help to discover?


If you don't want to post your msinfo due to the name of your PC (or personal info, although it doesn't contain much), you can edit that information out.

The main things I, or anyone else, needs to know to give any kind of accurate relevant advice is:
-OS (Service Pack #)
-CPU (accurate clock speed and thermal information is helpful, but not necessary in most cases)
-GPU(s)
-GPU driver #
-RAM (physical quantity, clocks are also helpful in some cases)
-Virtual Memory amount (page/max)
-Hard Disk the game is installed on (SSD/HD/USB) Free/Used space amount

Other helpful information would be the Network card/driver#, and if you have any other installed hardware like sound cards, RAM Disk utilities, etc.

Also how you are connecting the game to the internet, wireless, hardlined, carrier card, etc. Personal router name+firmware edition could also be helpful, but you can keep that info private, just make sure it is up to date and load the current firmware edition via the manufacturer if needed.

Additionally, performing a disk cleanup on your primary hard drive will eliminate most of the personal info output by msinfo32 that someone could potentially interpret (usually in the "system error memory dump files" check box).
Edited by runit3#1931 on 11/12/2013 11:12 PM PST
Reply Quote
My whole thing is I do not mind at all looking into all this stuff but my pc worked just fine with diablo for a long while. I moved and changed 3 things and im not sure if that was even the issue really.

I changed my router, wireless card (usb) and cable companies. Im not sure how one of the three can be the culprit but what else could it be when it was working for a full year before?

OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
System Manufacturer Dell Inc.
System Model Studio XPS 8100
System Type x64-based PC
Processor Intel(R) Core(TM) i7 CPU 860 @ 2.80GHz, 2801 Mhz, 4 Core(s), 8 Logical Processor(s)
BIOS Version/Date Dell Inc. A05, 7/8/2010
SMBIOS Version 2.6
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Installed Physical Memory (RAM) 8.00 GB
Total Physical Memory 7.96 GB
Available Physical Memory 5.38 GB
Total Virtual Memory 15.9 GB
Available Virtual Memory 13.1 GB
Page File Space 7.96 GB
Page File C:\pagefile.sys

Network stuff I have a linksys EA6500 router version 1 with the most updated drivers (wireless and no chance due to its location for wired) and an AE6000 linksys wireless N usb. I also have Mediacomm cable internet if that has any current issues.

Again the odd part is how well it worked before and now I cannot even so much as play. I've never had consistant d/c like this. And to boot the wifes laptop plays it just fine. I was dead set on it being on blizzards size but not sure now.
Reply Quote
not sure how relevant this is but I got a heartstone beta key recently. I did have the battle.net app working before but this all started when I got errors trying to download HS. I tried every suggestion and I couldn't get it to work. I cannot install the bnet app anymore nor HS. But I have it on my wifes laptop, im more interested in gettin my d3 to work again. And tyvm for your input as it seems you may be the only one.
Reply Quote
Well 2 things are possible.
1) When you copied over the battle.net & Blizzard entertainment folders from another computer something got screwed up. I have no idea how to decipher their files within those folders, but I am under the assumption they are client/PC specific settings/info. Deleting C:\ProgramData\Blizzard Entertainment AND C:\ProgramData\Battle.net, then running Diablo 3 should re-download and replace those files, which you should do.

2) Make sure the router NAT type is set to OPEN and the proper UDP/TCP ports are open, list here: https://us.battle.net/support/en/article/firewall-proxy-router-and-port-configuration
Directions for how to open those ports for your specific router here:
(SINGLE port) http://kb.linksys.com/Linksys/ukp.aspx?pid=96&vw=1&articleid=25787
(RANGE ports)
http://kb.linksys.com/Linksys/ukp.aspx?pid=96&g=96&vw=1&articleid=17241

Also make sure that if you are running windows firewall or a third party virus/firewall utility to add exceptions to those specific ports, and the D3 executables.

3) To clarify any issues of packet loss/firewall blockades on your end run a pathping, directions here: https://us.battle.net/support/en/article/running-a-pathping-test
If you hit a packet loss of 100/100% within the first few hops your wireless connection and/or the router are blocking d3 from communicating with the game servers. Even if you have packet loss of ~5% it may indicate that there is some interference on your wireless band.
Reply Quote
The copied stuff was after the fact, all it did was benefit me as it allowed me to even get into the install for d3.

The router has the ports done, I do not know how to mess with the NAT type tho.

Firewall has exception as well as my only anti virus MSE.

Here was the two, tracert and ping, from earlier.

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 edited out
1 edited out
2 172.30.10.109
3 172.30.10.109
4 172.30.24.117
5 12.249.235.5
6 cr82.mpsmn.ip.att.net [12.122.150.62]
7 cr1.kc9mo.ip.att.net [12.122.153.66]
8 cr1.dvmco.ip.att.net [12.122.3.45]
9 cr2.dvmco.ip.att.net [12.122.31.22]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar20.la2ca.ip.att.net [12.122.128.181]
13 12-122-254-234.attens.net [12.122.254.234]
14 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
15 * * *
Computing statistics for 350 seconds...

Tracing route to 12.129.209.68 over a maximum of 30 hops

1 13 ms 8 ms 9 ms
2 38 ms 39 ms 43 ms 172.30.10.109
3 31 ms 39 ms 59 ms 172.30.10.109
4 48 ms 38 ms 39 ms 172.30.24.117
5 38 ms 39 ms 39 ms 12.249.235.5
6 97 ms 108 ms 109 ms cr82.mpsmn.ip.att.net [12.122.150.62]
7 97 ms 99 ms 100 ms cr1.kc9mo.ip.att.net [12.122.153.66]
8 92 ms 99 ms 99 ms cr1.dvmco.ip.att.net [12.122.3.45]
9 84 ms 91 ms 90 ms cr2.dvmco.ip.att.net [12.122.31.22]
10 98 ms 92 ms 99 ms cr1.slkut.ip.att.net [12.122.30.25]
11 117 ms 93 ms 95 ms cr2.la2ca.ip.att.net [12.122.30.30]
12 84 ms 90 ms 87 ms gar20.la2ca.ip.att.net [12.122.128.181]
13 95 ms 89 ms 99 ms 12-122-254-234.attens.net [12.122.254.234]
14 96 ms 109 ms 99 ms mdf001c7613r0002.lax1.attens.net [206.16.68.54]
15 * * * Request timed out.
16 * * * Request timed out.
17 * * * Request timed out.
18 * * * Request timed out.
19 * * * Request timed out.
20 * * * Request timed out.
21 * * * Request timed out.
22 * * * Request timed out.
23 * * * Request timed out.
24 * * * Request timed out.
25 * * * Request timed out.
26 * * * Request timed out.
27 * * * Request timed out.
28 * * * Request timed out.
29 * * * Request timed out.
30 * * * Request timed out.

Trace complete.

From reading earlier things, if Im not mistaken, there doesn't appear to be much a problem in these. Unless of course I am reading it wrong or do not understand it fully.
Reply Quote
Try to do a path ping, which is different from a tracert. https://us.battle.net/support/en/article/running-a-pathping-test
Reply Quote
the first one was from those directions for a pingpath.
Reply Quote
MVP - Technical Support
View profile
Odinn the pathping can take more than 10 minutes to run so you have to let it go. It looks like you stopped it too early.

The tracert looks good though - no huge latency spikes although AT&T (not part of the Blizzard domain in this case) is a bit higher than your local ISP. I see no problematic timeouts. The timeouts at the end are due to the security measures put in place by Blizzard. The servers are masked to not respond to a ping so will appear to time out when they really don't.
Edited by MissCheetah#1661 on 11/13/2013 2:21 PM PST
Reply Quote
11/13/2013 09:24 AMPosted by Odinn
the first one was from those directions for a pingpath.


As MissCheetah pointed out, the pathping needs to report the calculations. It should look like this:
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\Travis>pathping 12.129.209.68

Tracing route to 12.129.209.68 over a maximum of 30 hops

0 Travis-PC.hsd1.wa.comcast.net. [192.168.1.103]
1 192.168.1.1
2 96.167.76.1
3 te-0-2-0-14-ur08.seattle.wa.seattle.comcast.net [68.86.98.41]
4 ae-20-0-ar03.seattle.wa.seattle.comcast.net [69.139.164.129]
5 he-1-3-0-0-11-cr01.seattle.wa.ibone.comcast.net [68.86.93.169]
6 be-12-pe03.seattle.wa.ibone.comcast.net [68.86.84.106]
7 as7018.seattle.wa.ibone.comcast.net [66.208.229.98]
8 cr82.st0wa.ip.att.net [12.122.84.18]
9 cr2.ptdor.ip.att.net [12.122.5.230]
10 cr1.ptdor.ip.att.net [12.122.30.141]
11 cr1.sffca.ip.att.net [12.122.30.146]
12 cr1.la2ca.ip.att.net [12.122.3.122]
13 gar20.la2ca.ip.att.net [12.122.128.181]
14 12.122.251.190
15 mdf001c7613r0004-gig-10-1.lax1.attens.net [12.129.193.250]
16 * * *
Computing statistics for 375 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Travis-PC.hsd1.wa.comcast.net. [19
2.168.1.103]
0/ 100 = 0% |
1 0ms 0/ 100 = 0% 0/ 100 = 0% 192.168.1.1
0/ 100 = 0% |
2 11ms 0/ 100 = 0% 0/ 100 = 0% 96.167.76.1
0/ 100 = 0% |
3 11ms 0/ 100 = 0% 0/ 100 = 0% te-0-2-0-14-ur08.seattle.wa.seattl
e.comcast.net [68.86.98.41]
0/ 100 = 0% |
4 14ms 0/ 100 = 0% 0/ 100 = 0% ae-20-0-ar03.seattle.wa.seattle.co
mcast.net [69.139.164.129]
0/ 100 = 0% |
5 14ms 0/ 100 = 0% 0/ 100 = 0% he-1-3-0-0-11-cr01.seattle.wa.ibon
e.comcast.net [68.86.93.169]
0/ 100 = 0% |
6 12ms 0/ 100 = 0% 0/ 100 = 0% be-12-pe03.seattle.wa.ibone.comcas
t.net [68.86.84.106]
0/ 100 = 0% |
7 16ms 0/ 100 = 0% 0/ 100 = 0% as7018.seattle.wa.ibone.comcast.ne
t [66.208.229.98]
100/ 100 =100% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr82.st0wa.ip.att.net [12.122.84.1
8]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.ptdor.ip.att.net [12.122.5.230
]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.ptdor.ip.att.net [12.122.30.14
1]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr1.sffca.ip.att.net [12.122.30.14
6]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% cr1.la2ca.ip.att.net [12.122.3.122
]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128
.181]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% 12.122.251.190
0/ 100 = 0% |
15 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0004-gig-10-1.lax1.att
ens.net [12.129.193.250]

Trace complete.

C:\Users\Travis>
Reply Quote
ah sorry, didn't know I was messing with it early.

0 Jim-PC [192.168.1.104]
1 Cisco40147 [192.168.1.1]
2 172.30.10.109
3 172.30.10.109
4 172.30.24.117
5 12.249.235.5
6 cr82.mpsmn.ip.att.net [12.122.150.62]
7 cr1.kc9mo.ip.att.net [12.122.153.66]
8 cr1.dvmco.ip.att.net [12.122.3.45]
9 cr2.dvmco.ip.att.net [12.122.31.22]
10 cr1.slkut.ip.att.net [12.122.30.25]
11 cr2.la2ca.ip.att.net [12.122.30.30]
12 gar20.la2ca.ip.att.net [12.122.128.181]
13 12-122-254-234.attens.net [12.122.254.234]
14 mdf001c7613r0002.lax1.attens.net [206.16.68.54]
15 * * *
Computing statistics for 350 seconds...
Source to Here This Node/Link
Hop RTT Lost/Sent = Pct Lost/Sent = Pct Address
0 Jim-PC xxx
0/ 100 = 0% |
1 8ms 0/ 100 = 0% 0/ 100 = 0% xxx
0/ 100 = 0% |
2 37ms 0/ 100 = 0% 0/ 100 = 0% 172.30.10.109
0/ 100 = 0% |
3 37ms 0/ 100 = 0% 0/ 100 = 0% 172.30.10.109
0/ 100 = 0% |
4 37ms 0/ 100 = 0% 0/ 100 = 0% 172.30.24.117
0/ 100 = 0% |
5 40ms 0/ 100 = 0% 0/ 100 = 0% 12.249.235.5
100/ 100 =100% |
6 --- 100/ 100 =100% 0/ 100 = 0% cr82.mpsmn.ip.att.net [12.122.150.62]
0/ 100 = 0% |
7 --- 100/ 100 =100% 0/ 100 = 0% cr1.kc9mo.ip.att.net [12.122.153.66]
0/ 100 = 0% |
8 --- 100/ 100 =100% 0/ 100 = 0% cr1.dvmco.ip.att.net [12.122.3.45]
0/ 100 = 0% |
9 --- 100/ 100 =100% 0/ 100 = 0% cr2.dvmco.ip.att.net [12.122.31.22]
0/ 100 = 0% |
10 --- 100/ 100 =100% 0/ 100 = 0% cr1.slkut.ip.att.net [12.122.30.25]
0/ 100 = 0% |
11 --- 100/ 100 =100% 0/ 100 = 0% cr2.la2ca.ip.att.net [12.122.30.30]
0/ 100 = 0% |
12 --- 100/ 100 =100% 0/ 100 = 0% gar20.la2ca.ip.att.net [12.122.128.181]
0/ 100 = 0% |
13 --- 100/ 100 =100% 0/ 100 = 0% 12-122-254-234.attens.net [12.122.254.234]
0/ 100 = 0% |
14 --- 100/ 100 =100% 0/ 100 = 0% mdf001c7613r0002.lax1.attens.net [206.16.68.54]

Trace complete.
Reply Quote

Please report any Code of Conduct violations, including:

Threats of violence. We take these seriously and will alert the proper authorities.

Posts containing personal information about other players. This includes physical addresses, e-mail addresses, phone numbers, and inappropriate photos and/or videos.

Harassing or discriminatory language. This will not be tolerated.

Forums Code of Conduct

Report Post # written by

Reason
Explain (256 characters max)
Submit Cancel

Reported!

[Close]