This might sound very simple for someone but I don't know what happened. 3 days ago I installed Diablo 2 on my vista for my brother and I created a TCP/IP game. I then went over to the vista, entered my ip (since we run on a network), and he joined the game without a single problem. Now, I'm able to create the game but when he trys to join he gets the message that he can't connect to the server. I get the same thing when he hosts a game as well. I didn't change any setting nor did he since he is only 6 and doesn't know how to. So what happened? Any chance I could fix this?

I'm ~75% certain that people with the same IP can't play with each other. I don't know where I remember reading/hearing about that, but I'm fairly sure that's the case.

Actually, you can. (Well, if he's on a network, the number on the end will be different. If it was the same IP, they'd be on the same computer, lulz.)

Most likely, game.exe in your Diablo 2 folder is being blocked by your firewall.

In your firewall's "exceptions" tab, click add program, then browse (if necessary), and select game.exe in your Diablo 2 folder.

..you may need to do the same to Diablo II.exe.

We have done this before where we have played on the network. And yes our IP address is different by one number. I have put the allowed checkmark on the firewall list, but I will try the method of using the same Diablo 2.exe. I know that the only thing that has changed since when we last played was that I added the -skiptobnet tag at the end of the .exe file to go right into Battle.net when I start up. I'll change it and see what happens.

It is vista you may need to turn off UAC and possibly port forward.

Post has been edited 1 time(s), last time on Aug 22 2008, 6:01 pm by Twitch.

Maybe install the TCP/IP Protocolls on your comp?

Different CDKeys?