I would be very interested in any write that you have on the SSH tunnelling.
I was attempting the "port forwarding" only the other nightbut again accessing the dynamic dns was proving too painful.
Thanks StevieP, this is just what I was looking for. However, I have done everything you have said, but when I try to connect using my iphone I get the message 'Information - Host has closed the session' and I'm not sure what this means exactly.
I still have the TightVNC service running on my Windows 8 laptop.
Any advise please?
Hi dmp192, this thread was last posted on over three years ago and the last time StevieP was logged on was in Aug 2010 so he may not reply to you.
Ah, right, didn't spot that, sorry. Thanks for pointing that out. Can anyone else suggest what I may be doing wrong please, or indeed, what the message 'Host has closed the session' really means?
Has anybody actually successfully configured the HomeHub 5 to provide "anywhere access" for MS Server Essentials 2012?
I have read the various threads and suggestions but none of them actually work and I cannot find anybody within or outside the BT forum who has cracked it.
I must admit I have only been on it for 4 days but, I think I may have prematurely retired my Billion 7800N in favour of the HH5.
Seems this is still aproblem, even 3 years later... 🙂
The solution is to ensure that the "Host:" header in your HTTP request matches what the hub expects to see... If you are tunneling, this won't normally be the case as you'll be browsing to something like http://localhost:8000 instead of http://192.168.1.1 as you would at home... This means your host header will look like "Host: localhost:8000" instead of "Host: 192.168.1.1"
You may be able to fix this with a browser plugin that modifies headers, but I simply added a couple of steps to my tunneling instead:
First, create a virtual ethernet interface on your local machine that matches the remote hub's address:
sudo ifconfig eth0:1 inet 192.168.1.1
Then when you tunnel to the machine that's going to forward the port for you, make sure you bind to this address:
ssh -L 192.168.1.1:8000:192.168.1.1:80 my-remote.host
Yes, I know this looks all wrong, but it works! 🙂
Now you can simply browse to:
and you will connect through the tunnel to the real 192.168.1.1
An alternative solution if you are stuck with a windows machine:
1) setup dynamic dns on the HH5 pointing to an hostname of your choice
2) use PuTTY to connect to the hostname you configured at the previous step
3) add an SSH tunnel to the PuTTY connection configuration, mapping local port 80 to bthomehub.home:80
4) edit your /windows/system32/drivers/etc/hosts adding the entry 127.0.0.1 for bthomehub.home
5) browse to http://bthomehub.home
Remember to reverse step 4) once done, otherwise you wont be able to connect to the HH5 from that machine unless the SSH connection/tunnel is in place.