Connection interrupts every game..

[BananaPancakes]

hi everyone. i don't know what's going on with my game. i was getting rushed in normal when i had an unlucky error (i didn't read it as i was rushing to get back in before quest gets completed). several attempts to connect back to battle.net were halted when they said my cd key was currently being used, by myself. i wait a bit and eject / pop back in the diablo 2 cd a few times. finally i manage to get back on to battle.net and join the game.

surprisingly, the game says i completed the quest (even though when i first got interrupted the quest wasn't even close to completing). i try to go through the portal and it doesn't work, even though quest log says i have completed it. soon after, i get a connection interrupt. i join back game puzzled, and ever since then anytime im in a game, i get kicked off within a minute. the quest also undid itself, even though i never actually received it, and now it says i need to complete it again.

i have tried with another character, and that character also gets kicked out of games within a minute. no 3rd party programs and i believe this is the first time happening ever in years of playing. can anyone help?

[SirDooFuss]

For wierd stuff like this I follow the following procedure:

Shut down my computer, then the router, then the cable modem. Then turn everything back on in reverse order. It usually works for me.:grin:

[BloZ]

Was it the Diablo quest? I got a similar error once.

I was entering the TP, my friend killed Diablo while I was still loading and I got C/I. When I came back in the game I wasn't able to enter the portal even though it said I had completed the quest.

I just created a new game and it said the quest wasn't done. Everything was OK then. I was a bit annoyed though...

[BananaPancakes]

Yeahhh, it was the diablo quest. BloZ that's pretty much what happened to me except with the added c/i every game. SirDooFuss: that's pretty much what I did, and glad to see it worked. its like the fool proof buddy system (from the simpsons, lol)

so yeah, my games are fine now, though I would still like to know what happened, and in the future how to prevent it. If anyone has any idea it would be great. Thanks everyone

[BloZ]

I believe I had C/I because I lagged the moment I entered the TP (on my screen, the game froze at town), and at the same time Diablo died and created even more lag which caused me to drop out.

My only idea is that you wait for the CS place to load before killing Diablo. Try shutting applications in background too, since it creates even more lag, at least for me.

[kuafu]

so yeah, my games are fine now, though I would still like to know what happened, and in the future how to prevent it. If anyone has any idea it would be great. Thanks everyone

This usually happens when you have a dead diablo2 process hanging in memory. Typical scenario will be your game crashes, you close it and start a new one, but sometimes the old "Game.exe" process will still be in memory. You'll then get C/I in every game you create after few seconds; I think it's a mechanism to prevent two instances using the same CD-key. The simpler fix is to open Task Manager and kill the old process; rebooting certainly works as an alternative to kill that process (as well as all the other processes:smiley:).

[BananaPancakes]

BloZ: well diablo wasn't close to dead when i dropped, but im not sure if it was lagging. anyway i'll be sure to keep your advice in mind next time it gets laggy there, thanks man.

kuafu: wow excellent, thanks for all the information. i'll be sure to try ending the process ( and way easier than rebooting my computer). thats a great explanation.

thanks again for all the help