Battle.net Issues

Snork

So I'm LANning Diablo II: Lord of Destruction with my friends at the moment and we're all (obviously) on a LAN from my wireless router (three on ethernet, one on wireless). All three other people (two ethernet, one wireless) can connect and log in to b.net, I cannot. It stalls for a little while at 'Connecting to the Fastest Server', and then tells me that I am not connected to the internet, which I obviously am.

I downloaded the patch from Blizzard, and that hasn't done anything.

I also tried power cycling my router and modem as well as restarting my computer and uninstalling and reinstalling D2.

My friend recommended doing this Run utility called tracert. The syntax is tracert battle.net.useast and it opens Command Prompt for like an eighth of a second, and then it shuts down.


Help?

Thanatos

Run cmd. Then, in the command prompt, type in "tracert battle.net.useast."

Snork

Unable to resolve target system name battle.net.useast

KungFu

Make sure port 6112 is forwarded to your comp on your router.

stigweard

Snork wrote:

Unable to resolve target system name battle.net.useast

try useast.battle.net Tracert uses dns to get the ip to do the resolution and their are no domains that end in useast.

Snork

After it goes through all 30 hops should it be ready to do good things?

KungFu

http://www.blizzard.com/support/?id=mdt000p for Diablo II Support Page.

Diablo II:

* Allow port 6112 TCP out and allow established sessions in
* Allow port 4000 TCP out (realm games)
* Allow port 4000 TCP out and in (hosting open games only)

Just some maybe helpful information.

Snork

How do I fix those things? I can't imagine why that would be the problem because I think it's worked on this router before, but I'll try it. How do I configure the router settings and stuff?

KungFu

http://www.blizzard.com/support/?id=msi0445p for Blizzard Ports information page.

http://www.portforward.com/ has information and walkthroughs for different routers to help you port forward. Just find your router on it. (Brand name and model)

If you're using any Firewalls, they need the ports forwarded as well.

krapst78

All traceroute does is show the path of your connection to the US East Battle.net server. The fact that you are getting some hops means that at least you are getting the correct DNS information and you are able to connect outbound to the battle.net servers.

The fact that everyone else connecting through your router can connect to the server and you can't, makes me believe that you're experiencing a firewall problem. You should check your firewall program and make sure that it is not blocking any data from battle.net. Usually most firewalls will let you set specific applications to connect to your system.

Snork

So the port forwarding isn't working. I also used logging in to my router to turn off its SPI Firewall as well as checking Windows Firewall, making sure it is off, and making an exception for DII anyway. After the SPI Firewall didn't work, I turned it back on because I'm not sure if I should leave it off. But does anyone know what's going on? Everyone else on my router is still connecting fine. Could it be my computer?

blincoln

Port forwarding isn't going to work in a situation where four people are trying to use the same router. I don't know what the solution is, but I know that much.

piL

If the other people aren't using it can you log on to battle.net. I'm talking out of my ass here, but it's possible they're limiting the number of people per port or some such (WolfET did this).