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.

Similar Messages

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.

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 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 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.

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---

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

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’

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 external access to VNC server on multiple machines

I will have 10 PCs connected to the WRT54GL wireless AP. I am testing with 1. It has a static addresses 10.155.22.51. It is running a VNC server at port 5951.
If I set my VNC client up to access 10.155.22.51:5951 it works through the WRT54GL wireless AP.
I set the WRT54GL port forwarding to 5951 - 5951, set the IP address to 10.155.22.51 and enable. The external address of the AP is 10.155.0.29 on the company LAN.
So I set the VNC client to access the AP address with the VNC port, i.e. 10.155.0.29:5951. I expect the AP to change the address to 10.155.22.51:5951. This does not work.
Note: the problem could be that the AP is going through NATting because I can also access it at 10.155.22.9 along with all the other PCs on that LAN, i.e. I can access the LAN directly from elsewhere on the company net.

You can try changing the IP of the AP manually ... connect it to the Computer ..... access the setup page using http://192.168.1.245 .... use password as admin ....
Configure the IP settings first ...
Again login with new IP address .... configure wireless settings .....
Power down the AP & then the router ....
Wait for few minutes .... then power on the router ...first then the AP ...

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.

Ssh Port Forwarding Stopped Working

I have used ssh port forwarding in the past, and it has come in handy.
I have recently upgraded to Mavericks, but it does appear that my ssh port forwarding stopped some time before this. The last time I know it worked was 5/14/14, and feel it has worked more recently as well.
Here's what I do, from my Mac I ssh to my work jump server (port 22, let's say its IP is 11.22.33.44), and my jump server has access to work PC (lets say IP of 10.1.2.3). My work PC has RDP running on it on the common port 3389. I have verified that I can set up a working RDP session at work from another box. Also, I know that my jump server can get to my PC at work as I can ping my work IP if I just ssh straight to my jump server. And I know that there is no firewall stopping me from the jump server as I can also open a telnet session to my work PC on port 3389, without errors.
So, here's how I have done it in the past and it has worked, but now recently stopped working in Terminal app:
ssh -f [email protected] -L 3388:10.1.2.3:3389 -Nnv
The verbose logging shows that it sets up connectivity. If I then look to see if my local port is listening I can type:
netstat -an | grep 127.0
I will note that port 3387 is in fact LISTENing and waiting for connection
I then start my RDP client app, and start a session to "localhost:3387" (I could also use "127.0.0.1:3387", and have, but it does not work either). My RDP client eventually times out. I have turned my firewall off and on, neither way works.
Does anyone know why this may have stopped working?
Your input is most appreciated.
The verbose log shows the following is setup appropriately (with noted modifications to server names and actual IPs):
debug1: Authentication succeeded (keyboard-interactive).
Authenticated to somewhere.net ([11.22.33.44]:22).
debug1: Local connections to localhost:3387 forwarded to remote address 10.1.2.3:3389
debug1: Local forwarding listening on 127.0.0.1 port 3387.

Unfortunately I don't have another device to test if RDP is working on my LAN, however, when I check out my network connections and this is what I see after setting up the ssh tunnel and prior to attempting the RDP connection (again names protected):
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
Then, as it is difficult to catch in the middle of TCP 3-way handshaking, here's what happens after an attempt with the RDP client while it sits and spins:
my-rmbp:~ me2$ netstat -an | grep 127.0
tcp4       0      0 127.0.0.1.3387         127.0.0.1.50323        FIN_WAIT_2
tcp4       0      0 127.0.0.1.50323        127.0.0.1.3387         CLOSE_WAIT
tcp4       0      0 127.0.0.1.3387         *.*                    LISTEN
You can clearly see it's attempting to make a connection over the tunnel via my RDP client, but it's being shut down right away. I will obtain a WireShark packet capture and see exactly what's happening. Oh, and if I tried to RDP to a port other than the one I set up the port forwarding tunnel with, RDP would disconnect right away.
What I'm most interested in is why, without any known changes, other than OS updates, did this work a few months ago, and now it does not?
I have also tried other test ssh port forwarding, such as to www.apple.com forwarding 8080 on localhost to 80, and others, and none of those work either with web browsers, I assume this is something Apple has done to disable ssh port forwarding/tunneling. Perhaps someone else has bumped into this and found a fix? Please share!
Also, I have heard that you have to be root in order to set up port forwarding, but clearly this is not accurate, as it worked before, and also as you can see above it worked without root. But I tried both ways, and sadly neither worked.
Could it by my jump server? Possibly, but others at work do this and it works just fine for them from their Windoze PCs. So can't be that either.
Perhaps my capture will tell me, I'll report back here with what I discover. Thanks in advance!

WRV210 port forwarding only works on http!!!

I'm trying to use SSH port forwarding, and VNC on the future.
Right now the only one that is working is http. I have enable both HTTP and SSH over two different PCs, and only the http one is working.
We already have version 2.0.0.11. Also tried DMZ the second PC and didn't work.
I hear about to use DHCP, and then I defined the second PC mac on the table, and still didn't worked.
Any idea of what is going on with this equipment.
Carlos Alperin

If you enter the IP address on this page http://www.whatismyip.com/ip-tools/ip-whois-lookup/
you can see who it belongs to.
But I suspect that its something within your router that is returning the wrong WAN address. Do you have an ADSL connection, or an Infinity connection?
Yo may have difficulty connecting to your own external WAN address from within your own network, unless your router has NAT loopback enabled.
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.

BT HomeHub 5 Port forwarding to 2 PCs

Similar Messages

Maybe you are looking for