Wikis

Windows Home Server

Anonymous — Thu, 11 Mar 2010 08:00:00 GMT

WHS Tutorials, Walkthroughs, Tips & Tricks

RPC Server Unavailable Error 0x800706ba

Alexander Kent (HSL) — Fri, 26 Feb 2010 08:00:00 GMT

The Windows Firewall (formerly known as Internet Connection Firewall) service and Distributed Component Object Model (DCOM) can cause access denied errors (such as an "RPC Server Unavailable" error - 0x800706ba) when trying to use the Grid Junction Custom Action scripts to shutdown remote clients using WMI scripts.

The solution to fix the RPC Server Unavailable" error - 0x800706ba, log in as Administrator and click on Start – Run and type:

Netsh firewall set service RemoteAdmin

[Thanks Andrew Hemming]

Note: Windows 7 responds with the following:

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
C:\Windows\system32>netsh firewall set service RemoteAdmin
IMPORTANT: Command executed successfully.
However, "netsh firewall" is deprecated;
use "netsh advfirewall firewall" instead.
For more information on using "netsh advfirewall firewall" commands
instead of "netsh firewall", see KB article 947709
at http://go.microsoft.com/fwlink/?linkid=121488 .
Ok.

You may need to use netsh advfirewall firewall set rule group="remote admin" new enable=Yes wilst logged in as the Administrator, or use the "Run as Administrator" option for the Command Prompt.

Alternatively on Windows 7, you can go into the Windows Firewall, click on "Advanced Settings" and click on Inbound Rules. Locate the Remote Administration (NP-in) and Remote Administration (RPC) entries. Click on Properties (for each one) and then click on the Scope Tab. Check Domain. Click OK.

[Thanks Patrick]

Remote Desktop Connection to WHS

Tink — Sun, 21 Feb 2010 08:00:00 GMT

This article discusses how to establish a Remote Desktop connection to your Windows Home Server.

The term Remote Desktop refers to graphical applications to be run remotely on a server. In essence, the remote desktop and all of the software applications which are located on the remote server are being displayed locally.

To establish a Remote Desktop connection to your Windows Home Server, follow these steps:

Click Start, click All Programs, click Accessories, click Communication, and then click Remote Desktop Connection. Or alternatively, in click Start, click Run or via the Search program and files field enter mstsc.exe , hit the Enter key.
Enter your Windows Home Server computer name, for example SERVER and click the Connect button.
Enter your Windows Home Server administrative credentials, the username will be Administrator and the password will be the password you use to connect to the Windows Home Server Console.
The Remote Desktop window opens, and you see the desktop settings, files, and programs that are on your host computer, which in this example is your work computer. Your host computer remains locked, and nobody can access it without a password. In addition, no one will be able to see the work you are doing remotely.

To end your Remote Desktop session:

Click Start, and then click Log Off at the bottom of the Start menu.
When prompted, click Log Off.

QSMMgr Storage Manager

SmurfCream — Sat, 20 Feb 2010 08:00:00 GMT

The QSMMgr class is located in HomeServerControls.dll and exposes a lot useful storage related functionality.

Warning
Many of these assemblies are not supported and not documented by Microsoft.

The class QSMMgr is located in namespace Microsoft.HomeServer.Controls.QSM which exposes a number of interesting methods:

void AddDisk(Disk currDisk, bool isStorage, System.Windows.Forms.Control parentControl, QSMReportDelegate callback);
void CreateConfigDataFile(string mountPath);
void DeleteConfigDataFile(string mountPath);
void FormatDisk(Disk currDisk, string newLabel, System.Windows.Forms.Control parentControl, QSMReportDelegate callback);
long GetAppFoldersSize();
long GetBackupSize();
Disk[] GetDisks();
string GetGlobalStatus();
long GetOperatingSystemSize();
ShareConnection[] GetShareConnections();
void GetSharedFoldersSize(out long size, out long dupSize);
long GetStorageFreeSpace();
long GetStorageSize();
long GetStorageUsedSpace();
void Init();
void PreviewDisk(Disk currDisk, System.Windows.Forms.Control parentControl, QSMReportDelegate callback);
void RegisterForDiskEvents(System.Windows.Forms.Control parentObj, Delegate eventDelegate);
void RegisterForFolderEvents(System.Windows.Forms.Control parentObj, Delegate eventDelegate);
void RegisterForGlobalEvents(System.Windows.Forms.Control parentObj, Delegate eventDelegate);
void RegisterForQsmEvents();
void RegisterForShareEvents(System.Windows.Forms.Control parentObj, Delegate eventDelegate);
void RemoveDisk(Disk currDisk, System.Windows.Forms.Control parentControl, QSMReportDelegate callback, bool removeIfMissing);
void RepairDisk(Disk currDisk, System.Windows.Forms.Control parentControl, QSMReportDelegate callback);

U-Verse 2Wire Residential Gateway

scrounger_ — Wed, 17 Feb 2010 08:00:00 GMT

CONFIGURE U-VERSE 2WIRE ROUTER FOR WINDOWS HOME SERVER REMOTE ACCESS

The U-Verse 2Wire Residential Gateway does not support the Windows Home Server automatic router configuration over UPnP standards. 2Wire provides home-networking gear via Internet Service Providers (ISPs) like AT&T, BellSouth, Verizon and Qwest. The following static Port Forwarding to your Windows Home Server instructions should work for most 2Wire Residential Gateway routers.

Overview

Log on to your router’s setup page
Create IP Address reservation for your Windows Home Server
Configure Port Forwarding to your Windows Home Server

STEP 1 - Log on to your router’s setup page

Open your web browser and enter your router’s URL

http://gateway.2wire.net/ is the default 2Wire router setup URL. Or http://192.168.1.254

STEP 2 - Create IP Address reservation for your Windows Home Server

a) In the control panel click the Home Network icon at the top, then Advanced Settings. You will be prompted for a password, by default it is on a sticker on the side of the residential gateway.

b) Click the Edit Address Allocation button.

c) Find your server by name and change the Address Assignment to Private Fixed and click on “Save”. Make a note of the private fixed IP address.

STEP 3 - Create an IP Address reservation for your Windows Home Server

a) Click the Firewall icon at the top of the screen and then click on Firewall Settings

b) Select your Windows Home Server by IP address in the “select a computer” box
• In “Edit firewall settings for this computer” select “Allow Individual Applications”
• Click “Add a new user-defined application”

In the Edit Application dialog:

enter the application name, set the protocol to TCP, enter 80 in the port from box and click Add Definition.
After the first port is added, enter 443 in the port from box and click Add Definition.
Finally repeat the last step using port 4125 and clicking Add Definition.
Press the back button to return to the previous screen.
Make sure the correct computer is selected and edit firewall settings for this computer is set to Allow individual applications. Add your new firewall exclusion to the Hosted Applications box by highlighting it and clicking Add. Then click Done.
The View Firewall Summary will show your new exclusion and the IP address it is associated with.

All done! After you configured your U-Verse 2Wire Residential Gateway for Remote Access you should test the remote connectivity from within your home and from outside of your home.

Shutdown Remote PC via Grid Junction

peter_k — Thu, 28 Jan 2010 08:00:00 GMT

You may use the following script as a starting point to define a custom Grid Junction action to logoff, reboot or shutdown another remote PC. This may be useful if you share a UPS between your Windows Home Server and another PC; per custom action event trigger (battery, critical, shutdown) to shutdown both your WHS and your remote PC providing your network switch or router is operational during a power failure.

'
' LOGOFF/REBOOT/SHUTDOWN REMOTE PC
'********************************
'Author: Alexander Kent
'Date: 12/30/20008
'Web: http://www.kentdome.com
'
'Use this script as an example how to logoff,
'restart or shutdown a remote PC computer.
'DO NOT RUN this shutdown code against another
'Windows Home Sever!
'
'User credentials must have permissions to the WMI database,
'and of course to be able to reboot the station.
'
'References: http://msdn.microsoft.com/en-us/library/9bbdkx3k(VS.85).aspx
'
'
Dim strComputer, OperationMode, strUsername, strPassword

'Remote computername or IP
strComputer="10.0.0.133"

'Specify the OperationMode (0 = Restart, 1 = Logoff, 2 = Shutdown)
OperationMode = 2

'Credentials
strUsername = "Administrator"
strPassword = "password"

'put computername into uppercase
strComputer = UCase(strComputer)

'Perform the operation on remote PC
Call OperationAction

Sub OperationAction
    On Error GoTo 0
    Set objSWbemLocator = CreateObject("WbemScripting.SWbemLocator")
Set objSWbemServices = objSWbemLocator.ConnectServer _
      (strComputer, "root\cimv2", strUsername, strPassword)
objSWbemServices.Security_.ImpersonationLevel = 3

'Call WMI query to collect parameters for reboot action
    'Set OpSysSet = GetObject("winmgmts:{(Shutdown)}//"_
     '& strComputer & "/root/cimv2").ExecQuery("select * from Win32_OperatingSystem"_
     '& " where Primary=true")

Set OpSysSet = objSWbemServices.ExecQuery("select * from Win32_OperatingSystem"_
& " where Primary=true")

Dim OpSysSet, OpSys

'Set PC to reboot
If OperationMode = 0 Then
        For each OpSys in OpSysSet
            opSys.Reboot()
        Next

'Set PC to logoff
ElseIf OperationMode = 1 Then

        Const EWX_LOGOFF = 0
        For each OpSys in OpSysSet
            opSys.win32shutdown EWX_LOGOFF
        Next

'Set PC to shutdown
ElseIf OperationMode = 2 Then
        For each OpSys in OpSysSet
            opSys.Shutdown()
        Next

End If
End Sub

Broadband Router Configuration

Alexander Kent (HSL) — Fri, 22 Jan 2010 08:00:00 GMT

The following router configuration guides are provided to help you configure your broadband router or firewall appliance for Windows Home Server Remote Access.

If you encounter any errors in our guides, or wish to contribute please let us know.

Choose your router:

	U-Verse 2Wire Residential Gateway

	Apple AirPort Extreme N Router

	Belkin G+ MIMO (F5D9231-4) Router Belkin N1 Vision (F5D8232-4) Router Belkin Wireless G (F5D7230-4) Router

	Buffalo WHR-G300N Router Buffalo WHR-HP-G54 Router

	D-Link DGL-4100 Router D-Link DGL-4300 Router D-Link DGL-4500 Router D-Link DIR-615 Router D-Link DIR-625 Router D-Link DIR-628 Router D-Link DIR-655 Router D-Link DI-604 Router

	Vigor 2820 Series Router


	IPCOP Firewall

	Linksys BEFSR41 Router Linksys BEFSX41 Router Linksys RVS4000 Router Linksys WAG320N Router Linksys WRT110 Router Linksys WRT120N Router Linksys WRT150N Router Linksys WRT160N Router Linksys WRT300N Router Linksys WRT310N Router Linksys WRT320N Router Linksys WRT350N Router Linksys WRT400N Router Linksys WRT54G Router Linksys WRT54G2 Router Linksys WRT54GS Router Linksys WRT610N Router Linksys WRVS4400N Router

	Netgear FVS338 Router Netgear WNR3500 Router Netgear WNR854T Router Netgear WPNT834 Router

	Sagem BSKYB Router

	SonicWALL NSA 240 Appliance SonicWALL NSA 2400 Appliance SonicWALL TZ 210 Appliance

	Westell 327W DSL Gateway

Netgear FVS338 Router

Alexander Kent (HSL) — Fri, 22 Jan 2010 08:00:00 GMT

CONFIGURE NETGEAR FVS338 ROUTER FOR WINDOWS HOME SERVER REMOTE ACCESS

The Netgear ProSafe VPN Firewall FVS338 router does not support the Windows Home Server automatic router configuration over UPnP standards. This means that you must manually configure port forwarding on your router to point port TCP 80, 443 and 4125 to your Windows Home Server.

Manufacturer: Netgear
Model: FVS338
Firmware Version: V1.6.47

Overview

Log on to your router’s setup page
Enable UPnP (Universal Plug and Play)
Create IP Address reservation for your Windows Home Server
Configure Port Forwarding to your Windows Home Server

STEP 1 - Log on to your router’s setup page

Open your web browser and enter your router’s URL

http://192.168.0.1 or http://192.168.1.1

For Netgear routers -by default the username is admin, and the password is password. If you have changed the defaults, then enter your corresponding information.

If you have forgotten your router password, you may reset the router by pressing and holding for a few seconds the reset button located on the router itself.

STEP 2 - Enable UPnP (Universal Plug and Play)

In respect to the Netgear FVS338 this step is optional and the results appear to be mediocre at best. The stock firmware does not provide the UPnP option but newer router firmware available from the Netgear website free of charge adds UPnP functionality to the FVS338. To configure your network and router for Remote Access it is recommended to configuration static port forwarding.

Applicable only to the newer firmware(s) and may not be available in all regions. The UPnP option may be enabled under Security -> UPnP.

STEP 3 - Create IP Address reservation for your Windows Home Server

a) In the top navigation bar click on the Network Configuration and then LAN Setup area. Next, open the DHCP Log to open a small window displaying all the current IP leases. We will use this window to find the Ethernet MAC address of the Windows Home Server.

b) Find and note your Windows Home Server's MAC address, for example 00-B0-D0-86-BB-F7

Then go back to Network Configuration -> LAN Setup and ensure the DHCP Server option is enabled.

c) Under the Network Configuration section, click on LAN Groups, and reserve an IP address for your Windows Home Server under the Add Known PCs and Devicesarea. Use your WHS's MAC address identified earlier and ensure the IP Address Type is set to Reserved (DHCP Client).

STEP 4 - Configure Port Forwarding

The Windows Home Server remote access feature requires you to forward port 80, port 443 and port 4125. To do so, click on the Security link near the top of the screen.

a) Enter the following service information:

Name: HTTP
Type: TCP
StartPort: 80
EndPort: 80

Click “ADD”

Name: HTTPS
Type: TCP
StartPort: 443
EndPort: 443

Click “ADD”

Name: RWW
Type: TCP
StartPort: 4125
EndPort: 4125

Click “ADD”

b) Click the Firewall Rules link near the top of the screen and create the three rules for incoming traffic (Remote Access) to your Windows Home Server. To do so, click on Add under Inbound Services, select the HTTP service we defined earlier with the ALLOW always action rule specify the Windows Home Server IP address under Send to LAN server. Repeat this for the HTTPS and RWW services.

All done! After you configured your Netgear FVS338 router for Remote Access you should test the remote connectivity from within your home and from outside of your home.

Configure Windows Home Server Remote Access

Alexander Kent (HSL) — Tue, 15 Dec 2009 08:00:00 GMT

[View:http://vimeo.com/8163403:640:480]

How you configure the Remote Access feature in Windows Home Server

One of the main features of a Windows Home Server (WHS) is to provide Remote Access to your data and home network from anywhere in the world where there is internet access available. In this wiki we will illustrate how you configure the Remote Access feature in Windows Home Server.

To begin, open the Windows Home Server Console and click Settings in the top right corner to open the Settings window. In the Windows Home Server Settings dialog window navigate to the Remote Access section and click on the Turn on button to start the Remote Access configuration wizard.

The Remote Access wizard will attempt to auto configure your router using UPnP standards to forward port 80, port 443 and port 4125 from your WAN (Internet) to your Windows Home Server on your LAN.

The Remote Access configuration wizard will attempt to verify that your remote Web site is available locally and remotely. If your router does not support UPnP standards you must manually configure static port forwarding –please take a look at the Broadband Router Configuration wikis for detailed instructions on how to configure port forwarding for many popular router manufacturer and models.

If you already had a domain name configured and your remote Web site is available from the Internet you will receive the Remote Access Successfully Activated dialog.

Domain Name Setup Wizard

If you have not yet configured a remote access domain name for your Windows Home Server the Domain Name Setup Wizard will launch.

WHS Original Equipment Manufacturer (OEM’s) ship with additional Domain Name Providers, but for the purpose of this wiki we will choose the “Windows Live Custom Domains” domain name provider which is provided free-of-charge by Microsoft. To proceed and register your remote access domain name you need to first sign into Windows Live with your Windows Live ID.

The “Choose a Domain Name” section allows you to pick a unique domain name which will be used to access your Windows Home Server remotely. You can quickly check if the chosen name is available by clicking on the Confirm button. To proceed, click on Finish and close the domain name wizard.

The domain name is used to connect to your home server while you are away from home. For example, we registered happyelf.homeserver.com for our home server. When we are away from home we can open our Web browser and type happyelf.homeserver.com in the address text box to connect to the Remote Access website on our Home Server.

Supported Uninterruptible Power Supply

Alexander Kent (HSL) — Mon, 30 Nov 2009 08:00:00 GMT

The following is a user-submitted list of tested uninterruptible power supply (UPS’s), these devices have been verified to work with Grid Junction.

WARNING!
Installing or using the built in UPS power management software is NOT supported on the Windows Home Server platform. Furthermore please do not install any UPS management software i.e. APC Powerchute or CyberPower PowerPanel on your Windows Home Server - unless explicitly designed for WHS usage - doing so may cause premature system shutdowns and a wide range of errors and is NOT supported and will NOT work with Grid Junction. Always ensure you are using the correct signaling interface cable.

American Power Conversion (APC)

APC ES 725 FW:821.y1.A USB FW:y1
Back-UPS 350 FW: 5.1.D USB FW: c1
Back-UPS 350 FW: 5.2.I USB FW: c1
Back-UPS 350 FW: 5.3.I USB FW: c1
Back-UPS 350 FW: 5.4.D USB FW: c1
Back-UPS 350 FW: 5.4.I USB FW: c1
Back-UPS 350 FW: 5.5.D USB FW: c1
Back-UPS 350 FW: 5.5.I USB FW: c1
Back-UPS 500 FW: 6.4.D USB FW: c1
Back-UPS 500 FW: 6.4.I USB FW: c1
Back-UPS 500 FW: 6.5.I USB FW: c1
Back-UPS BF350 FW:813.s3.IUSB FW:s3
Back-UPS BF500 FW:814.s3.IUSB FW:s3
Back-UPS BR800 FW:9.o2 .D USB FW:o2
Back-UPS BR800 FW:9.o2 .I USB FW:o2
Back-UPS BR800 FW:9.o3 .D USB FW:o3
Back-UPS BR800 FW:9.o4 .D USB FW:o4
Back-UPS BR800 FW:9.o4 .I USB FW:o4
Back-UPS BR800 FW:9.o5 .I USB FW:o5
Back-UPS BX1300G FW:864.L1 .D USB FW:L1
Back-UPS BX1500G FW:866.L1 .D USB FW:L1
Back-UPS CS 350 FW:805.q8.D USB FW:q8
Back-UPS CS 350 FW:807.q3.I USB FW:q3
Back-UPS CS 350 FW:807.q5.I USB FW:q5
Back-UPS CS 350 FW:807.q7.I USB FW:q7
Back-UPS CS 350 FW:807.q8.I USB FW:q8
Back-UPS CS 500 FW:806.q8.D USB FW:q8
Back-UPS CS 500 FW:808.q3.I USB FW:q3
Back-UPS CS 500 FW:808.q5.I USB FW:q5
Back-UPS CS 500 FW:808.q8.I USB FW:q8
Back-UPS CS 650 FW:817.v2.I USB FW:v2
Back-UPS CS 650 FW:817.v3.I USB FW:v3
Back-UPS CS 650 FW:817.v4.I USB FW:v4
Back-UPS ES 350 FW:1.e2.D USB FW:e2
Back-UPS ES 350 FW:800.e3.D USB FW:e3
Back-UPS ES 350 FW:800.e5.D USB FW:e5
Back-UPS ES 350 FW:800.e6.D USB FW:e6
Back-UPS ES 350 FW:823.B1.D USB FW:B1
Back-UPS ES 350 FW:823.B1a.D USB FW:B1a
Back-UPS ES 450 FW:844.K1 .D USB FW:K1
Back-UPS ES 450 FW:844.K1d.D USB FW:K1d
Back-UPS ES 450 FW:844.K2 .D USB FW:K2
Back-UPS ES 500 FW:2.e2.D USB FW:e2
Back-UPS ES 500 FW:801.e5.D USB FW:e5
Back-UPS ES 500 FW:801.e6.D USB FW:e6
Back-UPS ES 500 FW:824.B1.D USB FW:B1
Back-UPS ES 525 FW:851.t2.I USB FW:t2
Back-UPS ES 550 FW:828.D1.I USB FW:D1
Back-UPS ES 550 FW:828.D2 .I USB FW:D2
Back-UPS ES 550 FW:828.D2.I USB FW:D2
Back-UPS ES 550 FW:828.D3 .I USB FW:D3
Back-UPS ES 550 FW:840.B2.D USB FW:B2
Back-UPS ES 550 FW:840.B3.D USB FW:B3
Back-UPS ES 550 FW:843.K1 .D USB FW:K1
Back-UPS ES 550 FW:843.K1d.D USB FW:K1d
Back-UPS ES 550 FW:843.K2 .D USB FW:K2
Back-UPS ES 650 FW:818.w1.D USB FW:w1
Back-UPS ES 650 FW:825.B1.D USB FW:B1
Back-UPS ES 650 FW:842.J1 .D USB FW:J1
Back-UPS ES 650 FW:842.J2 .D USB FW:J2
Back-UPS ES 650 FW:842.J3 .D USB FW:J3
Back-UPS ES 650Y-IN FW:853.m4.I USB FW:m4
Back-UPS ES 700 FW:829.D2 .I USB FW:D2
Back-UPS ES 700 FW:829.D2.I USB FW:D2
Back-UPS ES 700 FW:829.D3 .I USB FW:D3
Back-UPS ES 725 FW:802.n2.D USB FW:n2
Back-UPS ES 750 FW:819.z2.D USB FW:z2
Back-UPS ES 750 FW:819.z3.D USB FW:z3
Back-UPS ES 750 FW:841.I1 .D USB FW:I1
Back-UPS ES 750 FW:841.I2 .D USB FW:I2
Back-UPS ES 750 FW:841.I3 .D USB FW:I3
Back-UPS LS 500 FW:16.b2 .D USB FW:b2
Back-UPS LS 500 FW:16.b3 .D USB FW:b3
Back-UPS LS 700 FW:19.b3 .D USB FW:b3
Back-UPS LS 700 FW:19.b4 .D USB FW:b4
Back-UPS LS 700 FW:19.b6 .D USB FW:b6
Back-UPS NS 1050 FW:7.g2 .D USB FW:g2
Back-UPS NS 1050 FW:7.g3 .D USB FW:g3
Back-UPS NS 1050 FW:7.g4 .D USB FW:g4
Back-UPS NS 1250 FW:7.g1 .D USB FW:g1
Back-UPS NS 1250 LCD FW:846.H1a.D USB FW:H1a
Back-UPS NS 1250 LCD FW:846.H2 .D USB FW:H2
Back-UPS NS 600 FW:818.w1 .D USB FW:w1
Back-UPS Office 500 FW: 4.3.D USB FW: d1
Back-UPS Pro 350 FW:15.5.D USB FW:a7
Back-UPS Pro 500 FW:16.4.D USB FW:a6
Back-UPS RS 1000 FW:7.g2 .D USB FW:g2
Back-UPS RS 1000 FW:7.g3 .D USB FW:g3
Back-UPS RS 1000 FW:7.g4 .D USB FW:g4
Back-UPS RS 1000 FW:7.g7 .D USB FW:g7
Back-UPS RS 1000 FW:7.g8 .D USB FW:g8
Back-UPS RS 1000 FW:7.g8 .I USB FW:g8
Back-UPS RS 1000 FW:7.g9 .D USB FW:g9
Back-UPS RS 1000 FW:7.g9 .I USB FW:g9
Back-UPS RS 1200 FW:8.g1 .D USB FW:g1
Back-UPS RS 1200 FW:8.g3 .D USB FW:g3
Back-UPS RS 1300 LCD FW:838.H7 .D USB FW:H7
Back-UPS RS 1500 FW:8.g2 .D USB FW:g2
Back-UPS RS 1500 FW:8.g4 .D USB FW:g4
Back-UPS RS 1500 FW:8.g6 .D USB FW:g6
Back-UPS RS 1500 FW:8.g7 .D USB FW:g7
Back-UPS RS 1500 FW:8.g8 .D USB FW:g8
Back-UPS RS 1500 FW:8.g9 .D USB FW:g9
Back-UPS RS 1500 FW:8.g9 .I USB FW:g9
Back-UPS RS 1500 FW:8.g9a.D USB FW:g9a
Back-UPS RS 1500 FW:8.g9a.I USB FW:g9a
Back-UPS RS 1500 LCD FW:839.H7 .D USB FW:H7
Back-UPS RS 500 FW:30.j3.D USB FW:j3
Back-UPS RS 500 FW:30.j4.I USB FW:j4
Back-UPS RS 500 FW:30.j5.I USB FW:j5
Back-UPS RS 500 FW:30.j6.I USB FW:j6
Back-UPS RS 550GI FW:857.L1 .I USB FW:L1
Back-UPS RS 700G FW:856.L1 .D USB FW:L1
Back-UPS RS 900 FW:9.o2 .D USB FW:o2
Back-UPS XS 1200 FW:8.g1 .D USB FW:g1
Back-UPS XS 1200 FW:831.E6 .D USB FW:E6
Back-UPS XS 1300 LCD FW:836.H4 .D USB FW:H4
Back-UPS XS 1300 LCD FW:836.H5 .D USB FW:H5
Back-UPS XS 1300 LCD FW:836.H7 .D USB FW:H7
Back-UPS XS 1300 LCD FW:836.H8 .D USB FW:H8
Back-UPS XS 1500 LCD FW:837.H3 .D USB FW:H3
Back-UPS XS 1500 LCD FW:837.H4 .D USB FW:H4
Back-UPS XS 1500 LCD FW:837.H5 .D USB FW:H5
Back-UPS XS 1500 LCD FW:837.H7 .D USB FW:H7
Back-UPS XS 900 FW:9.o1 .D USB FW:o1
Back-UPS XS900 FW:830.E4 .D USB FW:E4
Back-UPS XS900 FW:830.E6 .D USB FW:E6
Back-UPS XS900 FW:830.E7 .D USB FW:E7
Back-UPS XS900 FW:830.E8 .D USB FW:E8
J15 AV UPS FW:827.c2 .D USB FW:c2
Smart-UPS 1000 FW:600.1.D USB FW:1.3
Smart-UPS 1000 FW:600.1.I USB FW:1.2
Smart-UPS 1000 FW:600.1.I USB FW:1.3
Smart-UPS 1000 FW:600.3.D USB FW:1.4
Smart-UPS 1000 FW:600.3.D USB FW:1.5
Smart-UPS 1000 FW:600.3.D USB FW:8.1
Smart-UPS 1000 FW:600.3.I USB FW:1.3
Smart-UPS 1000 FW:600.3.I USB FW:1.4
Smart-UPS 1000 FW:600.3.I USB FW:1.5
Smart-UPS 1000 FW:652.12.I USB FW:4.2
Smart-UPS 1000 FW:652.13.I USB FW:4.2
Smart-UPS 1000 FW:652.13.I USB FW:7.3
Smart-UPS 1000 FW:652.18.D USB FW:7.3
Smart-UPS 1000 FW:652.18.I USB FW:7.3
Smart-UPS 1000 RM FW:618.3.D USB FW:1.5
Smart-UPS 1000 XL FW:631.3.D USB FW:1.5
Smart-UPS 1000 XL FW:631.3.I USB FW:1.5
Smart-UPS 1500 FW:601.1.I USB FW:1.2
Smart-UPS 1500 FW:601.3.D USB FW:1.5
Smart-UPS 1500 FW:601.3.D USB FW:8.1
Smart-UPS 1500 FW:601.3.I USB FW:1.5
Smart-UPS 1500 FW:653.12.I USB FW:4.2
Smart-UPS 1500 FW:653.13.I USB FW:7.3
Smart-UPS 1500 FW:653.18.D USB FW:7.3
Smart-UPS 1500 FW:653.18.I USB FW:7.3
Smart-UPS 1500 RM FW:617.3.D USB FW:1.5
Smart-UPS 1500 RM FW:617.3.D USB FW:8.1
Smart-UPS 1500 RM FW:617.3.I USB FW:1.5
Smart-UPS 1500 RM FW:617.3.I USB FW:8.1
Smart-UPS 3000 RM FW:666.5.D USB FW:2.4
Smart-UPS 3000 RM XL FW:691.16.I USB FW:7.2
Smart-UPS 750 FW:651.11.D USB FW:4.2
Smart-UPS 750 FW:651.11.I USB FW:4.2
Smart-UPS 750 FW:651.12.D USB FW:4.2
Smart-UPS 750 FW:651.12.I USB FW:4.2
Smart-UPS 750 FW:651.13.D USB FW:7.3
Smart-UPS 750 FW:651.13.I USB FW:7.3
Smart-UPS 750 FW:651.18.D USB FW:7.3
Smart-UPS 750 FW:651.18.I USB FW:7.3
Smart-UPS 750 RM FW:615.3.D USB FW:8.1
Smart-UPS 750 RM FW:619.3.I USB FW:1.5
Smart-UPS 750 XL FW:630.3.D USB FW:1.5
Smart-UPS 750 XL FW:680.18.D USB FW:7.4
Smart-UPS 750 XL FW:680.18.I USB FW:7.4
Smart-UPS 758 XL FW:630.3.D USB FW:1.5
Smart-UPS RT 1500 XLFW:800.2.D USB FW:6.2

Belkin

F6C1000-TW-RK 1000VA
F6C120auUNV 1200VA

Conext

CNB950 Battery Back Up

CyberPower Systems (CPS) / Geek Squad (GS)

BC 1300C
BC 1300D
CP 1000D
CP 1300C
CP 1300D
CP 1350C
CP 1500C
CP 1500D
GS 1285U
GS 1500U
Value 1200E
CP425HG
CP500HG
CP685AVR-G
DX-800U
UPS AE485
UPS AE550 (CP550SL)
UPS BF700
UPS BF800
UPS CP1000AVRLCD
UPS CP585
UPS CP600
UPS CP850AVRLCD
UPS GS875U
UPS OR500
UPS OR700
UPS RF825

EATON

Protection Station

IBM

IBM UPS1500TLV FW:601.1I1.D USB FW:1.5
IBM UPS750THV FW:651.3I2.I USB FW:7.3
IBM UPS750TLV FW:651.2I22D USB FW:4.2

Liebert

Liebert PSP 500 FW: 02
Liebert PSA 500 FW:09
GXT2-1000RT120 GXT2MR14 1.0 (with USB Intellislot option card)

Tripp Lite

OMNIPLUS 1000LCD 1000 VA

MGE UPS SYSTEMS

ELLIPSE
ELLIPSE MAX
O.P.S. Protection Center 750
Pulsar Evolution 1100
Evolution 1150
MGE EX
NOVA AVR

Nexxtech

UUPS1000 1000 VA

Hewlett Packard

R/T2200 NA
T1000 INTL
T1500 INTL
HP R1500 G2 UPS

Many additional models from each of these vendors will also work since they have the same communications protocols.

Windows Home Server Hardware

Alexander Kent (HSL) — Fri, 20 Nov 2009 08:00:00 GMT

Windows Home Server turn-key solutions are available in a number of configurations and designs from a broad range of manufacturers (availability varies by country). Windows Home Server OEM (original equipment manufacturer) solutions:

	easyStore H340
	ASUS TS Mini Home Server
	Scaleo Home Server 1500 / 1900 Scaleo Home Server 2105 / 2205
	MediaSmart Server EX470 / EX475 MediaSmart Server EX485 / EX487 MediaSmart Server LX195
	IdeaCentre D400
	SQA-5H-1000 / 2000 / 3000
	VIA NSD7800
	HS1000 / HS2000

ASUS TS Mini Home Server

Alexander Kent (HSL) — Fri, 20 Nov 2009 08:00:00 GMT

Specifications

Part Number
Operating System	Windows Home Server
Processor	Intel® Atom Processor N280 1.66GHz
Memory	1GB/2GB DDR2-800
Storage	500GB/1TB/2TB, 7200 RPM 2 x 3.5" SATA I/II HDD Bays
Interface Ports	6 x USB 2.0, 2x eSATA, 1x K-Lock
Communications	1 x 10/100/1000 (Gigabit) RJ45 LAN
Included Software	TBD
Dimensions & Weight	245mm (H) x 96mm (W) x 204mm (D) / 9.6" (H) x 3.8" (W) x 8" (D)

More Information: www.asus.com

Press Release

ASUS Unveils TS Mini Server for Today’s Small Office/Home Office
-- Compact, energy efficient and pre-installed with Windows® Home Server, the TS Mini serves the need to access and share content on-demand --

Fremont, California (November 18, 2009) – ASUS, a worldwide leader in personal computers, today introduces the TS mini small office/home office (SOHO) server. The TS mini targets modern home and small office users that frequently exchange data from multiple computers and require access from various locations. The TS mini secures documents, multimedia, and other digital content into a sleek repository. It further safeguards data on multiple computers across the home or office with automatic backups and cloud storage. TS mini allows centralized file access with local networks, attached storage devices and remotely over the internet. Equipped with an Intel® Atom™ processor, the TS mini delivers quiet, energy efficient, always-on access. Operating on the Microsoft® Windows™ Home Server Platform, it simplifies management of digital content. The TS Mini is available now for pre-order at Amazon.com and NewEgg.com starting at $349.99 USD.

“Consumer demand for rich content that can be accessed anytime, anywhere, on any device is fueling innovation in networking and storage of media and data in the home,” said Seth Bobroff, general manager, Data Center Group – Storage, Intel Corporation. “The Intel® Atom™ processor in the TS mini enables ASUS to deliver the ability to stream media, share files and protect data while remotely accessing it, all in a sleek and energy-efficient 2-bay design.”

“We are pleased to welcome ASUS, one of the industry’s leading PC manufacturers, to the Windows Home Server family,” said Leslie McGuire, Microsoft Director of Windows Server Marketing. “Customers tell us they want an easy and inexpensive way to store, manage and protect their digital content. ASUS helps them achieve all of that with their TS Mini Server, which includes a robust option for adding data capacity through external Web storage.”

Easy Backup and Restoration of Home Computers

The TS mini can automatically back up data from up to 10 computers daily. With six USB and two eSATA ports, the TS mini lets users directly back up, synchronize, and manage their files across various USB and eSATA devices and the internal hard disk drive. In a recovery scenario, users can bring individual computers or the entire office back online by loading the latest recovery information saved on the TS mini.

Convenient Content Sharing and Easy Remote Access

The TS mini makes it easy for users to stream photos, music, video and other digital content to various devices including TVs, computers, Media PCs, and gaming consoles—for all-around content access. With the Remote Access feature, users outside the local network can also leverage their personal Windows Live™ account to access the TS mini and its content. Additionally, they can stream music and multimedia content through the online connection.

Large Data Capacity with Exclusive Web Storage

For additional storage capacity, the ASUS offers TS mini users a year of free 500GB storage over the Web. Users can boost their storage or synchronize backups online for improved data security. Additionally, users can save large peer-to-peer files on the Web, and share data with user accounts worldwide.

Energy-saving Features

In line with global energy-saving initiatives, the TS mini uses minimal power—consuming 24.5W when in idle mode and 27.9W during activation. The TS mini is the ideal choice for 24/7, non-stop data center operation.

Pricing

The ASUS TS mini is available in 500G and 2TB models at $349 and $529, respectively.

HP StorageWorks X500 Data Vault

Alexander Kent (HSL) — Fri, 20 Nov 2009 08:00:00 GMT

Specifications

Part Number	HP StorageWorks X510 1TB Data Vault (Q2050A) HP StorageWorks X510 2TB Data Vault (Q2051A) HP StorageWorks X510 3TB Data Vault (Q2052A)
Operating System	Windows Home Server
Drive Type	1 TB 3G 7.2K LFF SATA 1.5 TB 3G 7.2K LFF SATA Supported, depending on model
Processor	Intel® Pentium® E5200 (2.5GHz)
Memory	2 GB PC2-6400 unbuffered DDR2 ECC 800MHz
Storage	1 TB Starting 6 TB Maximum 13.5 TB Maximum, with external storage options
Interface Ports	2-3 empty internal SATA hard drive bays (model dependant) 4 external USB 2.0 ports 1 eSATA port
Communications	1 x 10/100/1000 (Gigabit) RJ45 LAN
Management	HP Control Center Microsoft Windows Home Server Console
Supported Operating Systems	Microsoft Windows® Vista (32 and 64-bit) XP Home (SP2) or XP Professional (SP2) Media Center Edition 2004 (SP2) or later Mac® OS X Linux Automatic backup, file sharing and remote access capabilities vary based on PC OS.

More Information: www.hp.com

Press Release

Small business owners invest a tremendous amount of time, money and resources to make their ventures successful. Addressing immediate business concerns often means postponing or overlooking technology investments that could impact the bottom line. One of those areas often overlooked are data storage and protection needs. This can lead to missed revenue opportunities through poorly managed data or the inability to rebound from major data loss.

The HP StorageWorks X500 Data Vault Series is a new family of storage devices that help small businesses remain competitive by protecting important business data, easily sharing files regardless of location, and automating backups.

“Small businesses need storage technology that lowers risk by quickly bringing data back online if a disaster occurs. It can also increase productivity by sharing and remotely accessing files outside the office,” said Lee Johns, director of marketing, Unified Storage Division, HP. “The HP StorageWorks Data Vault is easy to install, offers data protection and file sharing at an affordable price for small businesses with limited technology resources and budgets.”

A complete storage solution

The HP StorageWorks X500 Data Vault Series enables small businesses with up to 10 PC clients and Mac’s to easily store information in a central place. Business owners also save money through a low purchase price, which is up to 22 percent less than comparable solutions.(1)

The HP StorageWorks X500 Data Vault Series covers all aspects of storage needs that are important to a small business, including:

Data storage – customers can meet demanding storage needs with up to three terabytes of storage space and virtually unlimited expansion capabilities that add capacity without powering down the device.

Data protection – customers can ensure data protection in the event of failure by automatically backing up their clients daily. Customers have added protection by choosing which files are most important, and with the click of a mouse, duplicate that folder to a second hard disk drive.

Data sharing – customers can share files on their local network through an easy-to-use control panel. Users can also collaborate on projects through Microsoft Windows Home Server, which allows secure remote access to business files.

Larger customers who need high availability or want to simplify data management and grow storage capacity can leverage the HP StorageWorks X1000 and X3000 Network Storage Systems, which consolidate file and block data into a unified storage solution.

The HP StorageWorks X500 Data Vault Series is available in select regions worldwide with pricing starting at €487.(2)

(1) The HP StorageWorks X510 Data Vault costs 22 percent less than the Buffalo Terastation III 2TB product.

(2) Estimated Euro list price. Actual price may vary. Available in the U.S., Canada, Western Europe, Singapore, Australia and New Zealand.

Assign Static IP Address

Chris Bickerstaff — Thu, 19 Nov 2009 08:00:00 GMT

If your router does not support the necessary UPnP standards that allow the Windows Home Server automatic router configuration for remote access; if you have installed additional software applications on your Windows Home Server for which you need to setup port forwarding – or if you simply want to ensure your WHS is always using the same IP address you should configure a static IP address.

Why is setting a Static IP on your Windows Home Server a good idea?

Users can access the WHS on the local network or through the internet if Remote Access is enabled and configured. If you have manually configured port forwarding to your WHS on your router but not configured your WHS to use a static IP address you are asking for trouble.
If you leave the server to acquire an IP address on the default DHCP means that your server’s IP address will likely change, for example the DHCP IP address lease expired, the server or router restarted due to a power outage etc.
Therefore, even if your router fully supports UPnP and you have Remote Access configured automatically, assigning a static IP address to the Windows Home Server is a good idea because it ensures the server will always use the same IP address.

There are two different ways you can configure a static IP address for your Windows Home Server.

1) Reserve a static IP over DHCP at your router level. For this to work you need to have a router which supports static DHCP / IP reservation and you need to know your WHS MAC address. In short, the DHCP server on your router allocates an IP address based on a table with MAC address / IP address pairs – any time your WHS requests an IP address, its MAC address will be matched/found in this table and the reserved IP address will be assigned. This feature is variously called Static DHCP assigned, DHCP reservation or Static DHCP depending on the router manufacturer.

Throughout the Broadband Router Configuration series we favor this option as the best way to assign a static IP address to your Windows Home Server.

2) Manually assign a static IP address directly on the Windows Home Server.

IMPORTANT
Your Windows Home Server’s IP Address configuration must be on the same network mask as your default gateway (your router) and all connected clients. Therefore we recommend to first check and note your current Windows Home Server IP address configuration.

Check your Network Configuration (Gateway & Subnet)

Establish a remote desktop connection to your server
Click on Start, and enter cmd into the run dialog box to open the command prompt
When the prompt opens, type IPCONFIG and press the ENTER key. This will display the server’s current IP CONFIGURATION. In most cases, the default gateway will be 192.168.0.1 or 192.168.1.1 and the subnet mask 255.255.255.0. However your network may use a different configuration, adjust accordingly and only proceed if you are sure of what you are doing!
Once you have determined your default gateway (router) IP address and subnet mask information you can proceed to configure a static IP address. Ensure that no other computer, laptop or device is using the same IP address –otherwise there will be address conflicts and problems.

Setting a Static IP address on the server

At this point you should be logged into your server’s desktop – if not, re-establish a remote desktop connection.

Click the Start button in the left hand corner, proceed to Control Panel and open Network Connections.
Most home server’s only have a single network interface card. If you have additional network cards installed make sure you configure the correct one. Right-click on the network adapter and choose Properties.
The connection properties dialog box will load. Select Internet Protocol (TCP/IP) and click on Properties.
The Internet Protocol (TCP/IP) Properties dialog opens where we can now change the IP options from DHCP to use a static IP address. Change from “Obtain and IP address automatically” to “Use the following IP address” and configure your IP address accordingly.
Double check your settings before proceeding. And when these new IP configurations are applied the remote desktop session will stop responding – this behavior is by design. It is best to reboot your client machine and try to establish a new remote desktop connection to your server using the new static IP address. You can now continue to configure static port forwarding to your Windows Home Server.

Sagem BSKYB Router

Alexander Kent (HSL) — Fri, 13 Nov 2009 08:00:00 GMT

CONFIGURE SAGEM (BSKYB) ROUTER FOR WINDOWS HOME SERVER REMOTE ACCESS

The Sagem BSkyB Router does not support the Windows Home Server automatic router configuration over UPnP standards. This means that you will have to manually configure Port Forwarding to your Windows Home Server.

OVERVIEW

Log on to your router’s setup page
Enable UPnP (Universal Plug and Play)
Create IP Address reservation for your Windows Home Server
Configure Port Forwarding to your Windows Home Server

STEP 1 - Log on to your router’s setup page

Open your web browser and enter your router’s URL

http://192.168.0.1 or http://192.168.1.1

For BSkyB routers -by default the user name is admin, and the password is sky. If you have changed the defaults, then enter your corresponding information.

If you have forgotten your router password, you may reset the router by pressing and holding for a few seconds the reset button located on the router itself.

STEP 2 - Enable UPnP (Universal Plug and Play)

Navigate to the Advanced section and click on on the UPnP option and ensure “Turn UPnP On” is enabled. (This step is optional but it is a good idea to ensure future compatibility or allow other network centric devices to automatically configure the router).

STEP 3 - Create IP Address reservation for your Windows Home Server

a) Since the Sagem Router does not show the device name of the attached devices you will have to use the IP address of your WHS. To find the IP address of your WHS whilst on your client computer, simply open the Windows Command Prompt then enter "ping server" where server is the name given to your Windows Home Server, for example "hpserver". This will show the IP address of the WHS in parenthesis ().

Take a note of this IP address to locate your WHS in your router's IP Address reservation list. In the top column click on the “Attached Devices”, locate your Windows Home Server name under “Device Name” and take note of your Windows Home Server’s MAC address.

Alternatively, you can verify your home server's MAC address by opening the WHS console and going to Remote Access under Settings.

b) Under "Advanced" click on “LAN IP Setup” , and ensure the “Use Router as DHCP Server” option is enabled and click on "Add".

c) Select your Windows Home Server from the available “Address Reservation Table” and make a note of the IP address (for example 192.168.1.3) and click “Add”

d) Verify that your Windows Home Server has been added under “Address Reservation” and press “Apply”.

STEP 4 - Configure Port Forwarding

The Windows Home Server remote access feature requires you to forward port 80, port 443 and port 4125.

a) Click on the Security tab on the top menu bar and proceed to the Services section. In the Services section click on “Add Custom Service”.

b) Enter the following service information:

Service Definition: HTTP
Type: TCP/UDP
Start Port: 80
End Port: 80
Click “APPLY”

c) Click on “Add Custom Service” and enter the following:

Service Definition: HTTPS
Type: TCP/UDP
Start Port: 443
End Port: 443
Click "Apply"

d) Click on “Add Custom Service” and enter the following:

Service Definition: RWW
Type: TCP/UDP
Start Port: 4125
End Port: 4125
Click “Apply” to return to the "Services" overview page and verify that all (HTTP, HTTPS, RWW) services and ports have been added as illustrated below

e) Add the necessary firewall rules to allow communication to the Windows Home Server. You need to do this for each of custom service port defined at the previous step d.

Filter Name: WHSHTTP
Service: HTTP(TCP/UDP80:80)
Action: ALLOW always
Send to LAN Server: 192.168.0.2 (this is the IP address assigned to your WHS)
WAN Users: Any

The resulting Firewall Rules table should look as illustrated below. Note that the server IP address represents your Windows Home Server IP address and may differ from 192.168.0.2.

All done! After you configured your BSkyB Sagem Router for Remote Access you should test the remote connectivity from within your home and from outside of your home.

Locating your Modem INF file

Alexander Kent (HSL) — Thu, 12 Nov 2009 08:00:00 GMT

Your modem’s information file (INF) is a text file that contains all the information that the Setup components need to install the modem drivers.

Generally, the information file contains the following:

Driver name and location
Driver version information
Registry information

How to find your Modem INF file

Go to Control Panel -> Phone and Modem Options -> Modem Properties -> Diagnostics and click the View log button.

Modem driver information is listed near the top of the modem log. The “Modem inf path” shows the name of the currently installed modem’s INF file.

Alternatively, to check your modem inf file name, you can go to Control Panel -> Phone and Modem Options -> Modem Properties -> Details -> Inf name. The displayed value will be the name of your Modem's INF file, for example: mdmcxpv6.inf

Modem INF Location

The modem INF file is located in the Windows INF folder c:\Windows\Inf

MagicJack as a Service

Alexander Kent (HSL) — Thu, 05 Nov 2009 08:00:00 GMT

Installing magicJack on your WHS

Establish a remote desktop session or physically log into your WHS desktop
Plug the magicJack device into a USB port and let the drivers install
Attach a physical telephone to the magicJack via RJ11
Navigate to “My Computer” and engage the auto-run on the Magic Jack drive
Let the magicJack download and install the software
Possibly receive the “No audio devices found no output/input devices are found” error message. Please see the How to magicJack the WHS blog post for a fix.
Reboot your WHS

magicJack as a Service

After you have installed the magicJack software and rebooted your WHS. Establish a remote desktop connection to your WHS and open the Windows Task Manager, navigate to the Processes tab and end the MagicJack.exe process.
Click the Start button and open the Run dialog box, enter MSConfig
Click on the Startup tab and uncheck cdloader2.exe and then click OK
When prompted to restart choose Exit Without Restart.
Click the Start button and open My Computer and go to C:\Documents and Settings\Administrator\Application Data locate the mjusbsp folder.
Copy the mjusbsp folder to C:\Documents and Settings\LocalService\Application Data
Return to My Computer and take note of the letter for a second drive assigned to the Magic Jack. Right-click the drive and choose Properties, the one we want to is the one with the PHONE label. For example magicJack (G:)
Download and the Windows Server Resource Toolkit. This will install a number of useful utilities. We are interested in two: SrvAny and its installer InstSrv are applications provided by Microsoft. SrvAny allows the magicJack software to run as a service although nobody is logged into the WHS desktop.
Install the Windows Server 2003 Resource Toolkit to its default installation directory.
Run the following command: "C:\Program Files\Windows Resource Kits\Tools\instsrv.exe" "MagicJack" "C:\Program Files\Windows Resource Kits\Tools\srvany.exe"
Open the Windows Registry Editor by running regedit and navigate to HKEY_LOCAL_MACHINE\SYSTEM\Current Control Set\Services\MagicJack
Ensure the MagicJack key is selected in the left hand pane and right-click, choose New -> Key and name it Parameters. In the newly created Parameters section, right click and choose New -> String Value and name it Application.
Double click the newly created Application key and set the value to
"C:\Documents and Settings\LocalService\Application Data\mjusbsp\magicJack.exe" /scf _magicJackPersonalDataRoot "G:\magicJack" where G is the second MagicJack drive letter you found earlier in Step 7, click OK and exit the Registry Editor.
All done! Reboot your WHS and wait a couple of minutes for the system to finish loading. If all went well you should now get a dial tone.

DrayTek Vigor 2820 Router

Brad Heare — Thu, 29 Oct 2009 07:00:00 GMT

CONFIGURE VIGOR 2820 SERIES ADSL ROUTER FIREWALL FOR WINDOWS HOME SERVER REMOTE ACCESS

Manufacturer: DrayTek
Model: Vigor 2820 Series

The Vigor 2820 Series ADSL Router Firewall supports the Windows Home Server automatic router configuration over UPnP standards. However, for best results we recommend to manually configure Port Forwarding to your Windows Home Server.

OVERVIEW

Log on to your router’s setup page
Enable UPnP (Universal Plug and Play)
Assign a static IP address to your Windows Home Server
Configure Port Forwarding to your Windows Home Server

STEP 1 - Log on to your router’s setup page

Open your web browser and enter your router’s URL http://192.168.1.1 is the default Vigor router IP address. It should look something like the image below.

STEP 2 - Enable UPnP (Universal Plug and Play)

Click on "Applications" and "UPnP" and then place a check mark in "Enable UPnP Service". Also place a check in both "Enable Connection control Service" and "Enable Connection Status Service". Now select the OK button to apply the changes.

STEP 3 - Assign a static IP address to your Windows Home Server

a) Navigate to LAN and then Bind IP to MAC

b) Select Enable and then highlight the IP Address andMAC Address listing (Red Square in Screen Shot) that is associated withyour Windows Home Server. Then select Add and it will populate those settings in the IP Bind List then select OK.

STEP 4 - Configure port forwarding to your Windows Home Server

a) Click on "NAT" and proceed to the "Port Redirection" section.

b) You need to enable forwarding for 3 different ports: HTTP (80) , HTTPS (443) , RWW (4125). Each of these will need its own row on the table. For all of these, the "LAN IP Address" should be the static IP address you gave to the Windows Home Server in step 3.

Enable: Check
Mode: Single
Service Name: http
Protocol: TCP
WAN IP: 1.All
Public Port: 80
Private IP: (From Step 3)
Private Port: 80
OK

Enable: Check
Mode: Single
Service Name: https
Protocol: TCP
WAN IP: 1.All
Public Port: 443
Private IP: (From Step 3)
Private Port: 443
OK

Enable: Check
Mode: Single
Service Name: Remote Access
Protocol: TCP
WAN IP: 1.All
Public Port: 4125
Private IP: (From Step 3)
Private Port: 4125
OK

Congratulations! After you configured your Vigor 2820 Series ADSL Router Firewall for Remote Access you should test the remote connectivity from within your home and from outside of your home.

Linksys WRT120N Router

Alexander Kent (HSL) — Tue, 27 Oct 2009 07:00:00 GMT

CONFIGURE LINKSYS WRT120N ROUTER FOR WINDOWS HOME SERVER REMOTE ACCESS

The Linksys by Cisco Wireless-N Home Router WRT120N supports the Windows Home Server automatic router configuration over UPnP standards. However, for best results we recommend to manually configure Port Forwarding on your router to point port 80, 443 and 4125 to your Windows Home Server.

Manufacturer: Linksys
Model: WRT120N
Firmware Version: V1.0.01

Overview:

Log on to your router's setup page
Create IP Address reservation for your Windows Home Server
Enable UPnP (Universal Plug and Play)
Configure port forwarding to your Windows Home Server

Step 1 - Log on to your router's setup page

Open your web browser and enter your router's URL. By default, this is "http://192.168.1.1". If you have configured the login information, log in with your username and password. If not, the default username and password is "admin".

Step 2 - Create IP Address reservation for your Windows Home Server

a) Click on the "Setup" tab and click the "Basic Setup" section. Ensure that the DHCP Server is "Enabled" and click on the "DHCP Reservation" button. If you have an aggressive popup blocker, you should temporarily disable it to allow the DHCP Reservation window to appear.

b) Look for the row that has your Windows Home Server's computer name in the "Client Name" column and Add it to the DHCP Reservation. Make a note of the specified IP Address information and click the “Save Settings” button.

Step 3 - Enable UPnP (Universal Plug and Play)

Click the tab labeled "Administration" and proceed to the "Management" section. Make sure that UPnP is enabled. If not, enable it and click "Save Settings".

Step 4 - Configure port forwarding to your Windows Home Server

a) Click the tab labeled "Applications & Gaming" and proceed to the "Single Port Forwarding" sub-tab.

b) You need to enable forwarding for 3 different ports: HTTP (80), HTTPS (443), RWW (4125). Each of these will need its own row on the table. Some of them may already have rows and may/may not be enabled. If there aren't enough empty row, re-use a row for a protocol that you aren't going to forward. For all of these, the "IP Address" should be the IP address you gave to the Windows Home Server in step 2.

Enable HTTP forwarding - by default, there will be a row for this, but some of the information (like IP address) will be missing.
        Application: HTTP
        External port: 80
        Internal port: 80
        Protocol: TCP
        IP Address: 192.168.100
Configure HTTPS forwarding:
        Application: HTTPS
        External port: 443
        Internal port: 443
        Protocol: TCP
        IP Address: 192.168.1.100
Configure RWW forwarding:
        Application: RWW
        External port: 4125
        Internal port: 4125
        Protocol: TCP
        IP Address: 192.168.1.100
Click the "Save Settings" button.

NOTES

The Linksys WRT120N router allows you to set the reconnection mode when using PPPoE (Point to Point Protocol over Ethernet) connection. DSL providers typically use this option. This method of connection requires you to enter a Username and Password (provided by your Internet Service Provider) to gain access to the Internet.

When using PPPoE you must ensure that the Reconnect Mode is set to: “Keep Alive”.

All done! After you configured your Linksys WRT120N Router for Remote Access you should test the remote connectivity from within your home and from outside of your home.

Linksys WAG320N Router

Alexander Kent (HSL) — Tue, 27 Oct 2009 07:00:00 GMT

CONFIGURE LINKSYS WAG320N ROUTER FOR WINDOWS HOME SERVER REMOTE ACCESS

The Linksys by Cisco Dual Band Wireless-N ADSL2+ Modem Gigabit Router (WAG320N) supports the Windows Home Server automatic router configuration over UPnP standards. However, for best results we recommend to manually configure Port Forwarding on your router to point port 80, 443 and 4125 to your Windows Home Server.

Important
The WAG320N has an integrated ASDL2+ modem for internet connectivity – be careful not to accidently modify the WAN network configuration when configuring your router.

Manufacturer: Linksys
Model: WAG320N
Firmware Version: V1.0.01

Overview:

Log on to your router's setup page
Enable UPnP (Universal Plug and Play)
Assign a static IP address to your Windows Home Server
Configure port forwarding to your Windows Home Server

Step 1 - Log on to your router's setup page

Step 2 - Enable UPnP (Universal Plug and Play)

a) Navigate to the "Administration" tab and click the "Management" sub-section and make sure that UPnP is enabled. If not, enable it and click "Save Settings".

Step 3 - Assign a static IP address to your Windows Home Server

The Linksys WAG320N Router does not support DHCP address reservation. You must configure your Windows Home Server to use a static IP address before proceeding to the next step.

Step 4 - Configure port forwarding to your Windows Home Server

a) Navigate to "Applications & Gaming" and proceed to the "Single Port Forwarding" sub-tab.

Enable HTTP forwarding - by default, there will be a row for this, but some of the information (like IP address) will be missing.
        Application: HTTP
        External port: 80
        Internal port: 80
        Protocol: TCP
        IP Address: 192.168.100
Configure HTTPS forwarding:
        Application: HTTPS
        External port: 443
        Internal port: 443
        Protocol: TCP
        IP Address: 192.168.1.100
Configure RWW forwarding:
        Application: RWW
        External port: 4125
        Internal port: 4125
        Protocol: TCP
        IP Address: 192.168.1.100
Click the "Save Settings" button.

NOTES

The Linksys WAG320N router allows you to set the reconnection mode when using PPPoE (Point to Point Protocol over Ethernet) connection. DSL providers typically use this option. This method of connection requires you to enter a Username and Password (provided by your Internet Service Provider) to gain access to the Internet.

When using PPPoE you must ensure that the Reconnect Mode is set to: “Keep Alive”.

All done! After you configured your Linksys WAG320N Router for Remote Access you should test the remote connectivity from within your home and from outside of your home.