GoToMyPC - Access Your PC From Anywhere

Are you interested in improving your home set-up but need some new ideas? If so, take a look Juan Goni’s master set-up in this edition of Show us Your Tech.

As a reminder, the Windows Home Server team has partnered with Microsoft’s Channel 9 , a video blog site that reaches of 5 million technology enthusiasts to revive a series called “Show Us Your Tech”. Similar to MTV Cribs, Show us Your Tech takes a look inside people’s homes. However, instead of looking in their fridge, it showcases some pretty elaborate technology set-ups that feature Windows Home Server.

In this edition, you will see Juan Goni’s set-up. Juan is a senior Program Manager at Microsoft in the Exchange Online Deployment group who has used Windows Home Server to connect his digital life and use it throughout his house. Juan has some pretty cool features in his set-up including the ability to control his home’s lighting with his PC, and also uses Media Center and extenders throughout his house to distribute video and music.

Check it out and get some new ideas for your own home!

http://channel9.msdn.com/posts/LarryLarsen/Show-Us-Your-Tech-Juan-Goni-Edition/

Enjoy!

-Nicole

Last weekend, I decided to go out and buy a new PC for at home. This PC would be used only as a “work PC” for when I do work at home. Sure, I could use my laptop but I’m sort of still a desktop guy. A lot of PC shopping happens online. Folks like Dell, HP, and many others have fantastic websites designed to give the consumer everything they need to make a purchasing decision for a PC. But a lot of PC shopping happens physically in stores too. I decided instead of ordering online, I would visit a local Best Buy and make my purchase there (of course if I found a PC I liked!).

I set out to find a PC based on the following criteria: doesn’t have to be a super powerful PC, has to be relatively low priced (around $500), had to have a small form factor (a desktop PC not a laptop), and had to carry the Windows 7 logo.

EN-w7_rgb_L

I wanted to primarily use this PC for blogging, email, and a bunch of scenario, hardware and software testing that I would end up blogging about. This PC wouldn’t be doing anything intensive like HD video editing.

I wanted in to Best Buy and went straight over to the Computers. I asked one of the Best Buy folks where I could find the small form-factor desktop PCs. He pointed me in the right direction. They had a row of tables with desktop PCs on them and section specifically for small-form factor desktop PCs. For most of their PCs, Best Buy puts out a label that has its price as well as hardware configuring usually listing a PCs processor, how much memory it has, how much storage (hard drive) it has, and sometimes graphics. I went an analyzed a few of these labels and weighed in spec and price for a few PCs. In the end – I found the perfect PC that met my needs exactly: the HP Pavilion (s5310y) Slimline PC.

DSC_0067 DSC_0069 

The HP Pavilion Slimline PC came with the following specs:

*Up to 256MB of system memory may be allocated to support graphics. This may result in Windows 7 reporting that you have 4GB of memory but 3.75GB “usable”.

**What exactly is LightScribe? Here’s a good explanation.

DSC_0072 DSC_0071

The PC is small, and slim which it gets its name from. It’s about 4 inches wide (thick), 12 inches tall (when standing up), and 15 inches deep (from front to back). It’s exactly what I needed to sit on a small shelf next to my desk next to my Windows Home Server.

DSC_0074

Total cost for the PC was $509.99. Not bad. Just about what had been expecting to spend.

For work, I needed to join this PC to the corporate Microsoft domain. This allows me to enjoy access to our internal Microsoft stuff. However, the PC ships with Windows 7 Home Premium which does not allow for domain join. I ended up picking up a copy of Windows Anytime Upgrade to move from Windows 7 Home Premium to Windows 7 Professional.

DSC_0076

Moving from Windows 7 Home Premium to Windows 7 Professional was extremely easy. Essentially the Windows Anytime Upgrade package provides you with a product key. This product key enables the upgrade to happen. On the PC I purchased with Windows 7 Home Premium, I went to the Start Menu and All Programs and chose Windows Anytime Upgrade. There I entered the key I had and the upgrade commenced.

1

The upgrade was pretty quick (took 2 reboots). I am now running Windows 7 Professional.

2

The rest of the evening I spent time downloading and installing the Microsoft Office 2010 Beta and setting the PC up just the way I want it (Windows Live Essentials, Zune, etc.). I joined it to the domain; Outlook 2010 picked up our corporate Exchange 2010 server and downloaded all my email. I now have a nice little work PC here in my home office!

From going to the store, buying the PC, and upgrading it to Windows 7 Professional, took less than 2 hours. I had a great experience – hope when you go out shopping for a PC it’s a great experience too!

This blog post was written by MVP, Alexander Kent.  Alexander is the founder and principal of Kentdome LLC, a Los Angeles, California based company specializing in enterprise security, custom software engineering, network infrastructure and co-location services. In recent years Alexander has taken a particular interest in the Windows Home Server platform. As a result, Kentdome LLC has produced a number of WHS solutions under his architectural guidance. In addition Alexander has been a very active technology evangelist, sharing his excitement for the WHS platform. Today he will share some information about Remote Access challenges.  Enjoy!

Windows Home Server is generally considered a great file server and backup solution for home users. A lesser known fact is that it also provides superb Remote Access capabilities. The “Remote Access” feature allows you to control your computers and access files on your Windows Home Server over any internet connection, from anywhere in the world.

Have you ever traveled somewhere and realized that important files were left at home? Now, with the help of the Windows Home Server Remote Access technology, you can securely reach your home network and interact with it from any machine on the Internet.

Enabling the Remote Access feature prompts the Windows Home Server to try and automatically configure the network to allow inbound connections. Seven times out of ten times this works perfectly, but given the sheer number of different devices, and the ever increasing complexity of home networks, the process of configuring your network for Remote Access may have to be more hands on.

This article explains the most frequent Remote Access challenges and then walks you through the steps of making your Windows Home Server accessible across the Internet.

#1) UPnP is not enabled or supported by your router
The Windows Home Server Remote Access Configuration Wizard attempts to auto configure your router over universal plug and play (UPnP) standards. UPnP represents a set of networking protocols that allow devices to connect, interoperate, and be configured. In order for this to work, your router must have the UPnP feature enabled, and must support the correct UPnP version.

If your router does not support the UPnP protocol, or if your router has UPnP disabled, then the Windows Home Server Remote Access Wizard will report a failure when attempting to configure the router through the Remote Access settings interface.

image

Figure 1.0: Router configuration failed

In many cases, downloading and installing a firmware update on the router adds UPnP support or fixes UPnP issues. If you have not done any firmware updates, visit your router manufacturer’s website to see if any updates are available. We recommend installing the firmware update, enabling UPnP on your router (if applicable), and try running the Windows Home Server Remote Access Configuration Wizard again.

In some cases, Windows Home Server will report an error with the automatic router configuration, but the Remote Access functionality proceeds to work without a problem. This occurs in cases where the UPnP protocol may not be implemented properly on the router and Windows Home Server cannot confirm whether or not configuration was successful.

image

Figure 2.0: Router configuration failed but remote Web site is available from the Internet. (Okay to proceed!)

If the above information does not solve your problem or UPnP is not available on your router, then you must manually configure port forwarding from your router to your Windows Home Server. To learn more, please visit the Broadband Router Configuration wiki produced by the Home Server Land team in conjunction with the Windows Home Server Remote Access feature team at Microsoft.

WHS Remote Access UPnP Problems from HomeServerLand on Vimeo.

#2) Double NAT

Network Address Translation (NAT) refers to the translation of an Internet Protocol address (IP address) used within one network to a different IP address known within another network. For example, a translation from the Local Area Network (LAN: the private home network) to the Wide Area Network (WAN: the public Internet).

A good example of a NAT device is the network router which can be thought of as the agent between the public Internet and the private home network.

A typical home network is made up of a single network router (NAT), usually with a built-in 4-port switch, and a basic DSL or Cable modem that connects to the Internet.

image

Figure 3.0: Typical Home Network Diagram

For the Windows Home Server Remote Access website to be available from the Internet, the router needs to be configured to forward inbound web traffic from the Internet to the Windows Home Server on the local network. Therefore, if another NAT device is introduced into the network, it too must be configured accordingly!

A home network containing two devices routing traffic and performing Network Address Translation is known as a Double NAT. Such devices can include a combination of routers, modems, firewalls, wireless access points, and other network devices.

What people often fail to realize is that DSL Modems that employ Point-to-Point Protocol over Ethernet (PPPoE) are frequently performing NAT and other roles such as Internet authentication and DHCP functions.

image

Figure 4.0: Double NAT network diagram

In a Double NAT environment, the UPnP protocol can only be used to automatically configure the nearest NAT device. Under these conditions, the Remote Access functionality will not work properly, and the Windows Home Server will report a failure when attempting to configure the router through the Remote Access Settings interface.

How do I know if I am behind a double NAT?
To determine whether or not a Double NAT exists, check the WAN (outside) IP address on the router nearest to the Windows Home Server. It should match the public IP address assigned by your Internet Service Provider (ISP). One way to check your public IP address is by visiting a site like http://whatismyipaddress.com/ from your home network.

If the WAN IP address on the router nearest to the Windows Home Server is a private IP address, meaning a non-routable IP address reserved for private use, you are dealing with a Double NAT scenario.

image

Figure 5.0: IP Address ranges reserved for private use

The solution would be to reconfigure your home network so that only one device is routing data in a NAT configuration. Many network devices, including Cable and DSL modems, support a “bridged” or "transparent" mode of operation, which disables all of the routing and NAT in the device. This effectively puts your other router into the position of managing the Internet authentication and network address translation. Consult your modem manufacturer documentation or contact your ISP for support.

Another common network setup mistake is made by people who wish to add wireless functionality without replacing their existing modem or router. As a result, if you attach another router behind or in-front of your existing router, you are effectively creating a Double NAT.

image

Figure 6.0: Double NAT by means of two routers

In this case, the solution would be to consolidate both devices into a single unit that can route traffic to the wired and wireless networks, or to configure port forwarding from the first NAT device to the second NAT device. Alternatively, circumvent the double NAT by attaching the Windows Home Server directly to the first NAT device on the network.

WHS Remote Access: Double NAT from HomeServerLand on Vimeo.

#3) Internet Service Provider is blocking Remote Access Ports

The Remote Access website requires inbound port 80 (HTTP), port 443 (HTTPS) and port 4125 (Remote Web Workplace or RWW for short) to be available from the Internet. However, many internet service providers block email related internet ports to curb spam or unsolicited commercial usage. In some cases ISPs block additional ports such as the ones required by Windows Home Server Remote Access: inbound port 80 and port 443.
If you have configured your network for Remote Access but the remote access website is still not available over the Internet, then contact your ISP to confirm whether or not inbound connectivity on TCP ports 80, 443 or 4125 are being blocked.

Alternatively you can determine whether or not ports are blocked with the Internet Connectivity Evaluation Tool.

WHS Remote Access: ISP Blocking Ports from HomeServerLand on Vimeo.

The Windows Home Server Remote Access functionality is a powerful and convenient feature that is well worth the effort to set up correctly and securely.

Hopefully the above breakdown of some of the most common Windows Home Server Remote Access challenges has been helpful. The Windows Home Server Remote Access feature team at Microsoft and the WHS communities are continuously engaged in improving and compiling data around compatibility and other home network issues. Feedback is always welcome and should you need additional help, please give us a shout in the forums where we can help you further.

-Alexander Kent

« go backkeep looking »
eXTReMe Tracker