11-30-2003, 02:05 AM
I decided to try some classic Diablo on my relatively new laptop. I am running Windows XP Home, Zone Alarm, and a Microsoft Wireless Base Station hooked to a Cisco dsl router. I have patched Diablo to 1.09b.
The problem: I cannot connect to battle.net. I have no problem connecting Diablo II to battle.net but Diablo dies at "querying gateway". When I cancel, it crashes so hard that I eventually have to do a hard reset to get rid of the remaining process. In my wireless base station, I have set all the ports that the battle.net support page and other messages indicate, 6112-6119 UDP and TCP in and out. I even threw in 4000 TCP in and out since D2 uses that port. I have attempted to run through a virtual dmz for this machine. I have checked the registry and found the proper gateways listed. I have given full permissions to diablo.exe, both in and out, for Zone Alarm. I have tried turning Zone Alarm off completely. I have tried running in both Win95 and WinNT compatibility modes. No luck.
Any suggestions? It seems like I am forgetting something that had to be done previously with the various patches. I am to the point where figuring out the problem is no longer fun. I usually enjoy getting things to work on these oh so frustrating machines too. I already had one huge problem with connectivity on this machine earlier this week. (I won't go into details as the solution turned out to be embarrassingly easy after wasting most of a day and finally a full hour on the phone with a tech.) I just don't need this much frustration again so soon. Diablo CD's and laptop computers tend not to appreciate being thrown against walls. :o
Oh yeah, the game does work playing single or multiplayer as long as I don't try connecting to battle.net.
Any and all help greatly appreciated!
The problem: I cannot connect to battle.net. I have no problem connecting Diablo II to battle.net but Diablo dies at "querying gateway". When I cancel, it crashes so hard that I eventually have to do a hard reset to get rid of the remaining process. In my wireless base station, I have set all the ports that the battle.net support page and other messages indicate, 6112-6119 UDP and TCP in and out. I even threw in 4000 TCP in and out since D2 uses that port. I have attempted to run through a virtual dmz for this machine. I have checked the registry and found the proper gateways listed. I have given full permissions to diablo.exe, both in and out, for Zone Alarm. I have tried turning Zone Alarm off completely. I have tried running in both Win95 and WinNT compatibility modes. No luck.
Any suggestions? It seems like I am forgetting something that had to be done previously with the various patches. I am to the point where figuring out the problem is no longer fun. I usually enjoy getting things to work on these oh so frustrating machines too. I already had one huge problem with connectivity on this machine earlier this week. (I won't go into details as the solution turned out to be embarrassingly easy after wasting most of a day and finally a full hour on the phone with a tech.) I just don't need this much frustration again so soon. Diablo CD's and laptop computers tend not to appreciate being thrown against walls. :o
Oh yeah, the game does work playing single or multiplayer as long as I don't try connecting to battle.net.
Any and all help greatly appreciated!
Lochnar[ITB]
Freshman Diablo
![[Image: jsoho8.png]](http://i61.tinypic.com/jsoho8.png)
![[Image: 10gmtrs.png]](http://i60.tinypic.com/10gmtrs.png)
"I reject your reality and substitute my own."
"You don't know how strong you can be until strong is the only option."
"Think deeply, speak gently, love much, laugh loudly, give freely, be kind."
"Talk, Laugh, Love."
Freshman Diablo
"I reject your reality and substitute my own."
"You don't know how strong you can be until strong is the only option."
"Think deeply, speak gently, love much, laugh loudly, give freely, be kind."
"Talk, Laugh, Love."