on 27-03-2012 19h13
Hey, sorry if this is in the wrong place, but I'm new to these forums.
I was wondering if anybody could explain how exactly I'm meant to port forward Minecraft on a BT Home Hub 3, because I really need to get a server set up. I've gone into my router settings through my browser, and I've set up the port for Minecraft (under a new application) which is 25565. Now, this bit I'm fine with, but it's all the IP address that are bound to the port that confuse me. Which IP do I need to put into my server.properties folder? Which IP address do my friends need to connect to? If they can't connect, then what?
I would greatly appreciate it if you could answer this, and I would especially like it if you have successfully set up a Minecraft server in the past without fail. I would also love it if you could make it as clear, and as simple as possible to follow as possible: preferably in step by step instructions. Thanks for the help!
Toshiba Satellite L775-13K
Windows 7 Home Premium
Intel Core i5 Processor
BT Infinity Broadband with BT Home Hub 3
on 27-03-2012 19h34
If you want to allow people to connect, even if your public IP changes, then you will have to sign up for a DDNS account with NO-IP or DynDNS.
on 07-04-2012 15h53
on 13-01-2013 19h14
My son wants to also have Minecraft on our Hub 3, his friends tell him it easy!!
Ready hear do not seem so!
My question is i am new to this port forwarding, is it safe can people access my home net work and take our data etc?
Or is this a case of pc to pc via a IP address and can't access anything else.
Also with this does this slow down my band width?
I have not tried yet to set up the Minecraft, as wanted to make sure it is secure for the rest of the family!
on 14-01-2013 10h38
I host a minecraft server and all you need to-do is portforward the port you've said for UDP and TCP. Then it will just be your IP from www.whatismyip.com
You don't need to put your IP in the server properties as it will be automatically assigned from your network once started. You need to make sure it is hosting from your Hub and not your local LAN connection.
Like 192.xx.xx..xx instead of probably 86.xx.xx.xx
on 29-07-2013 16h16