|
As the title says, does anyone know how to do it?
I used guides on YouTube/Portforward.com but it still doesn't work.
I am unsure of what I did wrong. I opened ports for both TCP/UDP from 6112 to 6112. Does anyone know a decent guide or have first hand experience on port forwarding Starcraft after they switched/got Fios? Please share your secrets!
|
Belgium9942 Posts
|
I just put myself on the DMZ.
|
On October 18 2009 03:18 RaGe wrote: 6112 to 6118 6112 to 6119
|
On October 18 2009 04:18 JadeFist wrote:6112 to 6119
and on YOUR ip adress obviously
|
|
On October 18 2009 04:10 Jadyks wrote: I just put myself on the DMZ.
The DMZ is usually not a good solution, since it has many potential security risks. It works, since what it does is forwarding ALL the ports to your computer. You really should put a little more effort into it, and just forward the required ports. (if your reason for chosing DMZ was not finding a port forwarding option on the router, try searching for "virtual server")
|
Still doesn't work. I don't know where the error is. Nitrogen I checked for 6112 and 6119 and it says my ports are open. I still can't host games though...
|
United States4126 Posts
Does your router/computer have a firewall on?
|
On October 18 2009 05:33 Amnesia wrote: Still doesn't work. I don't know where the error is. Nitrogen I checked for 6112 and 6119 and it says my ports are open. I still can't host games though... You need all the ports between 6112 and 6119. (I guess you know, but still, this might be an error) + Show Spoiler +6112,6113,6114,6115,6116,6117,6118 and 6119
Also, make sure you forward them for both TCP and UTP in and out. (in some routers this is just listed as "BOTH".)
|
As stated above, it isn't recommended to set a computer to DMZ. This is typically OK for your Xbox 360's, PS3's and handhelds but poses a security risk in regards to PCs and Servers where you may not want all ports accessible & open to communication from the outside world.
Assuming you're on Windows, you want to get into the Command Prompt (Start->Run->cmd) and issue the command: ipconfig (type "ipconfig" without quotes and hit enter). If you're on *nix the command is "ip addr" without quotes.
Look for either "Ethernet adapter Local Area Connection" or "Ethernet adapter Wireless Network Connection" depending on whether you're using a wired or wireless connection. You'll see something along the lines of "IP Address . . . . . 192.168.x.y" That is the internal address for your computer as assigned by the router/DHCP. When you go to the Port Forwarding menu inside of your router's configuration/webui you want to specify the address of your computer, the port range you need to forward (6112-6119) and check the little Enable box next to the entry if there is one there. After saving the settings everything should be in order.
Something you may want to consider in the future is disabling DHCP, which handles automatically assigning IP addresses to devices that connect to your network. This will require you to specify all the connection details on each machine and give them all their own static internal IP's. The benefit of this is that DHCP will no longer automatically assign an IP to a device each and every time it connects to the network.
To try and put it in perspective: You just finished forwarding ports 6112-6119 to 192.168.1.152 (for example we're assuming your computer was 152 at the time). It works great all night and then you shut down the computer. Some time over night somebody else decides to hop on the WiFi with their laptop or iPod or whatever. Your computer is off and no longer using 152 so it is considered free to be assigned to whatever machine connects to the router next. DHCP happens to automatically assign it to their their laptop/ipod/whatever. This makes their device 152 (at least until they shut it down) and thus the forwards are now going to their machine. If they never shut down they maintain that IP and when you boot up in the morning DHCP is going to gives you the next available IP address of 153. Of course you set your forward up to go to 152 the night before (and it is going there) but you're no longer 152 so the forward no longer works for your machine.
DHCP isn't hard to disable on the router nor is it hard to assign static IPs to you devices but I'm running low on time and will have to explain the process in more detail when I get to work. I have to be there in an hour so I'm gonna go get cleaned up and then I'll be back online. I'll make some screencaps when I get there and revise this response. Don't disable DHCP yet since you'll probably cut yourself off from the net in doing so (most likely no computer on you network is properly configured to handle being without DHCP yet) but feel free to respond with your router's make/model # (example: Linksys WRT54G, Belkin ME-1004R, etc) and I'll get back to you when I get to work on how to get it all configured.
|
United States1654 Posts
I had the same problem with FIOS. It wouldn't work for me when I opened only 6112-6119, so instead I had to open TCP and UDP ports from "any" port to destination ports of range 6112-6119, which ended up working for me.
|
FIOS has a port forwarding application when you go into change the router settings...all you do is select starcraft from the list of applications.
|
I'm at work and I've assembled a few screencaps and descriptions detailing how to find your gateway (router) IP, DNS servers, computer IP, etc as well as how to set your computer (or others on your network) to have a Static (unchanging) internal IP (meaning it'll always be 192.168.1.150 if you set it as such). I'm only missing a Make/Model for your Router so I can make some images specific to what you will see on your screen.
On October 18 2009 06:33 Coca Cola Classic wrote: FIOS has a port forwarding application when you go into change the router settings...all you do is select starcraft from the list of applications.
This is a possibility but I'm unfamiliar with what applications Verizon ships on their software CDs. I've always opted not to install any software provided by my ISP or included with things such as WiFi adapters because they are typically unnecessary, save for the drivers for the devices.
|
This guide is going to be specific to most Linksys brand routers and the changes are being made using Windows XP however he concepts will remain the same regardless of Make / Model of the router or the Operating System of the user.
Start by going to the Start Menu and opening the Run Dialog. Run "cmd" to open the command prompt.
With the command prompt open, type ipconfig and hit enter. You will see results similar to the ones pictured below.
The IP Address is the IP currently assigned to the computer you are using. The Default Gateway is the IP address of your router (the address you use to access the router's WebUI - http://192.168.1.1/ is the Linksys default). Write both of these down as well as your subnet mask (which is usually 255.255.255.0 by default).
Log in to your Router's WebUI and under Applications & Gaming in the Port Range Forwarding sub-menu add an entry for Starcraft. Name it Starcraft, specify the range (6112-6119), and point it to the IP Address of your computer that you retrieved a moment ago. Check the box to enable the forwarding.
Under your router's status page you'll find information such as the gateway your router answers to at your ISP. The only information we require from here are the DNS servers that are listed. Write these down.
Now we have our IP, Router IP (Gateway Address), Subnet & two or three DNS servers. We can safely disable DHCP and configure the devices on the network to use static (unchanging) IP addresses. Disabling DHCP will ensure that any time your computer connects to router it will always maintain the same network IP Address and the port range forward created earlier will always point to the same machine.
Make sure you are disabling Network DHCP and not Internet DHCP. Internet DHCP is how your router automatically obtains it's connection information from your ISP. The Network DHCP is how your router automatically assigns addresses amongst the devices on your network.
Pull up your connection status by right-clicking on the icon in your taskbar and choosing Status. The icon is usually two blinking monitors for a wired connection or a WiFi/Signal Strength icon if you're on wireless. With the status menu visible click on Properties.
In the dialog that pops up scroll down and click on Internet Protocol (TCP/IP) and click Properties.
Now we can enter all the information we've written down. Check the two radio buttons to "Use the following..." and enter the data we've written down. IP Address is the IP you want your computer to always have. You want it to be the same IP you set the forwards up for. The subnet mask is the subnet your wrote down and the default gateway is the IP of your router. Fill the two DNS boxes with two of the DNS servers you pulled from the router's status page.
Save the settings and you're good to go. Because DHCP is no longer working you will also have to repeat the last few steps for every device on your network, giving each one its own unique IP Address (the other stuff like the gateway, subnet and DNS will be the same). You may also want to write down what IPs you have assigned to each computer just in case you need to set up forwards for programs on the other machines in the future. It's always good to know what IP relates to what machine on your network (something that is very difficult to achieve when using DHCP).
192.168.1.150 - Gaming PC 192.168.1.151 - Mom's Computer 192.168.1.152 - Linux Seedbox etc etc etc
Again, by disabling DHCP on the router and assigning each computer its own IP you ensure that whatever forwards you create for any of the machines always go to the intended machine. DHCP won't give you 150 one day and then 158 the next time you turn on your computer.
If you get back to me with the Make / Model of your router I'll attempt to arrange a series of screenshots for that router's WebUI should you have any troubles adapting this guide to your own hardware.
Hope this has helped, Lokomis
|
Lokomis, thanks for that guide. You mention: "Because DHCP is no longer working you will also have to repeat the last few steps for every device on your network, giving each one its own unique IP Address (the other stuff like the gateway, subnet and DNS will be the same)."
Is it possible to fix the IP address of just one PC on the network and have the others as floating?
|
On October 18 2009 13:31 ThunderGod wrote: Lokomis, thanks for that guide. You mention: "Because DHCP is no longer working you will also have to repeat the last few steps for every device on your network, giving each one its own unique IP Address (the other stuff like the gateway, subnet and DNS will be the same)."
Is it possible to fix the IP address of just one PC on the network and have the others as floating?
Yes, it is possible. Fix your IP address (the way shown before) to an IP address outside of the DHCP server's range, and leave the DHCP server turned on. (so for example you set yours to be 192.168.1.100, and you set the dhcp to use the interval 192.168.1.101-199) Also, in some rare occasions this might solve the hosting problems, because there are supposedly a few routers that cant forward ports correctly within DHCP range.
|
|
|
|