Horizon - Port Forwarding

Wan port reflection doesnt work but if you use something like dyndns I wonder if you can add a hosts entry on the horizon box pointing to the local Ip address so when you're on the internal network the name resolves to the internal address and not the external address.

Postie, if you just use the ip address of the device and port number when you are at home and the house ip and port when you are not.Are you typing it into the address bar or using software for your cctv or accessing on an app?

whats the problem you are having?. I have mail, Ftp and webcams setup and all work perfectly and quite literally all Ive done is setup the Ip address of the machine running these and the port number and thats it.

Practically everyone who has problems setting it us is doing the same thing, trying to use the external address on the internal network to test.

ok, so it will do that, HOWEVER, if you try testing it from your internal network using the WAN Ip address it will appear to fail.
Inside your home you need to use the 192.168.192.6:4200 address. Externally, as in a completely separate internet connection, you can use your WAN address xxx.xxx.xxx.xxx:4200

That worked from outside my network alright. It kinda makes sense in that if you could use the address that the outside world knows you as, you could end up forwarding to yourself. Anyway thanks again.

sorry, what port forwarding are you trying to do and what URL is giving you that page issue?

80 is the default http port so the box actually uses its own internal IP and port 80 for its web gui.

http://192.168.192.2 is a LAN Ip address so port forwarding has nothing to do with trying to access that URL.

Its would also be odd that this device has .2 as its address unless it was the first device ever to connect to it or youv'e set that statically, as a rule of thumb devices that you want to connect to internally shoudl have a static IP and start somewhere around 192.168.192.100 or so. So I guess is what Im saying is make sure whatever youre trying to connect to has that address.

Anyways, i digress

Typing http://192.168.192.2 is actually really http://192.168.192.2:80, with 80 being the default port fro http, https (secure http) is port 443 so you want to be typing https://192.168.192.2 or https://192.168.192.2:443

If you want to contact that device from outside your network you woul point 443 to the internal IP of that device 192.168.192.2 443 both (tcp and udp) and to test you would need to use a completly seperate connection from OUTSIDE your horizon network. Since wan port reflection is not supported you CANNOT test it on using teh WAN IP address on the LAN.

To get into the boxes web interface its 192.168.192.1 admin/admin..

Could have just asked that in the first place

Is it working internally? Is port 7777 listening if you check it from your network?

Dickmcsavage wrote: »

I typed netstat -a and can see activity on that port. I'm assuming that means it open?

Definitely seems like it's listening. Is there a firewall on the .100 machine? Might be blocking inbound connections

Do you have another windows machine on the network? You could install Advanced Port Scanner and see if port 7777 is accessible from another machine

Youre doing nothing wrong and it probably works properly.

Horizon doesn't support WAN port reflection. Ive explained this in detail several times in this thread. I suggest you actually read the thread as the exact same scnario you posted has been asked and answered more then once here.

The netstat shows connections outwards on that port, It doesnt show its listening on that port.

You would ecpect on a netstat -an | findstr "7777" to see something like

TCP 192.168.192.100:7777 0.0.0.0:0 LISTENING

Dickmcsavage has not shown 7777 is accessible on the 192.168.192.100 machine from inside the LAN.

This should be established first before attempting to setup or troubleshoot a connection to that port from the WAN, IF The horizon box cant access the service on that port theres no way you can do it from Outside on t'interwebs.

any device with a telnet app should be able to test this on port 7777, doesnt have to be a windows machine, theres several free ones for IOS and Android.

This has been explained a half dozen times in this thread but fcukit Ill explain again, If youre using DDNS inside your horizon network, even though its an external web address its translating that web address into the WAN port address of your horizon box. The horizon box doesnt support wan port reflection so it makes no difference if you use a ddns address or the internet address of your horizon box. If you are testing this from inside your own network it will APPEAR that the port forwarding isnt working. But it is.

If you were on a different internet connection and had the post forwarding settings pointing to your internal IP of the webcam on port 82 using both protocols you would be able to access your webcam. Inside the network you can only use yoyr internal address of the webcam (192.168.192.x:82)

Hi Folks, need an advice how to make Transmission work on Horizon.

My set up is a laptop, smarttv and a zyxel nsa325 (v1) NAS, on GB lan + horizon box (200mibt). I used to have the Cisco EPC Gateway, torrent was working like a charm via TM RemoteGui, but I've forgot to check what settings I had before moving to Horizon.

the NAS has a fix ip. let's say 192.168.1.16, TM uses port 9091, I can log into the TM client running on the nas from browser as well using this "example" ip/port combination. I'm trying to d/l TBBT off eztv.it, torrent added to the job list, but doesn't start, no peers, stc.

In TMGUI I have 9091 as incoming port,enabled port forwarding, utp/dht/peer exchange enabled, so does the encyrption.

I recall I had to forward a port in the EPC GW to make P2P d/l work, but honestly forgot how to do that.

Considering the above "example" ip/port combination am I correct that I need to put:
9091 to Public Port Range
192.168.192.16 to Target IP Address
9091 Target Port Range
Protocol Both

Am i doing it wrong?

Thx for the advices

Edit: this worked.not only to be able to d/l from public tracker, but now from private ones. finds peer list straight. Still need to work to fine tune as i'm only getting 2,7mbyte/sec where I have over 4000 seeder

Make sure you have set the machine running the minecraft server to have a static IP, say 192.168.192.100

Then the settings in your horizon box would be
25565 <Public port range
192.168.192.100 < Target port Range
25565 <Target Port Range
Both <protocol

to find out what users OUTSIDE your network need to connect to just goto www.whatismyip.com
You could use some sort of DDNS but UPC leases last ages, prob no point and many games check this themselves anyway.

on your LAN your external address wont be contactable, you need to use your internal address when on your own network, for this example that would be 192.168.192.100

You will need someone on a different internet connection to test if they can connect to your minecraft server form the outside, you cannot do this from within your own network.