02-18-2005, 05:42 PM
magisleepy,Feb 15 2005, 03:54 AM Wrote:NOw, that I've been messing with it, and sending inquires, I'm not sure if it's my router anymore. It could be, but it does technically say that it connected, but it won't dl the stupid terms and Agreements.
Oh well, on the plus side, I found a thinking cap and hidden shrine on the same level today.[right][snapback]68094[/snapback][/right]
Possible reasons for failure to download ToS:
1) Unable to connect to server. This would likely be a badly configured router at fault, since you already have one connection to that server for logging on, so it's clearly reachable.
2) Server lacks the required file. The only situation in which I can believe this would happen is if you're connecting to some badly configured battle.net emulator. Note that playing on an emulator with other Blizzard games may have changed your server settings to select the emulator for Diablo as well.
As a relatively easy way to check these: what is listed in the Gateway selection at the MP screen? Gateway is at the bottom left. Also, while it is hung trying to download the file, tab out and run netstat -n. Post here with any lines which contain ":6112" (and post the entire line, please). You're behind a router, so the "local" IP is probably bogus. If you're concerned about posting your public IP address, just X that out. I only need the remote IP (the one next to the :6112) and the connection state.
As an amusing note, it's only because you're using such a badly written client (i.e. Blizzard code) that you're unable to logon. Emulation clients have no problem ignoring braindamaged servers.