Starcraft 2 Lan Fix

broken image


It has been known for quite a bit of time that Starcraft II will not be featuring pure Local Area Network multiplayer games, with Blizzard saying that it aims to eliminate LAN play, thus routing. On these trips my brother and I always bring our laptops & such and we are always wanting to play 1v1 against each other or 2v2 with bots on LAN. There is no internet connection aside from our dinky little mobile hotspot which we pay for data usage. It's not an option. How can he and I play Starcraft 2 on an Ad-hoc network we set up? Text Rob Pardo is the VP of Game Design, and he had strong words for LAN play when he spoke with IncGamers. 'We don't have any plans to support LAN,' he told the site, also saying, 'We will not support it.' I assume it will be all Battle.net-based. They're cutting.

Starcraft 2 Lan Fix 1.7

Posted by dOoBiX on April 12th, 2008 at 2:29 pm | 16,541 views

Starcraft 2 Lan Fix Download

If you are behind a router/gateway with another computer and you tried playing StarCraft together with other people on Battle.net, you might have noticed that it was really laggy and unplayable. To fix this problem, all you have to do is change the ports for one of the computers on your network. The default port for Battle.net is 6112 and it lags because it can't handle more than one computer in that port.

So all you have to do is go to your router/gateway's Port Forward page and set one of your computers to use a port between 6113 and 6119 (UDP, not TCP). After you forward a port for one of your computers, you need to open the Registry Editor for that computer. To do this, click Start, Run, and press enter after you type regedit. In the left side of the registry editor, navigate to HKEY_CURRENT_USERSoftwareBattle.netConfiguration. Now click Edit > New DWORD Value, and name it Game Data Port. Double click that value that you've just created, click Decimal in the Base area, and type the port that you forwarded for your computer in ‘Value data' (6114 for example), and press OK.

Your computers sharing the same router/gateway should now be able to play on Battle.net with other people with no lag!

Description of the Problem:
You host a Warcraft II game but your friends can't join because they receive a 'Latency is too high' message. This happens because your router is blocking traffic for port 6112, which is what WC2 uses.

To fix the latency issue that prevents people from joining your games you will need to forward port 6112 in your router configuration page.

Note: These instructions will help only if you receive this message when you try to host, i.e. if NOBODY can join your game. Connection problems affecting individual users are not covered by this solution.

War2Combat v4 and newer now supports UPnP (universal plug and play) for automatic port forwarding. If games you host have high latency and you aren't using the latest version of War2Combat it's recommended to install it and see if that fixes the problem.
A note about 'Real' IP:
All these instructions will be applied to you ONLY if your ISP (Internet service provider)
Lan
provides a REAL IP for you. Otherwise this article will be for you and you should either change your ISP or take some additional services like external VPN service. Also note that REAL is not the same as STATIC. Your IP can be dynamic, but still real.

The easiest way to check if your IP is real is to compare: Terraria full version apk 2018.

  • the external IP in your router admin panel status
  • and the IP given by any site showing your public IP address.

Also read this forum thread about real IP.

This port forwarding guide will only help when your ISP provides real IP for you and you have your own router used for Internet connection.

iL

Step 1

If you don't know your router information, start here:

  1. Navigate to Start Menu > All Programs > Accessories > Command Prompt
    • Alternatively, you can navigate to Start Menu > Run and type in 'cmd' (without quotes)
  2. In the black window that pops up type 'ipconfig' (without quotes) and press enter.
  3. Make a note of the number beside 'IPv4 Address' and the one beside 'Default Gateway' — you'll need them later.


Note by iL:
Proper local IP address should begin with '192.168.' or '10.' or '172.16.'. Default Gateway for most routers will be 192.168.0.1 or 192.168.1.1 if you didn't change it during the first configuration.

Step 2

  1. Go to your Internet browser and type the number that was beside Default Gateway into the address bar, e.g. http://192.168.0.1
  2. This will take you to a login page where you must enter your router's username and password. The default username and password combos are usually:
    • Username: 'admin', Password 'admin'
    • Username: 'admin', Password: 'password'
    • Username: 'admin', Password: [leave blank]
    • Username: [leave blank], Password: 'password'
  3. If none of these combinations work you can check this website for the default information used by your make & model of router, or look on the side of your router or in the instruction manual. If the default password has been changed to something unknown you can reset the router to factory default settings by pressing the small 'reset' button on the side/back/bottom of the router with a paperclip and holding it until the lights flash (usually for around 30-60 seconds).

Once you have all the necessary information and can successfully login to your router, follow the rest of the steps below.

Step 3

Note: The following instructions are generic. Your router interface may not look exactly like the screenshots below (Step 4) but it should be similar. The idea is to look through the settings pages and locate the section that handles 'Port Forwarding' — once you've found that it'll be easy to figure out what information goes where based on this guide.

You can also get specific instructions for your make & model of router on portforward.com.

After logging in find the section in your router settings that deals with port forwarding. The location of this will vary depending on your make & model of router, but you're looking for a section labeled 'Port Forwarding', or sometimes just 'Fowarding'. It could be located under any of the following categories:

  • Advanced
  • Virtual Servers
  • Security
  • NAT

Step 4

Once you find the page for port forwarding you will see a table with several different fields for you to fill out. Generally, only one entry is needed for port 6112 (enter '6112' in both the Start and End fields) however a range can be used as well (e.g. 6112 – 6119). If there's only one field for the port (no start/end) that's fine too.

The screenshot below is taken from a Linksys router but you should see a similar table no matter what router you're using: Bd player program.

Explanation of columns, from left to right:

  • Application: the name of the program you're forwarding the ports for. This can be anything you want, it's just for your reference. (Don't worry if your router doesn't have this field.)
  • Start: if you're forwarding a range of ports this will be the lower number. In our case it is 6112
  • End: if you're forwarding a range of ports this will be the higher number. In our case it is also 6112
  • Protocol: If possible set this to 'Both'. If 'Both' isn't an option you will need to create two separate entries in the table. They should be identical, but one should be for the 'TCP' protocol and one for the 'UDP' protocol.
  • IP Address: this is the IPv4 address you wrote down from ipconfig in Step 1, you usually only have to enter the digit(s) that are after the final period.
    IMPORTANT:
    Make SURE you use the IPv4 address you wrote down from Step 1. DO NOT use the same address used to access your router!
  • Enable: this box needs to be checked in order for your settings to take effect, otherwise they'll be saved to the table but not activated.

When you've finished entering the settings make sure you click on the 'Save' or 'Apply' button (or equivalent) located at the bottom of the page, otherwise your entries will be lost. Once the page reloads and you confirm your new port forwarding entry is saved, that's it! You should now be able to host.

Starcraft 2 Download Size

When you click on 'Save' some routers might take a long time to apply the changes. Your Internet connection may even get briefly interrupted – don't worry! It's normal and should resolve itself very quickly.


And… that's it! Now GO HOST!

Troubleshooting

Still can't host? Try following these additional steps.

Firewall

War2Combat configures windows firewall automatically. There's no reason to do that yourself if you install Combat.

Sometimes your firewall can accidentally get configured to block incoming connections from Warcraft II — this will prevent you from hosting even if your ports are forwarded. Follow this step-by-step guide to check your firewall settings.

Game Data Port

This guide only works if Warcraft II is set up to use port 6112, but sometimes it can become set to a different port. Follow these steps to make sure it's actually using 6112 so your port forwarding settings can take effect.

  1. The easiest way to do this is to rerun the War2Combat installer (download here) and make sure the 'default port' option is selected. (You don't have to uninstall it first, just make sure War2 isn't running.)
  2. Another way is to manually set your game data port in the registry — click here for a step-by-step guide.

Port 1024

Sometimes after you forward port 6112 your will receive a message when you host saying that port 1024 is blocked now. If you've already followed the steps above to check your firewall & game data port then there are a few more things you can try.

  1. Reinstall War2Combat. Grab the latest version from our home page and rerun the installer. (No need to uninstall the current version first. If you have custom options set, e.g. to include the singleplayer campaigns or the black to pink patch, make sure to select them again.) The first time you run War2 after reinstalling you should receive a prompt asking to update, click 'Yes' and War2 should open in a few seconds. If it doesn't then right click on the icon and select 'Run as administrator' and try updating again.
  2. Forward port 1024. If reinstalling doesn't work then repeat the steps in this guide to forward port 1024 in your router. (Don't delete the entry you made for 6112, just forward both.) This will usually work if you were previously able to host after forwarding port 6112, then some time later started getting the message about port 1024.

Alternate Method – DMZ

This method is optional and not needed if you followed Steps 1 – 4 to forward your ports. Port forwarding is the better option and should fix hosting for most people, but if it doesn't work you can try enabling DMZ (if your router supports it). DMZ essentially means you forward all the router ports into your local computer behind the router — it's less secure, so it's better to try port forwarding (above) first.

  1. Follow Steps 1 – 2 above for accessing your router.
  2. Find the setting for DMZ in your router, click enable, and then finish filling in the IP (the same one you used before). When you're done click on 'Save settings' or the equivalent.


Note by iL:
Also note that if your local computer uses IP address assigned automatically by DHCP, that means its IP address could be changed from time to time. Then your ports (or DMZ) will be forwarded to the wrong IP address and become broken. Possible solutions are to either to assign static internal IP for your computer (that mean static external IP given by ISP) OR to configure your DHCP to fixed IP attached by MAC address.




broken image