RSS

FAQ: Windows Home Server and Port Forwarding

Tue, Jan 29, 2008 | Terry Walsh

Next up in the series of FAQs from the We Got Served forums is a common issue with router configuration. Windows Home Server has the ability to automatically configure many routers to permit access to your home server when away from home, using a technology called uPnP.

Unfortunately, not all routers are compatible with uPnP and indeed, some that say they are cannot be configured automatically by Windows Home Server, so it’s down to the user to manually configure the router using “port forwarding”.

Whilst this isn’t too difficult to do, it can be nerve-wracking for those who haven’t done it before, so FAQ has been published on the WGS forums to help you through it.

Can my router be automatically be configured for port forwarding?

The answer to that question is yes and no. The logical answer would be if it says so on the box of the router, you’ll get home, plug it in and have no trouble.
But unfortunately UPnP isn’t that efficient. It can be compared with the days when wireless networks first came out. If they weren’t made by the same person, they wont work.

Well, how do I know whether my router will be configured using UPnP?

Microsoft have released a very nice a piece of software for testing your router. To do so, you must make sure that UPnP is enabled. You can find out how to check this in your router handbook or by seeking the advice of the manufacturer. Microsoft’s testing tool is available here. Be warned, as mentioned by Darkone, it can take up to 10 minutes to run.

I ran Microsoft’s tool and my router passed, but it still doesn’t work. Why?

You’re not alone. There have been a handful of posts over on the Microsoft forums of people complaining that they cannot use UPnP even though their routers have passed. This means you’re going to have to configure them manually.

How do I do that?

I would first recommend that you give your home server a static ip address.

If you are letting your router assign an ip address using DHCP, it cant always be guaranteed that it will stay the same from day to day. You can follow the instructions in the Setting your own IP address FAQ here .

You need to then consult your Router’s manual to find out how you access its remote configuration website.

This is normally achieved by typing in your routers ip address, which is your default gateway, into your browser like you would a web address, e.g. 192.168.1.1

It will then prompt you for a password. This might be found on the bottom of your router, otherwise this will also be in the manual.

The ports that you will need to configure to enable remote access are port 80, port 443 and port 4125. To do this, you use something called port forwarding…….


Continue Reading:
Windows Home Server and uPnP (WGS Forums)

Subscribe to We Got Served: RSS | Email

Similar Posts:

This post was written by:

Terry Walsh - who has written 694 posts on We Got Served.

Hi - I'm Terry and I'm the Owner of We Got Served. The site's been covering everything to do with Windows Home Server since February 2007. I live in Silverstone, UK with my wife and when I'm not working on We Got Served, I have a career as an Innovation Consultant to contend with.

Contact the author

2 Comments For This Post

  1. Peter Says:

    I had trouble getting WHS to configure my router, a Xincom XC-DPG502, and it turned out the router had a limited number of UPnP port forwarding entries. After I deleted some unused entries, WHS successfully configured the router.

  2. rich ruscio Says:

    I see a lot of questions about routers which ‘just won’t work’ with WHS, but I’ve never seen anything that “really works well”.

    I have seen a couple of references to high-end Cisco routers, but, no thanks.

    Any pointers to routers that don’t allow the excuse that it’s the router’s fault for connector failures?

    Thank in advance,

    rr

Leave a Reply

Tags:
Separate individual tags by commas