Posts: 3
Threads: 1
Thanks Received:
0 in 0 posts
Thanks Given: 0
Joined: Jul 2012
Reputation:
0
Hey,
I've noticed a lot of people talking about using hamachi.
Hamachi is a pretty is a pretty bad way to host your server. The best way is to simply portforward and directly host it.
The reason hamachi is not so good is because for people to be able to connect to your hamachi server, they have to download hamachi, install it, make an account then join your hamachi server. It does not only waste someones time, but it also very annoying to do this.
Portforwarding is not hard to do at all.
(Note 1: If you don't have wireless connection you don't need to portforward)
Just follow these steps:
Step 1: Static IP
To portforward, you need a static IP. Usually all routers have dynamic IP, which means the IP constantly changes.
A static IP is just one non-changing IP. You need to do this, otherwise portforwarding won't work.
Okay, first, open up your cmd: (Just open "run" and type "cmd")
Now, type ipconfig/all:
1.
Remember the stuff in the white lines, write them down or leave the cmd open.
2.
Click on the thing in the black lines (Sorry for the Dutch language, but it should still be understandable where to click)
3.
Press this
4.
Right-click your wireless connection, click on properties
5.
Right-click on the thing in the black lines, click on properthis
Now this should pop-up
6.
7.
As I said in the picture, enter all the stuff from the ip/config all. If you notice your internet connection is down, revert it to dynamic ip-address and try it again.
NOTE: At the IP-Address, change the last number to something else
For example, my IP address, as you can see in the picture was 192.168.2.7. If I wanted a static IP-Address, I could change that to 192.168.2.70.
Alright, this was setting up the static-IP. The hardest part is done, now to the easiest part.
-----------------------------------------------------------------------------------------------------------------------------------------------------
Step 2: Portforwarding
Note: For this I will be using my router, fritz.box. This should still give you an idea on how to do it on your own router. If you really can't figure it out, go to google and find out how to do it for your router.
1. Alright, open up cmd. Type ipconfig (NOT ipconfig/all). Look at "Default Gateway" (The last one). Enter that in your URL-bar to connect to your router.
2. You should see your router interface:
Now, as I said before, find out where to click to see the port-forwarding interface (the place where you have to open the ports).
3.
Alright, that was portforwarding in the router. Now the easiest part. Opening it in your firewall. (I am not going to use any pictures for this as it is very easy).
Note: This is for windows firewall. If you are using a specific anti-virus firewall, look up on google how to open ports for your anti-virus firewall.
1. Open control panel
2. Press "System and Security" (The first one, upper left corner).
3. Press "Windows Firewall"
4. Click on "Allow a program through windows firewall".
5. The rest should be self-explanatory. Press on new ports, TCP, enter ports. etc
Alright, this way my tutorial. I hope I helped you guys!
Posts: 154
Threads: 2
Thanks Received:
0 in 0 posts
Thanks Given: 0
Joined: Sep 2011
Reputation:
0
lol can i use my ip as a server OO?
You are wrong, local network addresses are mostly static. And almost never change, only time they do is when the network goes down. Just open 192.168.1.1 or 192.168.0.1 and go to port forwarding, enter your computers IP (ipconfig -> "Ethernet adapter Local Area Connection:" -> "IPv4 Address") and port range 4001-4001, and range 4110-4110.
Posts: 1,163
Threads: 160
Thanks Received:
0 in 0 posts
Thanks Given: 0
Joined: Jun 2011
Reputation:
0
You are wrong, local network addresses are mostly static. And almost never change, only time they do is when the network goes down. Just open 192.168.1.1 or 192.168.0.1 and go to port forwarding, enter your computers IP (ipconfig -> "Ethernet adapter Local Area Connection:" -> "IPv4 Address") and port range 4001-4001, and range 4110-4110.
True but i have 3 pc's 2 xbox's an 2 mobiles plus friends mobiles an laptops that connect to the network.
If say my home pc was 192.168.1.3 but my home pc was off an a friend or mobile connected it could use that local ip if it was the next free ip in line! then i trun my pc on as the local ip is in use my pc would be set a new ip.
I know you know your networking an im not picking just pointing this out. Setting your IPs to set mac address's is always better if your planning to port forward to that lan ip.
For me if i do port forward I always use a bind setting in my router to lock a lan ip to a mac address.
True but i have 3 pc's 2 xbox's an 2 mobiles plus friends mobiles an laptops that connect to the network.
If say my home pc was 192.168.1.3 but my home pc was off an a friend or mobile connected it could use that local ip if it was the next free ip in line! then i trun my pc on as the local ip is in use my pc would be set a new ip.
I know you know your networking an im not picking just pointing this out. Setting your IPs to set mac address's is always better if your planning to port forward to that lan ip.
For me if i do port forward I always use a bind setting in my router to lock a lan ip to a mac address.
The only real benefit of forcing a local IP, is if the network ever does go down (ie lost power). You wouldn't have to change the IP for the ports on the router (which only takes a split second). Forcing your computer to use a specific IP through IPv4 just makes it so your computer is always known as 192.168.1.[CeNsOrEd]. If you don't set these the next time the router reboots itself (loses power), it will re-identify the network. Which could result in a different local IP, computers IP addresses is assigned by the router. Tho like I said, these local IP's are mostly static and never change without a reset. It could prove beneficial if you maybe have a machine that you remote connect to (no monitor, keyboard, mouse). But otherwise if your home loses power, the computer doesn't turn itself back on. The downtime would be the same either way. To sum it up, the only benefit from it is saving the time of going into your router once every few months and changing the IP address in two boxes. I don't see anyone running a server from home any time soon anyhow, it would be best to stick to Hamachi or LanBridger so your home security isn't at risk.
