|
-
Tiger Shark
In order to connect to Battle.net, connect to others over a Local Area Network, and allow others to connect to you using any Blizzard Entertainment game, the following ports need to be opened:
4000 UDP
4000 TCP
6112 up to 6119 UDP
6112 up to 6119 TCP
Some firewall programs have preset ports available in their configurations that are often necessary to be open. One in particular is a connection to your DNS server. This usually takes place on UDP port 53. If you are playing over a Local Area Network and using a firewall you will need to open port 6111 for UDP and TCP.
As for inbound and outbound or internal and external, I would think they mean that inbound(internal) are the frames/packets that are going to your computer, and outbound (external) are the frames/packets that are leaving your computer and going to theirs.
As for forwarding ports, try multiple methods to open them, and try hosting a game of either Starcraft/Diablo2 on OPEN Battle.net/or Warcraft III <---War3 has been experiencing connectivity issues on their BETA (repeat, BETA) server
I say use Diablo 2 on OPEN Battle.net, not the realms, to test your hosting/port opening skills, I find that the best game to use for that reason. If you dont have it, try Starcraft or Diablo 1, at all costs try using Warcraft III beta to test your hosting skills LAST, as the game is still in beta.
Your not the only one with this problem.
MAKE SURE..... when you are opening those ports, that you are assigning the ports to a STATIC IP adress, and not a dynamic IP adress.
By the way, here is a list for ALL ports to open for more games than just Blizzard games...
http://www.practicallynetworked.com/..._port_list.htm
Last edited by Snipe7; 06-16-2002 at 05:26 PM.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|