R
Ross T.
Last week, I was playing Diablo II: Lord of Destruction
across my home network, two Win2k Pro computers, Linksys
router, Netgear printserver. Everything worked fine up
until a day or two ago. Now, when I try to play a network
game of Diablo II, the game errors out with the follow
notice:
Halt
Location: D2Net\SRC\Client.app, line #108
Expression: Socket
When I click on that window, it closes, the game closes
and I get this notice:
Unhandled Exception:
Access_Violation (c0000005)
Now, here's the kicker and why I'm on a Windows Support
board: I think it has something to do with TCP/IP and not
the game.
Both of my computers have a manually set IP address,
subnet mask, gateway and DNS servers. The DNS servers are
the same. The computer I'm using to write this post
obviously doesn't have the same problem. ^^
On the problem computer, I can see the other elements
(computers, printserver) in the network in Network
Neighborhood. I can access the elements in Network
Neighborhood, copy files, etc. I can ping elements within
the network AND computers outside the network i.e. on the
Internet.
BUT, in addition to the error that I receive for Diablo
II, I can't call up anything in Internet Explorer. If I
use a domain name (www.duxcw.com) or the IP address
(216.92.56.121) I still get the same error page. Also, I
can't call up my router page in the browser either. Other
than these two things, everything works fine.
Last bits of info:
**I can't telnet.
**When I run tracert on an Internet computer (a battle.net
server) I get an "unable to resolve target system" error.
**When I run nslookup, I get an error that says that
nslookup could not resolve names for my DNS servers.
**This is all in addition to all of the standard hardware
troubleshooting, like checking the cable, router, NIC,
etc. Everything else seems to check out just fine.
**I've checked Blizzard (maker of the game) and their
support site is pretty useless as far as this particular
problem goes.
As you can see, I've tried everything I know and I'm
coming up empty. Aside from the frustration of
having "random" errors in windows (of which I have had
very few since upgrading to Windows 2000 Professional)
such that something that worked a few days ago no longer
works, I can't satiate my renewed habit of Diablo II
network play with my wife.
Any help would be greatly appreciated.
Ross T.
across my home network, two Win2k Pro computers, Linksys
router, Netgear printserver. Everything worked fine up
until a day or two ago. Now, when I try to play a network
game of Diablo II, the game errors out with the follow
notice:
Halt
Location: D2Net\SRC\Client.app, line #108
Expression: Socket
When I click on that window, it closes, the game closes
and I get this notice:
Unhandled Exception:
Access_Violation (c0000005)
Now, here's the kicker and why I'm on a Windows Support
board: I think it has something to do with TCP/IP and not
the game.
Both of my computers have a manually set IP address,
subnet mask, gateway and DNS servers. The DNS servers are
the same. The computer I'm using to write this post
obviously doesn't have the same problem. ^^
On the problem computer, I can see the other elements
(computers, printserver) in the network in Network
Neighborhood. I can access the elements in Network
Neighborhood, copy files, etc. I can ping elements within
the network AND computers outside the network i.e. on the
Internet.
BUT, in addition to the error that I receive for Diablo
II, I can't call up anything in Internet Explorer. If I
use a domain name (www.duxcw.com) or the IP address
(216.92.56.121) I still get the same error page. Also, I
can't call up my router page in the browser either. Other
than these two things, everything works fine.
Last bits of info:
**I can't telnet.
**When I run tracert on an Internet computer (a battle.net
server) I get an "unable to resolve target system" error.
**When I run nslookup, I get an error that says that
nslookup could not resolve names for my DNS servers.
**This is all in addition to all of the standard hardware
troubleshooting, like checking the cable, router, NIC,
etc. Everything else seems to check out just fine.
**I've checked Blizzard (maker of the game) and their
support site is pretty useless as far as this particular
problem goes.
As you can see, I've tried everything I know and I'm
coming up empty. Aside from the frustration of
having "random" errors in windows (of which I have had
very few since upgrading to Windows 2000 Professional)
such that something that worked a few days ago no longer
works, I can't satiate my renewed habit of Diablo II
network play with my wife.
Any help would be greatly appreciated.
Ross T.