|
10387 Posts
One of the biggest barriers Brood War faces is the notorious port forwarding issue that plagues almost everyone. There are various guides and tips out there, but information is scattered and results seem to be mixed at best. This thread is to consolidate that info, and to help encourage anyone having issues to come ask for help in this thread.
BW is still playable w/o port forwarding, but it's a proven fact that your enjoyment of BW quintiples once you successfully configure your ports. So don't be afraid, ask your question! And feel free to make any suggestions to the Resources/Tips section
How I want this thread to work: First, look at the Port Forward Resources/Tips section below to see if any of that will fix your problem. Then, if you still have trouble or have problem understanding some of the steps, post about your issue here. Given some time, some kind, tech-savvy soul/s will help solve the issue  . (like the SQSA thread in the Strategy forum). Simple! (maybe)
To get started, here's a possible example of how to ask:
Router: Netgear
Problem: Can't join games or host, or I don't know what this one step in the guide means, etc etc.
<insert screenshots of relevant information such as the Router port forward page inside a spoiler tag>
Port Forward Resources/Tips
- Liquipedia has a general Port Forwarding guide.
- Portforward.com has a more specific router-based guide.
- Make sure you allow Starcraft in your firewalls and anti-virus programs.
- To forward ports for multiple computers on the same router, or to play online with a friend against others through the same router, follow this Game Data Port guide.
Discussion
On January 14 2013 12:39 R1CH wrote:
I'm very surprised iccup hasn't added upnp support to their launcher yet. 99% of routers could be automatically configured via upnp, it would save so many headaches.
Someone relay the message, to all current launcher developers (iCCup, wLauncher, MINI)
On that subject, LegendaryDreams has posted his own method of port forwarding via the a UPnP Wizard. Could someone verify the reliability of this method?
|
|
|
I've been an admin at iCCup for a few weeks now and I've been port forwarding for people through Teamviewer and here are some stuff that I've seen:
•Port Forwarding and Port Range Forwarding are NOT the same thing, having both on at the same time will conflict and cause port forwarding to fail.
•DMZ is NOT recommended because it opens ALL of your ports.
•Datasian(a blizzard employee) created a program that can forward your ports via UPNP(http://datasian.homeserver.com/web/toolbox/portfwd.php), I've been using it in many cases however sometimes it can't open ports, probably because UPNP implementation in routers aren't the same(<--just a guess).
•It's possible that Windows Firewall may be blocking Starcraft, delete all of your Starcraft rules in Windows Firewall and run Starcraft, alt+tab out and check if there's an error message asking to keep blocking or unblock Starcraft.
•The internal ip address is not your public ip address that you find on websites like whatsmyip.org, go to your command prompt and type ipconfig and look for your ipv4 address
•For some odd reason, your UDP port for Starcraft is not a standard port(6112-6119), you can check by logging onto iCCup and type /netinfo. Look for a line that says Client UDP, the first numbers are your public ip address and the number after the colon is the port that Starcraft is set to. Reset your ports if it isn't within the 6112-6119 range, https://sites.google.com/site/maged123/ports
Note: There are cases where everything seems to be correct however not working, unfortunately, my only suggestion is to buy a new router or use a custom firmware like ddwrt.
If you are having trouble port forwarding, I can do it for you via Teamviewer, just PM me your iCCup username and I'll try to contact you when I'm online.
|
Generally those tools test TCP connections, which is not all that helpful in determining if you've forwarded ports for BW correctly (which uses UDP for client-client connections like games)
On February 02 2013 12:54 xboi209 wrote:I've been an admin at iCCup for a few weeks now and I've been port forwarding for people through Teamviewer and here are some stuff that I've seen: •Port Forwarding and Port Range Forwarding are NOT the same thing, having both on at the same time will conflict and cause port forwarding to fail. •DMZ is NOT recommended because it opens ALL of your ports. •Datasian(a blizzard employee) created a program that can forward your ports via UPNP(http://datasian.homeserver.com/web/toolbox/portfwd.php), I've been using it in many cases however sometimes it can't open ports, probably because UPNP implementation in routers aren't the same(<--just a guess). •It's possible that Windows Firewall may be blocking Starcraft, delete all of your Starcraft rules in Windows Firewall and run Starcraft, alt+tab out and check if there's an error message asking to keep blocking or unblock Starcraft. •The internal ip address is not your public ip address that you find on websites like whatsmyip.org, go to your command prompt and type ipconfig and look for your ipv4 address •For some odd reason, your UDP port for Starcraft is not a standard port(6112-6119), you can check by logging onto iCCup and type /netinfo. Look for a line that says Client UDP, the first numbers are your public ip address and the number after the colon is the port that Starcraft is set to. Reset your ports if it isn't within the 6112-6119 range, https://sites.google.com/site/maged123/portsNote: There are cases where everything seems to be correct however not working, unfortunately, my only suggestion is to buy a new router or use a custom firmware like ddwrt. If you are having trouble port forwarding, I can do it for you via Teamviewer, just PM me your iCCup username and I'll try to contact you when I'm online.
Most of these are decent suggestions, but I really doubt the last one will ever solve anyone's issues. To get outside of the 6112-6119 range, you'd have to either A) be using all of those ports for other things (unlikely), or B) have specified a port outside of that range in the registry (also unlikely, given most people don't know that setting exists). But I suppose those registry entries are helpful if you have multiple computers trying to play from the same network.
|
|
|
On February 02 2013 15:53 tec27 wrote:Generally those tools test TCP connections, which is not all that helpful in determining if you've forwarded ports for BW correctly (which uses UDP for client-client connections like games) Show nested quote +On February 02 2013 12:54 xboi209 wrote:I've been an admin at iCCup for a few weeks now and I've been port forwarding for people through Teamviewer and here are some stuff that I've seen: •Port Forwarding and Port Range Forwarding are NOT the same thing, having both on at the same time will conflict and cause port forwarding to fail. •DMZ is NOT recommended because it opens ALL of your ports. •Datasian(a blizzard employee) created a program that can forward your ports via UPNP(http://datasian.homeserver.com/web/toolbox/portfwd.php), I've been using it in many cases however sometimes it can't open ports, probably because UPNP implementation in routers aren't the same(<--just a guess). •It's possible that Windows Firewall may be blocking Starcraft, delete all of your Starcraft rules in Windows Firewall and run Starcraft, alt+tab out and check if there's an error message asking to keep blocking or unblock Starcraft. •The internal ip address is not your public ip address that you find on websites like whatsmyip.org, go to your command prompt and type ipconfig and look for your ipv4 address •For some odd reason, your UDP port for Starcraft is not a standard port(6112-6119), you can check by logging onto iCCup and type /netinfo. Look for a line that says Client UDP, the first numbers are your public ip address and the number after the colon is the port that Starcraft is set to. Reset your ports if it isn't within the 6112-6119 range, https://sites.google.com/site/maged123/portsNote: There are cases where everything seems to be correct however not working, unfortunately, my only suggestion is to buy a new router or use a custom firmware like ddwrt. If you are having trouble port forwarding, I can do it for you via Teamviewer, just PM me your iCCup username and I'll try to contact you when I'm online. Most of these are decent suggestions, but I really doubt the last one will ever solve anyone's issues. To get outside of the 6112-6119 range, you'd have to either A) be using all of those ports for other things (unlikely), or B) have specified a port outside of that range in the registry (also unlikely, given most people don't know that setting exists). But I suppose those registry entries are helpful if you have multiple computers trying to play from the same network.
Trust me, I've helped maybe 10+ people port forward their routers so far and maybe a quarter of them has their port set outside of the 6112-6119 range for unknown reasons. It's highly unlikely that another program was already using it and it's also highly unlikely that they've manually set it via the registry.
|
Croatia9565 Posts
Maybe they've changed it in Chaoslauncher's settings although I see that as highly unlikely as well.
|
No I'm sure they didn't change it, every guide that shows you how to change your ports only say to change it between 6112-6119 with a scary warning that tells you that you will utterly screw up your computer if you mess around in the registry. Plus, almost no one on iCCup uses chaoslauncher for antihack anyways.
|
Norway28908 Posts
xboi is an absolute hero at this, I'd trust anything he says on this issue as absolute truth. and if he ever offers to help you out, take up on his offer.
|
On February 03 2013 02:14 xboi209 wrote:Show nested quote +On February 02 2013 15:53 tec27 wrote:Generally those tools test TCP connections, which is not all that helpful in determining if you've forwarded ports for BW correctly (which uses UDP for client-client connections like games) On February 02 2013 12:54 xboi209 wrote:I've been an admin at iCCup for a few weeks now and I've been port forwarding for people through Teamviewer and here are some stuff that I've seen: •Port Forwarding and Port Range Forwarding are NOT the same thing, having both on at the same time will conflict and cause port forwarding to fail. •DMZ is NOT recommended because it opens ALL of your ports. •Datasian(a blizzard employee) created a program that can forward your ports via UPNP(http://datasian.homeserver.com/web/toolbox/portfwd.php), I've been using it in many cases however sometimes it can't open ports, probably because UPNP implementation in routers aren't the same(<--just a guess). •It's possible that Windows Firewall may be blocking Starcraft, delete all of your Starcraft rules in Windows Firewall and run Starcraft, alt+tab out and check if there's an error message asking to keep blocking or unblock Starcraft. •The internal ip address is not your public ip address that you find on websites like whatsmyip.org, go to your command prompt and type ipconfig and look for your ipv4 address •For some odd reason, your UDP port for Starcraft is not a standard port(6112-6119), you can check by logging onto iCCup and type /netinfo. Look for a line that says Client UDP, the first numbers are your public ip address and the number after the colon is the port that Starcraft is set to. Reset your ports if it isn't within the 6112-6119 range, https://sites.google.com/site/maged123/portsNote: There are cases where everything seems to be correct however not working, unfortunately, my only suggestion is to buy a new router or use a custom firmware like ddwrt. If you are having trouble port forwarding, I can do it for you via Teamviewer, just PM me your iCCup username and I'll try to contact you when I'm online. Most of these are decent suggestions, but I really doubt the last one will ever solve anyone's issues. To get outside of the 6112-6119 range, you'd have to either A) be using all of those ports for other things (unlikely), or B) have specified a port outside of that range in the registry (also unlikely, given most people don't know that setting exists). But I suppose those registry entries are helpful if you have multiple computers trying to play from the same network. Trust me, I've helped maybe 10+ people port forward their routers so far and maybe a quarter of them has their port set outside of the 6112-6119 range for unknown reasons. It's highly unlikely that another program was already using it and it's also highly unlikely that they've manually set it via the registry.
There's no other way it can happen. I just looked at the assembly of the code that picks a port last night. It starts at the port specified in the registry (defaulting to 6112 if there isn't one specified). It then tries every port until it finds one that works, up to 100 ports above at which point it fails. Note that routers don't have to use the same port that the computer is using, they can reassign it. At that point though, assigning a different port locally doesn't do anything differently.
|
Is it possible to do this with college dorm internet? I'm a total newbie at this.
|
On February 03 2013 05:35 tec27 wrote:Show nested quote +On February 03 2013 02:14 xboi209 wrote:On February 02 2013 15:53 tec27 wrote:Generally those tools test TCP connections, which is not all that helpful in determining if you've forwarded ports for BW correctly (which uses UDP for client-client connections like games) On February 02 2013 12:54 xboi209 wrote:I've been an admin at iCCup for a few weeks now and I've been port forwarding for people through Teamviewer and here are some stuff that I've seen: •Port Forwarding and Port Range Forwarding are NOT the same thing, having both on at the same time will conflict and cause port forwarding to fail. •DMZ is NOT recommended because it opens ALL of your ports. •Datasian(a blizzard employee) created a program that can forward your ports via UPNP(http://datasian.homeserver.com/web/toolbox/portfwd.php), I've been using it in many cases however sometimes it can't open ports, probably because UPNP implementation in routers aren't the same(<--just a guess). •It's possible that Windows Firewall may be blocking Starcraft, delete all of your Starcraft rules in Windows Firewall and run Starcraft, alt+tab out and check if there's an error message asking to keep blocking or unblock Starcraft. •The internal ip address is not your public ip address that you find on websites like whatsmyip.org, go to your command prompt and type ipconfig and look for your ipv4 address •For some odd reason, your UDP port for Starcraft is not a standard port(6112-6119), you can check by logging onto iCCup and type /netinfo. Look for a line that says Client UDP, the first numbers are your public ip address and the number after the colon is the port that Starcraft is set to. Reset your ports if it isn't within the 6112-6119 range, https://sites.google.com/site/maged123/portsNote: There are cases where everything seems to be correct however not working, unfortunately, my only suggestion is to buy a new router or use a custom firmware like ddwrt. If you are having trouble port forwarding, I can do it for you via Teamviewer, just PM me your iCCup username and I'll try to contact you when I'm online. Most of these are decent suggestions, but I really doubt the last one will ever solve anyone's issues. To get outside of the 6112-6119 range, you'd have to either A) be using all of those ports for other things (unlikely), or B) have specified a port outside of that range in the registry (also unlikely, given most people don't know that setting exists). But I suppose those registry entries are helpful if you have multiple computers trying to play from the same network. Trust me, I've helped maybe 10+ people port forward their routers so far and maybe a quarter of them has their port set outside of the 6112-6119 range for unknown reasons. It's highly unlikely that another program was already using it and it's also highly unlikely that they've manually set it via the registry. There's no other way it can happen. I just looked at the assembly of the code that picks a port last night. It starts at the port specified in the registry (defaulting to 6112 if there isn't one specified). It then tries every port until it finds one that works, up to 100 ports above at which point it fails. Note that routers don't have to use the same port that the computer is using, they can reassign it. At that point though, assigning a different port locally doesn't do anything differently.
Well you wanna start an investigation? Just go around iccup and /netstat people, if someone doesn't have their port set to 6112-6119, ask them if they even bothered changing ports before. The answer is most likely no
Also, while the port may be completely random, there are other times where it's one port above or below the the tcp port which may suggest that the router is reassigning the port. But even if the router is reassigning the port, you should still reset your port within the 6112-6119 range.
|
I agree that its unlikely that they're setting the port, that's why I said that in my original post. My point is that telling them to set their port is at best useless because the router will re-assign it either way. The router has no knowledge that you've specified a registry key that only BW cares about. On top of this, you're causing possible future harm because people that gain the ability to forward their ports might only forward 6112, and you've previously told them to change their port to something else.
|
i've actually had a lot of problems hosting games even after i have done port forwarding and after doing some google searches, it appeared that me lacking a static ip was causing all the problems. so i created a static ip by following instructions from a website and changed the ip thingy in my router website and viola. i could host games not just on iccup but on garena which i use to play dota on as well.
|
On February 03 2013 06:14 TBone- wrote:
Is it possible to do this with college dorm internet? I'm a total newbie at this.
If you have access to your Router and your internal IP address then you can do it. To access your router type in your browser 192.168.0.1 . Aldo if the router is of the uni they probably have a password.Its not that hard at all you just need the corrent information before starting
|
Oh man is this thread needed! Thanks!
|
On February 03 2013 09:50 tec27 wrote:
I agree that its unlikely that they're setting the port, that's why I said that in my original post. My point is that telling them to set their port is at best useless because the router will re-assign it either way. The router has no knowledge that you've specified a registry key that only BW cares about. On top of this, you're causing possible future harm because people that gain the ability to forward their ports might only forward 6112, and you've previously told them to change their port to something else.
Well when does the port get reassigned? I've resetted people's ports and it stayed that way so if the router doesn't reassign the port often, then it isn't useless at all to reset the port.
Also, I don't understand how I'm causing possible future harm when I'm the one port forwarding for other people. If I ever tell someone to set their port to within 6113-6119, I also tell them to port forward 6112-6119 as well.
|
The port gets reassigned for a number of reasons, depending heavily on the network setup your dealing with. For consumer routers, you're mostly dealing with cases where another computer (or port forwarding settings) have already "claimed" the port when its used, so the router moves your packets to a different one so that it can know where to route them properly. For network components in larger networks, sometimes you'll see devices that always randomize the outside ports, for security and other concerns.
For an example of this happening on your own, you can forward 6112 to a different IP, set your port to 6112 and connect to ICCup. You'll very likely see your port getting randomized to something different than 6112, despite your client thinking its on 6112.
For local networks, this setting should be unnecessary UNLESS you have multiple computers on the same network running BW. In those cases, you should each pick a separate game data port and forward that port to the respective computer. That is the one major case where this setting is useful.
For school, corporate, and other large networks, this setting can be useful as well, but I don't know why the hell you would set it within the 6112-6119 range. This range is a fabrication of someone's imagination, the game itself doesn't care what the port number is. Its a range that somewhat makes sense for configuring a network for playing Battle.net with lan players ( there are 8 ports in that range and 8 players in a game) but past that its a really bad idea to limit yourself to it (and has no basis in the code of the game). In a place where you have no idea how many other people are trying to play BW (or other battle.net games) or even if this is why your port is being moved, it just makes you more likely to have your port reassigned anyway. Picking a completely random port would give you higher odds of not colliding with someone else on the network and being reassigned.
|
Good, this thread should not only help me with BW but also WC3!
|
On February 03 2013 17:10 tec27 wrote:
The port gets reassigned for a number of reasons, depending heavily on the network setup your dealing with. For consumer routers, you're mostly dealing with cases where another computer (or port forwarding settings) have already "claimed" the port when its used, so the router moves your packets to a different one so that it can know where to route them properly. For network components in larger networks, sometimes you'll see devices that always randomize the outside ports, for security and other concerns.
So if a port is already taken by another computer, why would setting the port back to 6112 work after using the .reg?
On February 03 2013 17:10 tec27 wrote:
For an example of this happening on your own, you can forward 6112 to a different IP, set your port to 6112 and connect to ICCup. You'll very likely see your port getting randomized to something different than 6112, despite your client thinking its on 6112.
Tried this, didn't work for me.
On February 03 2013 17:10 tec27 wrote:
For local networks, this setting should be unnecessary UNLESS you have multiple computers on the same network running BW. In those cases, you should each pick a separate game data port and forward that port to the respective computer. That is the one major case where this setting is useful.
Well I tried port forwarding someone before and they couldn't host until I set the port to 6112 so I find this kind of necessary.
On February 03 2013 17:10 tec27 wrote:
For school, corporate, and other large networks, this setting can be useful as well, but I don't know why the hell you would set it within the 6112-6119 range. This range is a fabrication of someone's imagination, the game itself doesn't care what the port number is. Its a range that somewhat makes sense for configuring a network for playing Battle.net with lan players ( there are 8 ports in that range and 8 players in a game) but past that its a really bad idea to limit yourself to it (and has no basis in the code of the game). In a place where you have no idea how many other people are trying to play BW (or other battle.net games) or even if this is why your port is being moved, it just makes you more likely to have your port reassigned anyway. Picking a completely random port would give you higher odds of not colliding with someone else on the network and being reassigned.
School, corporate, and large networks are often the networks where you don't get access to the router to port forward so trying to host at all is pointless. If you're on a private network, it's most likely small so you can just go up the ladder and try until you find a port that works.
|
|
|
|
|
|
EPT
