{"id":91,"date":"2009-11-28T17:16:33","date_gmt":"2009-11-28T17:16:33","guid":{"rendered":"http:\/\/www.seepyou.net\/blog\/2009\/11\/28\/windows-home-server-and-the-thomson-tg585v7-router\/"},"modified":"2014-07-30T15:27:53","modified_gmt":"2014-07-30T14:27:53","slug":"windows-home-server-and-the-thomson-tg585v7-router","status":"publish","type":"post","link":"http:\/\/www.seepyou.net\/blog\/2009\/11\/28\/windows-home-server-and-the-thomson-tg585v7-router\/","title":{"rendered":"Windows Home Server and the Thomson TG585v7 router"},"content":{"rendered":"

It has been noted that this router has a problem with the setup of the Remote Access feature of WHS. It plays nice with the UPnP protocol and the WHS reports as having setup the router successfully, but it turns out that there is a problem and the (name).homeserver.com is not accessible, pointing instead to your router admin page.<\/p>\n

The reason for it is that the router will not forward the 443 port required and reserves it for its own use, hence when the https connection is established it just points to the router.<\/p>\n

There are two ways to deal with it. One, you force the router to release port 443 and all is well, and two, translate any port you wish to 443 for the server. Solution one is described here<\/a> but I don’t like it. It means forcing your router to do something it doesn’t want to which one never knows what it can cause, and the process itself is not so easy and requires a certain knowledge that not everyone has.<\/p>\n

The second option, however is far simpler and easy. All one need to do is forward other ports and some have even suggested to point the one above it (i.e. instead of 443, forward 444). Now here are two points that need to be made.<\/p>\n

1.\tThis solution does work. As the router does not restrict other ports except 443, forwarding any port you want to the server with a trigger for 443 will work.
\n2.\tThis can cause major problem if you are not a little careful. As I said, some suggested using port 444 to handle the server. Port 444, however, is quite common, used in pagers all over the world and could trouble you.<\/p>\n

For this reason, I would suggest that you go here<\/a> and find a port that is not showing. Then use this to call your server and have your router catch that port and forward it to the server with a 443 translation.<\/p>\n

Here is how (in pictures). Enter your router and go to the port forwarding page. Put a name for the scheme and create a blank one.
\n\"step1\"<\/p>\n

Type in the ports and hit Add after each one. Make sure that the protocol is set to TCP, not any or UDP.
\n\"step2\"
\n\"step3\"
\n\"step4\"<\/p>\n

After you reach this point, click on Assign a game or application to a local network device.
\n\"step5\"<\/p>\n

This final image is what you should end up with.
\n\"step6\"<\/p>\n

The address I am using for my WHS is of my own choosing, simply because I have a certain addressing scheme in my head (router at the end of the subnet, then servers, with printers at the start and everything else starting from 64 onward – for a standard 255.255.255.0 subnet). You will of course replace that with the address of your own WHS.<\/p>\n

Now all you have to do is let people know that the proper address for them to log in to your site is:
\nhttps:\/\/(name).homeserver.com:395\/remote
\nand that is all.<\/p>\n","protected":false},"excerpt":{"rendered":"

It has been noted that this router has a problem with the setup of the Remote Access feature of WHS. It plays nice with the UPnP protocol and the WHS reports as having setup the router successfully, but it turns out that there is a problem and the (name).homeserver.com is not accessible, pointing instead to … Continue reading Windows Home Server and the Thomson TG585v7 router<\/span> →<\/span><\/a><\/p>\n

<\/div>
<\/div>
 <\/span><\/svg><\/span><\/a> <\/span><\/path><\/rect><\/rect><\/svg><\/span><\/a> <\/span><\/path><\/svg><\/span><\/a> <\/span><\/path><\/svg><\/span><\/a> <\/span><\/path><\/svg><\/span><\/a> <\/span><\/path><\/svg><\/span><\/a> <\/span><\/svg><\/span><\/a> <\/span><\/path><\/path><\/path><\/svg><\/span><\/a> <\/span><\/svg><\/span><\/a> <\/span><\/g><\/svg><\/span><\/a> <\/span><\/path><\/ellipse><\/svg><\/span><\/a> <\/span><\/svg><\/span><\/a> <\/span><\/path><\/svg><\/span><\/a> <\/span><\/svg><\/span><\/a> <\/span>
<\/div><\/a><\/div><\/div>
<\/div>","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"footnotes":""},"categories":[11,12,13],"tags":[],"class_list":["post-91","post","type-post","status-publish","format-standard","hentry","category-computers","category-hardware","category-internet"],"aioseo_notices":[],"_links":{"self":[{"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/posts\/91","targetHints":{"allow":["GET"]}}],"collection":[{"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/comments?post=91"}],"version-history":[{"count":2,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions"}],"predecessor-version":[{"id":335,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/posts\/91\/revisions\/335"}],"wp:attachment":[{"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/media?parent=91"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/categories?post=91"},{"taxonomy":"post_tag","embeddable":true,"href":"http:\/\/www.seepyou.net\/blog\/wp-json\/wp\/v2\/tags?post=91"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}