It seems that you're using an outdated browser. Some things may not work as they should (or don't work at all).
We suggest you upgrade newer and better browser like: Chrome, Firefox, Internet Explorer or Opera

×
Community
DiabloTrouble getting battle.net working(78 posts)(78 posts)
(78 posts)
Pages:
1
2
3
4
5
6
This is my favourite topic
Posted March 07, 2019
Hello,

I think i'll stick to this thread.
I got the same problem - over and over. Reseting to main menu aint working for me, same as reseting the game.

I've given access to Diablo1 in Windows Defender Firewall, and still no luck in joining bn in playable mode.

Could somebody give some advices how to proceed?

Cheers,
w.
Posted March 07, 2019
I have the same problem. PortForward ok, Windows firewall Ok, Enter Bnet and exit over and over don't work :(
Posted March 07, 2019
All set up on Firewall but still can't create or join any game...same UDP error. Port range is 6112-6119
Posted March 07, 2019
Hello,

I have another message about battlnet needs upgrade and finally i have message like in attachment, Maybe im doing something wrong? Thanks in advance for advice
Attachments:
diablo.bmp (162 Kb)
Posted March 07, 2019
For anyone with this issue I got it to work by making sure to add port forward to both the modem, and the router. If you don't do this for both then it will not let you connect to battle.net.

1. Go to the modem, and go under devices to find the router's ip number.
2. Next add port forward for the modem, and add a new port.
3. Name it to what ever you want, and select the type as tcp/udp.
4. Then make External Starting Port 6112, and make External Ending Port 6119.
5. Now enter the router IP number, and save/apply.
6. Next go to the router settings, and go to devices to find the computer ip number.
7. In the router go to add port forward, and repeat steps 3 & 4.
8. Finally enter the computers IP number, and save/apply.

Classic version of Diable should now be able to connect to battle.net. If you still have issue make sure you do the steps required for firewall permission settings, and try again. Hope this helps.
Posted March 07, 2019
This is not how I remember the battle.net of old. Back then, I could definitely join people who had public IP addresses, even without using port forwarding. Port Forwarding was just the means to be able to host your own games and have other people actually join your game. But you could still join other hosts, even without being able to host yourself. Why is it limited in such a way that you cannot even check the game list or join a game now?

I have been using shared internet access for years, which means that any port forwarding magic is useless for me, because my ISP would need to do the port forwarding for me. I'm afraid that anyone with a shared internet access will be unable to play over battle.net aswell.
Attachments:
d1.jpg (49 Kb)
Posted March 08, 2019
Please solve this problem, There is no need to forward port to connect to a serice at Cloud. Even batllenet. I have Diablo II play at Battlenet without port forwarding.

Att,

Mariano
Post edited March 08, 2019 by Trackerbr
Posted March 08, 2019
When i try to connect at battlenet in classic mode i get this screen.
Attachments:
batlenetissue.jpg (459 Kb)
Post edited March 08, 2019 by Clownsanity
Posted March 08, 2019
I am also having the same UPD Port error. Just being another voice and hopefully this issue will be looked into.
Posted March 08, 2019
Here is what fixed it for me:

Go to "Change Gateway" from multiplayer menu
Select "Global" (even though it was already selected)
Try now

Oblaram the Sorcerer
Posted March 08, 2019
I solved this by opening manually the door in my router :), can't share a specific solution since depends on your router, just connect to it and check the optiions usually advanced one and create a rule for triggering ports (6112 UDP in this case)
Posted March 08, 2019
This issue is persistent and none of the previous fixes work.

I have:
Created a rule in windows firewall.
--Went as far as disabling firewall and antivirus, on the chance they were the issue, no change.

Set up port forwarding on router for ports 6112 - 6119
Rebooted router - 3 times, no change.

Joined Diablo, went back and forth from Battle.net to selection screen over and over, no change.
Restarted the game multiple times, no change.

This should not be as much of an issue as it is, and its happening for a lot of people.


Please fix this...

-Draggonoth
Posted March 08, 2019
Same here. I tried everything and everything failed. No problems with Diablo 2 and Starcraft 1 :-/
Posted March 08, 2019
I just fixed this issue using an entirely different, weird method.

After receiving the error message, I went back and selected "Modem" instead of "Battle.net" to start a multiplayer session. After that, I clicked back and went back to "Battle.net" once more, and the error message did not reappear, and I'm now able to create and join games.

Perhaps this is akin to the Fonz smacking the Juke Box to get it to work? (I know this reference is dated, but.. well so is this game)

So to recap the steps I took:

1. Attempt to connect via Battle.net and receive the UDP error message.
2. Go back to the multiplayer menu and select "Modem" instead of "Battle.net" (I have not tried any of the other options, but you may want to try them if "Modem" does not work for you)
3. Click cancel, then attempt to connect via Battle.net once more.

HOPEFULLY this works for some of you. It's frustrating when a solution that seems stupid and wouldn't work.. suddenly does work. Even more frustrating is when you try all these weird solutions which don't work for you.
Posted March 08, 2019
avatar
Not5id: HOPEFULLY this works for some of you. It's frustrating when a solution that seems stupid and wouldn't work.. suddenly does work. Even more frustrating is when you try all these weird solutions which don't work for you.
yep,weird but works

thanks
Pages:
1
2
3
4
5
6
This is my favourite topic
Community
DiabloTrouble getting battle.net working(78 posts)(78 posts)
(78 posts)