BT HomeHub 4 - Port Forwarding.

I need to open up ports 80, 8068 on my Home Hub 4, I have followed the port forwarding instructions but it will still not open them.
I have opened up ports 9000, 85, & 18004 in the same way and this has worked?
Any advice?
Cheers.

Traffic will only be allowed back in on port 80 from a source if your device has already sent traffic to that source, because port 80 is used pretty much everywhere for http traffic and leaving it fully open would be just asking for trouble - it's pretty much a given that one of a limited number of browsers is sat at the end of it.  I'm assuming that 8068 is similarly restricted.

Similar Messages

  • BT Homehub port forwarding - Conflicts?

    I am trying to set up an application for a minecraft server. I need to forward ports and I create the application for the Minecraft server with ports 25565 and when I try to actually apply it, it says:
    ports setting conflict
    This application ports setting conflict with others, Please correct it and try again.
    I dont see how there are any conflicts? I dont have any other applications set up on my router?

    Same thing happens when you try to add Xbox Live - nobody knows why.  Basically a full reset seems to be the only fix and even then you have to be quick when setting up port forwarding otherwise the conflicts issue happens.
    ---Remember to mark as 'solved' and give stars when you like a post---

  • Homehub Port Forwarding trouble. (Terraria)

    Hey everyone, yet more problems with my HH2. This time port forwarding is being very weird.
    Im tryng to set up a terraria home server (its a video game on PC for those who don't know) and it requires TCP and UDP port 7777 to be open.
    I followed this guide: http://portforward.com/english/routers/port_forwarding/BT/BTHomeHub2/Terraria.htm to try and set it up.
    I then downloaded portforward.com's program which checks to see if your ports are open, and heres the weird thing, TCP 7777 wont connect however UDP 7777 will connect. So I tried it with port UDP and TCP ports 7776 and 7778 and in this case both the TCP and UDP ports work fine for 7778 and 7776. I've triple checked to make sure I've not mistyped but as far as Im aware its correct. Any ideas what might be causing this?
    [EDIT] turns out my firewall is to blame, god I feel silly now
    Aut inveniam viam aut faciam

    If you want to say thanks for a helpful answer,please click on the Ratings star on the left-hand side If the reply answers your question then please mark as ’Mark as Accepted Solution’

  • Port Forwarding and Loopback with HomeHub 3B

    There have been a number of threads discussing port forwarding and loopback, so I thought it might be useful to summarise my experiences. I have two HomeHub 3Bs on separate lines, one is a standard broadband line, the other is on an Infinity connection. My experience is limited to these two specific devices :-)
    Port Forwarding does work but it is "temperamental" and "arcane" in the way you need to set it up. Although I have had it running perfectly, I have also had experiences where the router has refused to "accept" my changes. Tentatively, I put this down to the fact that I was running a Seagate GoFlex network drive on the network and this piece of equipment (definitely a Do Not Buy) was acting aggressively and screwing up the DDNS allocations. But ... YMMV
    One definite probllem with Port Forwarding is if you attempt to specify a range of addresses. I have failed to get this to work on both my hubs. In my case I was trying to forward (say) 8021-8022 to 21-22, and the router insisted on forwarding both 8021 and 8022 to port 21.  The cure is to set up each port as a separate rule within the same user-defined application.
    On Loopback, I know various people have said it doesnt work, but it has always worked fine for me, at both the locations where I have a HomeHub 3B. I use a DDNS service and I can test that my port forwarding is working by opening a Command Prompt window on my PC and typing  telnet mydomain.dyndns.web.com 21 or whatever. That command contacts my DDNS host to ascertain my IP address and then (attempts to) connect to port 21.
    If port 21 is closed on your router (i.e. you have no port forwarding in place) you will see the message attempting to connect to mydomain.dyndns.web.com... and, after a while that will time out, with Could not open connection to the host, on port 21: Connect failed. If you do have your port forwarding set up correctly then your application will respond in some appropriate mannerr. However, you do need to understand what youre doing, because the response of an application that is expecting HTTP data is simply to do nothing!  You will probably get a blank screen. If you type GET / HTTP/1.1 [note spaces] (which is not echoed to your screen, so be careful not to mistype it) you will receive a page of HTTP response data and HTML data. Thus proving that your port forwarding is working.
    If you do not have any port forwarding set up at all, you can still test the loopback function by attempting to connect to port 161. This port is open on the BT routers and telnetting to it will result in a blank screen (as opposed to the attempting to connect message).
    In summary: loopback works on the Home Hub 3B. Port forwarding also works to a degree but it is temperamental and does have some quirks, like not properly accepting ranges of ports. On this last point, at least, it would be helpful to get an acknowledgement from BT that this is a known fault.

    There have been a number of threads discussing port forwarding and loopback, so I thought it might be useful to summarise my experiences. I have two HomeHub 3Bs on separate lines, one is a standard broadband line, the other is on an Infinity connection. My experience is limited to these two specific devices :-)
    Port Forwarding does work but it is "temperamental" and "arcane" in the way you need to set it up. Although I have had it running perfectly, I have also had experiences where the router has refused to "accept" my changes. Tentatively, I put this down to the fact that I was running a Seagate GoFlex network drive on the network and this piece of equipment (definitely a Do Not Buy) was acting aggressively and screwing up the DDNS allocations. But ... YMMV
    One definite probllem with Port Forwarding is if you attempt to specify a range of addresses. I have failed to get this to work on both my hubs. In my case I was trying to forward (say) 8021-8022 to 21-22, and the router insisted on forwarding both 8021 and 8022 to port 21.  The cure is to set up each port as a separate rule within the same user-defined application.
    On Loopback, I know various people have said it doesnt work, but it has always worked fine for me, at both the locations where I have a HomeHub 3B. I use a DDNS service and I can test that my port forwarding is working by opening a Command Prompt window on my PC and typing  telnet mydomain.dyndns.web.com 21 or whatever. That command contacts my DDNS host to ascertain my IP address and then (attempts to) connect to port 21.
    If port 21 is closed on your router (i.e. you have no port forwarding in place) you will see the message attempting to connect to mydomain.dyndns.web.com... and, after a while that will time out, with Could not open connection to the host, on port 21: Connect failed. If you do have your port forwarding set up correctly then your application will respond in some appropriate mannerr. However, you do need to understand what youre doing, because the response of an application that is expecting HTTP data is simply to do nothing!  You will probably get a blank screen. If you type GET / HTTP/1.1 [note spaces] (which is not echoed to your screen, so be careful not to mistype it) you will receive a page of HTTP response data and HTML data. Thus proving that your port forwarding is working.
    If you do not have any port forwarding set up at all, you can still test the loopback function by attempting to connect to port 161. This port is open on the BT routers and telnetting to it will result in a blank screen (as opposed to the attempting to connect message).
    In summary: loopback works on the Home Hub 3B. Port forwarding also works to a degree but it is temperamental and does have some quirks, like not properly accepting ranges of ports. On this last point, at least, it would be helpful to get an acknowledgement from BT that this is a known fault.

  • BT HomeHub 5 Port forwarding to 2 PCs

    I have two PCs set up with TightVNC server and can access them both perfectly.  One is on <ipaddress>:ort 5900 and the other on <ipaddress>prt 5901.  I have also set up port forwarding so I can access one PC via the internet using no-ip to handle the ddns.  To set this up I selected the application VNC and linked it to the PC.  This works well and remote TightVNC client can log into the TightVNC server on that PC.   The problem is that I have two PCs running TightVNCserver and I need to remotely log into either or both simultaneously but I cannot set up another port forwarding entry as VNC is in use and removed from the list of applications.
    Is there any way to set up port forwarding to two PCs with different port numbers?
    Thanks
    Richard
    Solved!
    Go to Solution.

    Without getting my HH out of the cupboard to check, is there not an 'other' application that you can assign the port to? Surely the name is just a label it doesn't have to be called VNC.
    Edit: Found this http://bt.custhelp.com/app/answers/detail/a_id/46548/~/how-to-set-up-game-and-application-sharing%2F... click 'no' at step 3 of the second set of instructions.

  • BT HomeHub 4 - Cannot configure Port Forwarding

    so I want to open port forwarding on my HH4 to set up Vodafone Sure Signal which stopped working when infinity installed. the instructions at 
    http://bt.custhelp.com/app/answers/detail/a_id/43715 
    bear no relation to what I get on Home Hub Manager please advise....

    Here is an example of the settings for an IP camera connected to a home hub 4.
    http://forumhelp.dyndns.info/hardware/cctv/foscam/foscam.html
    It should give you some extra guidance.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • Homehub 5 port forwarding for Windows Homeserver 2...

    Hi
    Has anybody any solutions on setting up the HH5 for Windows Homeserver 2011
    I've inputted all the rules manually as WHS couldn't complete the task, to find ports 80, 443, 4125 remain closed after manual input.
    WHS reply's with UPnP not working / router not working.
    BT customer services quite appalling and I'm not paying for Tech Support as the package is only 6 months old and I feel I shouldn't have to pay for a product that isn't working correctly, if it was over 12 months I understand I should pay.
    I've manually inputted and setup port forwarding for my Iphone app and Android and they've finally started working.
    Cheers
    Solved!
    Go to Solution.

    Can you just put WHS in the DMZ on the HH5?
    If you found this post helpful, please click on the star on the left
    If not, I'll try again

  • Port forwarding issue on Homehub 3.0 Type A

    I'm trying to port forward both Minecraft and Black Ops 2. Everything works alright up until I try and actually forward it to my desktop.
    When I press 'Add' or 'Apply' either in the port forwarding section or home network section it changes Minecraft to PalTalk and Black Ops 2 to BT Homesafe Camera. I can't find any information on this specific issue but if anyone can help I would much appreciate it.
    Another thing to mention is that when I try and forward Minecraft and it changes to PalTalk both are removed from the drop-down list of selectable things to prot forward. I use the PFPortChecker program from portforward to check and it's saying that the ports are closed.
    Thanks

    Thanks for all your suggestions and help. I had sorta the same problems on an old 2.0 hub (the one where once you deleted a rule you had reset all settings to reassign it).
    I managed to get Minecraft portforwarded... I have no idea how. I was mostly absorbed in my thoughts of "What dumba** at BT actually let this product go through testing if they even do any testing on their modem/routers to begin with?"
    So I managed to get the original PalTalk rule deleted o.O. I'm doing the same for Black Ops now so hopefully I can recreate the steps. When I click edit on the Black Ops rule it brings me in to the BT Homesafe Camera rules. After editing this and changing the name form BT Homesafe Camera to BT Black Ops 2 I applied it and instead of editing the rule, it added a new rule. So now I had Black Ops 2, BT Black Ops 2 and Minecraft in my user-defined options. I deleted the one called Black Ops 2 and it instead deleted BT Black Ops 2. And now it works. Also the BT Homesafe Camera original rule is now gone and now it's time to make a back-up if ever it screws up again.
    So that's weird but thanks a lot for your help and I hope my poorly written paragraph helps others that might be having the same issue

  • Port Forward Question _ BT HomeHub 3

    Hello all,
    Ive been trying to set up port forwarding on my bt router but to no avail so far.
    On the port forwarding tab in the router settings when I click Add to assign a device nothing happens??
    Ive tried on my iphone and laptop and the "add" button turns grey but nothing happens?
    Can anyone help?

    so your selecting the "game or application" then selecting the "device" and the "ADD" button stays grey?
    or can you select add but after selection and the page refreshing the new device doesnt show up?
    under "supported applications" you can manually set up a device vis "new game or application" as a last resort

  • Home Hub 3 Port Forwarding (NOT)

    Hello World
    Ok recived the New Home Hub 3 today, ahead of my Infinity install.
    I thought ok lets replace Trusty Home Hub 2 with the 3 as it works both on Std ADSL and Infinity
    Super Quick UI and love the GIG port BUT and its a BIGGY (well for ME) !
    THe hub is running 4.7.5.1.83.8.48 (TypeA) lastest and greatest, Upnp does work so Xbox works no prob and it can be seen in the FW Log being setup 
    BUT if you configure port forwarding by hand ie HTTP to 192.168.0.2 DOESNT WORK !!!
    I tried using a connected device to forward to and just the IP address BOTH FAIL !
    roll back in trusty Hub2 and all work again !
    Phoned in and was told after a few minutes on hold (No Problem) to roll back to Home Hub 2 and there should be a Firmware upgrade for the 3 soon to fix this issue.
    So now you know if you try it and it doesnt work
    Giz
    Solved!
    Go to Solution.

    Similar situation here.
    I received HomeHub 3 this week. Overall, I am pretty satisfied with the new router. The local networking feels quicker due to the gigabit port (connected to gigabit switch). And the wifi reception is better probably due to the intelligent channel selection.
    Similarly, I tried to replicate settings from my old HomeHub 2. I wasn't able to setup port forwarding.
    The problem is the router in inaccessible using the external IP address.
    I contacted BT Broadband Help desk. I spoke to 2 operators. First told me he would investigate and call me back. Never did. Second told me they were untrained to deal with this sort of queries and suggested speaking to the BT Subscription help line.
    So, now I know thanks to you. Waiting anxiously for the patch. Hope it will be out soon.
    Slava

  • Port Forwarding (for IP Camera)

    I have so far been unsuccessful in in setting up my new ip camera for remote monitoring.
    I have followed all instructions within the "bt homehub" domain for port forwarding in application sharing but when I check that the port (80) is open (using pfportckecker.exe) it returns "unable to ping your router" and "port is not open or available".
    Can anyone help please - I am becoming very frustrated !
    Thanks
    Solved!
    Go to Solution.

    mikedunk wrote:
    I have entered the local ip address (192.168.1.69) which translates to "Unknown-7c-dd-90-05-5e-df"
    which I assume to be the ip camera (which is connected wireless)
    What am I doing wrong !
    Thanks,
    Mike
    For "Unknown-7c-dd-90-05-5e-df" the bit in bold should be the MAC address of your camera. It is normally printed on the device somewhere.
    You can rename this if you wish, by editing the name to something more appropriate.
    You should have a created a custom rule called mikes-camera, which with:-
    Protocol TCP
    Start port 8080
    End port 8080
    Mapped to 8080
    Leave the rest blank.
    You should be able to assign this to the device.
    A lot depends on which version of the home hub you are using.
    What I have found by experience, is that it is better to use a static IP address, if your device supports it, as DHCP can be a bit unreliable when port mapping is involved.
    You can use a static address outside of the DHCP range. Like 192.168.1.50.
    You can still forward ports to it, by selecting the device by its IP address, not its name.
    If you can view your camera within your own network, using http://192.168.1.69:8080 then you just need to persevere with the port mapping.
    There are some useful help pages here, for BT Broadband customers only, on my personal website.
    BT Broadband customers - help with broadband, WiFi, networking, e-mail and phones.

  • Port Forwarding on Home Hub 5 not working

    Hi,
    Is anybody else having problems getting ports to forward on their Home Hub or Home Hub 5?
    I am a new BT customer, less than a week infact and BT have been utterly hopeless in getting this resolved. All they do is send me instructions for port forwarding on a homehub which I do not need and tell me that i need to pay for their tech support to investigate it further which is freaking ridiculous considering port forwarding is an essential part of any router and this router is brand new, less than a week old. (Do BMW sell you a car and then refuse to take responsibility for a broken engine?)
    My other option is buying an ADSL 802.11ac router for £150 which out of principle, i dont think i should have to do. One of the reasons i came to BT in the first place was because the homehub is supposed to be one of the best free provider supplied routers around. 
    Please only reply to this if you know what you are talking about or have experienced this same issue yourselves. I reiterate that I have not missed any configuration steps on my part and this is a case of the homehub simply not working as it is designed.
    Scenario:
    I like to have remote desktop access to my home computer from external networks. I do not use 3rd party software such as 'log me in' or 'team viewer', I like to use Microsoft Remote desktop and had been doing so for years with my Sky broadband until last week.
    I have dynamic DNS running on my machine which updates my constantly changing external IP to the dns server so dont worry about that, thats all good.
    I have correctly set up the forwarding of TCP 3389 to the static I.P of my home desktop on the homehub (and rebooted and or factory reset several times)
    Result:
    Nothing. The homehub displays as though it has forwarded the ports yet i am still unable to remote in from an external network. The port shows as closed when i run a port scanner.
    The same goes for other ports I have tried to open. For example, my Xbox One.
    BT are sending me out a replacement Hub to try but I fear that this will have the same result as i have seen a few other people post with the same issues.
    If anybody has experienced and or resolved this, please let me know and i will be forever grateful
    Thank you

    When you do a major network revision always reset the TC to factory and start over.. it simply remembers too much of the last setup.
    Plug WAN TC into the HH5 and run through the airport utility again. The TC must go into bridge mode. It then should work fine, but I recommend particularly with Mavericks you use strict naming.
    Not apple names.. long, loose and loopy.
    Names that are short, 2-10 characters is plenty but make an upper limit of 20.
    No spaces..
    Pure alphanumeric.. no apostrophe or any other odd character.

  • Port Forwarding HELP NEEDED!!!!

    I have a HomeHub v2 and I just cannot get the 25565 port open!
    I have it opened in the router settings exactly as all the guides say to do it however http://www.yougetsignal.com/tools/open-ports/ still says it's closed!!!!!!
    Please help, what am I doing wrong???

    As well as the suggestion above, you also need to check that the IP address/Device Name that the Port Forwarding is assigned to is available. You should use ping to check this locally first.
    Due to the IP address being dynamic (able to change when the DHCP lease expires), it is sometimes easier to set a static IP address on the device you are forwarding to.
    Settings->Advanced->Home Network->Click on Device->Always use this IP address. While you are there, check that this device corresponds to the IP address/hostname that you have Port forwarded to.
    For your convenience, Home Network link here:
    http://192.168.1.254/hnet_device.lp?be=1&l2=0&l0=2&l1=3

  • New Customer Experience with Port Forwarding

    OK, so my OpenReach Modem and HomeHub 3 were installed last week and all seemed OK at first.
    A bit of background:
    I'm a seasoned IT guy and have a nice network set up at home that caters for my needs (most of the time).
    Without going into too much detail, I have my own DHCP/DNS server and I run a Webserver for personal use.
    I have Virgin Broadband - which work most of the time.
    I've also just had BT Infinity installed so I should always have Internet access no matter which ISP is having issues.
    I was hoping to be able to access my webserver externally from either my BT or Virgin. I didn't think this would be an issue.
    It still all works fine through my Virgin connection. I use dynamic DNS (no-ip.org)  to get to my server. 
    On the Virgin Superhub - I have DHCP switched off and all my machines (except one at the moment) get the Virgin router assigned as the Internet gateway (via my own DHCP server).  
    My test machine gets a the BT HomeHub 3 assigned as the Internet gateway (also from my own DHCP server) and I have switched off DHCP on Home Hub.  
    Before I move onto my issue, I have to say that the above network setup works flawlessly. 
    The Virgin Router is on 192.168.0.1, The Home Hub is on 192.168.0.2.  (subnet 255.255.255.0)
    They are on the same network but because DHCP it switched off on both routers - everything is happy.
    I can access my Server from the Internet via my no-ip.org address and it all works great.
    The issue:
    I thought it would be relatively simple to configure the BT Home Hub 3 to access my server from the Internet.
    Hmmm. Port Forwarding seems to be the issue. It just doesn't work reliably enough. Sometimes it works, then sometime it stops working. Right now it's not working.
    At first I though it was just me, not configuring it correctly. But no.
    Then I started reading this forum and found there are reports of issues with port forwarding going back a year.
    I don't know if that a good or bad thing - an issue running that long must be on the verge of getting fixed right?
    Or any issue running that long without resolution probably has no simple resolution or just isn't a priority (for BT) maybe.
    My Question:
    (and I think I already know the answer)
    Has anyone got a sure fire way of configuring the HomeHub3 so the port forwarding works? 
    Or should I just throw in the towel now and buy a Dual Wan Router? 
    One last note:
    This morning my Infinity Broadband Speed dropped from
    38Mb down/6Mb Up (measured several times yesterday)
    to
    0.7Mb down/0.3Mb Up (yes those decimal points are in the right place)
    And I haven't got a clue why.
    I power cycled the HomeHub and it returned to normal. Does this happen to other people?
    Cheers
    Graeme.
    Graeme

    Bullitt wrote:
    the port on your network is defined by lan ip address and port number eg 192.168.1.10:80
    you cannot forward this outbound port twice
    There is no "port on my network" A port is associated with a IP address not a network.
    My webserver listens an port 80 - requests from the Internet for http are port forwarded by the router (either BT Homehub or Virgin Superhub) to port 80 at address 192.168.0.5 (in my case). 
    If I am trying to access my webserver from the Internet, I point my browser at the WAN IP address of my router (again it doesn't matter which one - BT or Virgin) and the router port forwards the request to my Webserver.  Each router can do this independently. 
    "you cannot forward this outbound port twice"
    As explained above - It's an inbound port not an outbound port.
    I appreciate you are trying to be helpful but just telling me something is not possible without explaining why its not possible doesn't really help me.
    As I said before, this was working fine, then it stopped working but only when trying to access my webserver via the BT Router. It still works fine from my Virgin Router. I used WireShark and port mirroring on my switch to prove that the Home Hub as stopped port forwarding inbound traffic to my webserver. 
    This is a problem with port forwarding on the Homehub, not my network setup. Looking at other posts on this forum - I'd suggest I'm not the only one having problems.
    To be honest, it's the least of my problems with the HomeHub right now. I'm far more concerned with the fact that twice today I've had to power cycle it because the throughput has dropped from 38Mbit-down/6Mbit-up to <1Mbit-down/<1Mbit-up. It's a known problem, BT are working on it, yet I still am paying full price for a product that should never had made it out of Beta test.
    Graeme

  • How to get Port Forwarding to 8080 working on HH2

    Hi,
    How can I get port forwarding to 8080 working on my HomeHub2?
    I have a QNAP TS219P NAS connected via wired Ethernet to my HomeHub2.
    This has a Web Administration facility that should enable me to access & manage the NAS over the Internet.
    I have set the NAS to have a fixed IP address of 198.162.1.100 and enabled a dyndns account to point to my ISP WAN IP. I then used Application Sharing on the HH to forward all traffic to 8080 to the NAS device (called "Kermit" in my case).
    However, using http://mysite.dyndns.org:8080 simply brings up the admin page of the Home Hub.
    Despite the HH telling me the port is forwarded correctly, http://www.canyouseeme.org reports the port as - "Error: I could not see your service on nn.nn.nn.nn on port (8080) ...Reason: Connection refused"
    My HH firewall is set to "Default" (Allow all outgoing connections and block all incoming traffic. Games and application sharing is allowed.), but I have tried disabling it and this made no difference at all.
    I know that dyndns and port forwarding are working in other respects, since I also set the NAS up as a Web Server with a simple home page, and forwarded port 80 on the HH through to the NAS. Requests over the Internet for the http://mysite.dyndns.org:80 home page work fine...
    There's nothing in the HH Event log that I can make sense of and I'm going mad...
    Is anyone able to talk me through some good ideas of how to progress this?

    Another thing I thought of- did you setup the port forwarding to forward to your named IP address or to the hostname?
    I would recommend setting the port forwarding to your named IP address:
    http://192.168.1.254/app_config.lp?be=1&l2=0&l0=2&l1=4
    In this menu (Application Sharing -> Configuration, select "User Defined" in Device. A textfield entry box appears below device and hardcode 192.168.1.100 in there).
    Finally, any logs on the QNAP for your external connection attempts? - Could it be passing through the HomeHub and then get rejected by the QNAP?

Maybe you are looking for