Stuff to pimp your Windows Home Server

Hacking Windows Home Server is a blog dedicated to Microsoft's WHS technology. Brought to you by Donavon West, Microsoft MVP and author of LiveGadgets.net and donavon.com I'll also discuss the Hewlett-Packard HP MediaSmart Server EX470, EX475, EX485, EX487, the T7-HSA Tranquil Harmony Home Server and any other new Home Server hardware platforms that arise. You can also call this hacking or hackz. In any case I will show you some cool things to make your Microsoft Windows Home Server even sweeter.

A blog devoted to getting the most out of your
Windows Home Server by Microsoft MVP Donavon West.

Thursday, December 13, 2007

Configuring the Apple AirPort Extreme for use with WHS

image I have an Apple Airport Extreme Gigabit Edition and am using Windows Home Server (WHS). WHS allows remote access so that you can remote desktop into your home computers from anywhere. To do this, your router needs to be configured to open up certain ports. To do this, WHS used UPnP (Universal Plug and Play).

Unfortunately, the Apple Airport Extreme doesn't support UPnP. No big deal, I'll show you how to set it up manually.

  1. First we will need the MAC and IP addresses of the WHS box. We'll need to remote desktop into the WHS box to get it (you can skip to step 5 if you already know how).
  2. On your remote PC click Start and type mstsc and press enter. You should see a window like this: image
  3. Type in the name of your Home Server and click Connect. Mine is called "homeserver" (I'm very creative that way).
  4. You will be prompted for a username/password. Type administrator for the username and use the password that you setup initially.
  5. After you are remotely logged into your WHS bow, click Start, Control Panel, Network Connections, Local Area Connection.
  6. You should see a dialog appear. Click on the Support tab and then click Details. Note the Physical Address (i.e. MAC address) and IP address (yours will be different from mine). whs-mac-address
  7. Start up the AirPort Utility.
  8. Click on the Manual Setup button.
  9. First we will setup a DHCP reservation so that our WHS will always get the same IP address. Click on the Internet icon along the top, them on the DHCP tab. image
  10. Under DHCP Reservations, click the plus button.
  11. Under Description type in anything you like (e.g. "Home Server")
  12. Be sure the MAC Address radio button is checked and click Continue. image
  13. Type in the MAC address (don't type the dashes) and the last segment of your IP address and click Done. Your Home Server box will always get the same IP address. (Note: my IP address is 197, yours will likely be different). image
  14. Next we setup Port Forwarding so that HTTP, HTTPS and Remote Desktop requests from the Internet are routed to your WHS box. Click on the NAT tab, then of the Configure Port Mapping... button. image
  15. Click on the plus button under the Allow list box.
  16. Leave Services alone
  17. Under Public TCP ports type: 80, 443, 4125
  18. Leave Public UDC Ports blank
  19. Under Private IP Address, enter the IP address of your WHS box
  20. Under Private TCP ports type: 80, 443, 4125
  21. Leave Private UDC Ports blank
  22. Your dialog should look similar to this: image
  23. Click Continue

You have now configured HTTP, HTTPS and Remote Desktop services for Window Home Server in your Apple AirPort Extreme router. But let's test things out be make sure.

  1. imageGo to the Windows Home Server Console by double clicking the tray icon.
  2. After you log in, click on the Setting button in the upper right hand corner of the screen. image
  3. Then click on Remote Access. After a few seconds you should see a green check mark next to the Router icon and it should read "Manually configured". whs-settings

Fin. Why not comment on what you've just read or even Digg It!

Microsoft Social Bookmark on Microsoft Social

26 comments:

Anonymous said...

Hi,
I've made the same exact procedure that you wrote but not successfull for me... the only thing different is that my aiport utility is on my other computer laptop... (does it make a difference?)

Marcio Oliveira said...

If you are trying to access a computer that is not Windows Home Server, then the remote desktop connection port is different, it is 3389. The example show is for the Web Remote Desktop of WHS.

Tim Cooper said...

I was having issues as well and followed your procedure here to no avail. I ended up reading to turn off the Window Firewall and it found it and configured. Not sure if it was your steps or the Windows Firewall, but it's up and running now!

Ichiryan said...

I followed the steps exactly and am unable to get web access to work. This used to work, but after a router reset or something it stopped. I've also turned off the windows firewall per Tim's suggestion. The first and the last two steps of the Router Configuration details are showing errors if that helps. Anyone else have any suggestions. Thanks!

DBB said...

monkey magic kook obamma voter

Anonymous said...

I just bought an AirPort Extreme Gigabit router (to replace an older netgear). I also have an HP Media Smart Server with Windows Home Edition. Everything is working fine, I can navigate to folders on the server, from computers on the network, but I can't get the Home Server Console to connect. It says "Unable to connect to your home server. The following issues my cause this problem:
-Your home server is not powere on. IT IS.
-A firewall on this computer is blocking the connection I TURNED FIREWALL OFF
-A proxy server is configured on this computer for the network connection. NOT SURE WHAT THIS MEANS.

Any ideas what is going on here?

Unknown said...

I got this to work, i think, well my console says manually configured at least. Make sure in TC that you select TCP and not UDP because i had mine in UDP not realizing the locations were switched from above.

Unknown said...

I cant get this to work, followed the steps, and verified it several times. My setup is like ADSL+ router then Airport and then Homeserver.

Is it the adsl+ that need the configuration too?

Adamsonfoto said...

WHS and airporter is not working, I have followed all steps to no avail. I have switched off, All Firewalls, and still nothing, I have checked with my ISp and port to use is 80. What am I to do? I am stuck

Joe Santa said...

This worked perfectly for me.

Spamouflage said...

IT WORKED. Thank you so much!!!

Ken Thomas said...

Great article..My set up is slightly different...I have the airport extreme connected to an external hard drive that does not run WHS. I access the harddrive directly from the extreme. In this case, how can I access the drive remotely?
Any suggestions is quite welcome...
Thanks
Ken

Zazoo Pitts said...

Worked perfectly for me. Thank you very much!

Anonymous said...

Have you had any issues with this set up? Im considering this and the DIR-685. I have a Mixed laptop household. I might move to a Macpro to run bootcamp but still undecided

Unknown said...

This was very helpful thank you. It did not however work for me at first. I just purchased an HP EX490 and was trying to get the remote access configured with an Airport Extreme. I troubleshot this for about an hour. I believe the only thing that was incorrect in my configuration was the IP and MAC address for my Home Server. The process stated above for the 'Remote Desktop Connection' did not grab the correct IP and MAC for my home server. But, if you go through all the steps as stated above - THEN - go back into the 'Remote Access' screen within 'Settings' in Home Server Console you should see (under the 'Router' heading)your Home Server IP address and the Home Server physical (MAC) address. Just go back into the Airport setup and enter those addresses and all worked fine after that. Hope that helps.

kurkista said...

thank you so much, this hack made my day and saved me a lot of trouble! (iMac OS 10.6.2, Airport Extreme 7.4.2, HP MS 490EX)

Denzo said...

Worked PERFECTLY Thanks!!!!!

Boh Ruffin said...

Thanks! Worked beautifully!

Huab Lodge, Namibia - www.huab.com said...

it does not work for me. however, my setup is a litte different.
i have a mac computer living behind a time capsule router. my windows server is in a data centre and available at a public ip address. it has worked fine when using a mikrotik router but does not with time capsule at all. i can connect but i only get a black screen and there it hangs. i have setup port redirection as described for 80, 443, 4125, 3389 towards my mac up address without success. any idea?

Unknown said...

Worked perfectly for me! Steps 18 and 21 should read UDP and not UDC (but it doesn't change anything - just a tip for anyone unfamiliar with what's being done here and got concerned that they couldn't see UDC on the screen anywhere).

One other tip - the WHS mac address and current IP can be seen from the WHS console - settings - remote access. MAC == Home Server physical address.

Many thanks Donavon!

Nick

murphysclay said...

Rebooting the server worked for me after not working at first. Thanks!!!

Unknown said...

Wow! Totally worked. Just got the Airport Extreme and was freaking out that my HP Home Media Server wasn't available. Thank so much!

Anonymous said...

My Airport utility will not allow me to enter more than one port in to the Public or Private TCP ports. When I do it won't give me the continue button. Please advise!

Unknown said...

24+ hours of trial and error. Mainly error. Then, I found your blog. THANK YOU! Worked perfect (used port 3389). I'm using Parallels to run a virtual machine (Windows 7) on a Mac Mini OS X Server. The idea is to run QuickBooks Enterprise in the virtual machine and allow remote Mac users to access using remote desktop.

By the way, Parallels 6 is awesome.

Unknown said...

Be sure to check that if you have static ip addresses configured, if it changes your beginning DHCP than those computers with static wont connect. you have to just change it and it will adjust the settings you just made for whs accordingly

mikegilroy said...

Will not let me get passed port mapping.. When i enter the privet TCP port is says " the port mapping you entered already exists"

Post a Comment