Setup Static IP for Windows Home Server

If you have installed additional applications on Windows Home Server you would have setup port forwarding which enables your router to forward ports to the server’s IP address that you specified. Whilst this would work when you initially set it up, after restarting your WHS it would most probably get a different IP address. When this happens the ports would no longer be forwarded to your server’s IP address and port forwarding would no longer work. To get around this issue there are two options we can undertake. We can either setup a static IP via the router which is known as Static DHCP or we can setup a static IP on the Windows Home Server.

Static DHCP: If your router can do it, we can tell it to reserve an IP address for your server from within DHCP.  This means entering the MAC address from the network card in the WHS, into the router and assigning it a static IP address then whenever the WHS is restarted it will always have that same address.

The MAC address can be obtained by typing IPCONFIG /ALL at a command prompt from within the Windows Home Server.

If like many routers yours does not support this feature then we need to setup a static IP on the Windows Home server instead.

Static IP on WHS: First we need to choose an IP address.

IP Address Ranges:-
192.168.0.0   192.168.255.255   
172.16.0.0   172.31.255.255   
10.0.0.0   10.255.255.255

If in the router the DHCP Server IP addresses’ are assigned 192.168.1.100 to 192.168.1.150 then we can use any IP address from 192.168.1.151 to 192.168.1.255 for the static IP address as these will still be in the subnet but not in the DHCP scope.

Within the server click Start, Run and type CMD

In the box that opens type ipconfig /all and press Enter on your keyboard. Take note of the Subnet Mask, Default Gateway and the DNS Servers.

The DNS Servers entry may not be correct as some router’s act as a proxy between the actual name DNS servers and your computer. You will know if this is the case, because the Default Gateway will list the same IP address as the DNS Servers entry. We need to have the correct DNS Servers IP addresses otherwise we will not be able to browse the web. To get this information we need to log into the router’s web interface, and look at your router’s status page. On that page you should see an entry for DNS or Name Servers. Write down these IP addresses.

Type exit in this window, then press the Enter key to close it.

One again click on Start then Control Panel, Network Connections and then Local Area Connection.

On the dialogue that opens on the General tab click Properties.

On the General tab of this new box click on Internet Protocol (TCP/IP) (make sure that you do not un-tick it) and then click Properties.

On the General tab click Use the following IP address and enter the IP address you choose earlier followed by your Subnet mask and the Default gateway.

Click the lower Use the following DNS server addresses and enter those that you wrote down earlier.

We can now OK out of all the dialogue boxes.

We now need to re-boot the Windows Home Server and that’s it job completed!

69.png

25 Responses to “Setup Static IP for Windows Home Server”

  1. Simon Smith Says:

    Excellent article and the second part is exactly how I set mine up. But don’t you think this should be part of the WHS installation routine, along with the ability to set the workgroup name?

  2. Philip Churchill Says:

    Hi Simon Smith,
    I totally agree. The ability to set the workgroup name would be easy to implement but I can imagine that getting the WHS configured automatically to use a fixed IP address during installation would be a nightmare for the home server team to setup.

  3. Woody Leonhard Says:

    I’ve been playing with this a bit and saw something happen repeatedly that has me wondering…

    WHS’s automatic router configuration routine seems to run on its own accord from time to time. I’m talking about the program that runs when you go into WHS Console, click Settings, Remote Access, then under Router, click Details, then click Refresh.

    I’m almost certain that, if you’re lucky enough to get the automatic configuration routine working, it’ll re-assign the forwarding address inside the router *automatically*, to point ports 80, 443 and 4125 at the WHS server, on a schedule that I don’t yet understand.

    Has anybody else seen anything similar happening?

  4. Klaus Says:

    Hint: if the static IP get set up after a WHS DHCP installation, it may be required to get rid of the IP in the WINS server.
    Usually you get this by
    1. add the WINS ip into the TCPIP configuration on your WHS
    2. reboot the WHS.

  5. Klaus Says:

    Update: I was not successful here to reconnect WHS connector to WHS after static IP change.

    I had to do these things for a reconnect:
    1) a registry key on my client VISTA PC
    HKLM\Software\Microsoft\Windows Home Server\Transport\Clients\{08E2E743-B368-4F5A-8D1B-686139702ECB}\IPAddress
    2) add a host entry into the hosts file

    :-(

    PS: I use a samba server for DNS and WINS (home network)

  6. Philip Churchill Says:

    Hi Klaus,
    Thanks for the info.

  7. David Parkinson Says:

    Is it OK to reset the workgroup name for WHS? I now see 2 workgroups, mine and WORKGROUP, with the WHS in on its own.

    I can see that I can change it using remote desktop, but don’t know if its a good idea?

    HP MediaSmart 475 ( new ) so still playing {:-)

  8. Philip Churchill Says:

    Hi David Parkinson,
    You can change the server workgroup to the name you are currently using. The only thing you may have to do afterwards is too reinstall the connector software on the client PCs as they may not find the server after the name change.

  9. Herman Says:

    You said: Within the server click Start, Run and type CMD

    I don’t see any Start buttuon within the server??!?!

    Thanks for your help.
    Herman

  10. Philip Churchill Says:

    Hi Herman,
    You need to use the Remote Desktop Connection on Vista or XP to connect to your server as a remote connection. You will them see the desktop of your server machine and the start button in the bottom left hand corner.

  11. Herman Says:

    Dear Philip,
    O, of course. I was looking in the Home Server Console.
    Thanks.
    Herman

  12. Andrew Moss Says:

    I have a question which maybe the static config would fix.

    I have a Vonage router with my wireless netgear router behind it with all my computers and HP home server.

    I cant set up the Remote access.
    I cant verify that the whs is accepting web site connections nor can I verify that it is accepting Remote access connections.

    Will static setup fix this?

  13. Philip Churchill Says:

    Hi Andrew Moss,
    In what way cant you verify that it is not accepting remote access connections. Can’t you navigate to the web interface?

  14. OhPinchy Says:

    I’m a newbie on this stuff, sorry if it’s a stupid question: my Linksys WRT55AG router allows assigning a static IP address to a particular MAC address.

    If I enter the MAC address of my Windows Home Server and give it an IP address of 192.168.1.100 will that mean the WHS will always get that IP address and I don’t need to do any of the above?

  15. Philip Churchill Says:

    Hi OhPinchy,
    You are correct and thats exactly what I do with my Linksys.

  16. OhPinchy Says:

    Thanks. I’ve seen mentions elsewhere that Linksys routers might preserve certain IP addresses for specific uses and I should set the static IP address to something lik 192.169.1.203 – does that sound right?

  17. Andrew Moss Says:

    Philip,
    Thats what the WHS software message is under routre configuration detail.
    Configured not verified.
    Keep trying and it will not verify.
    Website setup with HPhomeserver.com

    Help?

  18. Philip Churchill Says:

    Hi OhPinchy,
    That does sound right, that way all other address’s are out of the way.

  19. Philip Churchill Says:

    Hi Andrew Moss,
    It sounds like you will need to let the ports through manually with port forwarding in your router and/or the firewall on your PC is blocking the ports also.

  20. MikeC Says:

    Hi,

    My Belkin router F5D8230-4 doesn’t allow Static DHCP. When I tried static IP with DNS server same as default gateway, all my PCs lost internet connectivity. Why is this?

    I know your article above specifically says to use the actual DNS server from ISP. My ISP refused to give out at IP. My router status page doesn’t show it. Is there a tool to find out what my DNS server’s IP is?

    Is it OK to assign a static IP but have WHS obtain DNS automatically?

    If I don’t have any apps installed on WHS, is it OK to go ahead with dynamic IP? Will the remote access (and photo sharing in HP EX470) work if the WHS IP changes?

    MikeC

  21. Olaf Engelke Says:

    Hello,
    in the most configurations it is recommended, to use the IP address of the router also as DNS server (and NOT the IP address of the ISP, as Phil stated).

    So you avoid the trouble, that clients and server try to register their network connections on the DNS server of the ISP, which will fail.

    Also name resolution for your WHS may go wrong, if your clients try to resolve the WHS name at your ISP instead of your home network.
    Best greetings from Germany
    Olaf

  22. Gary Says:

    I can’t get anything set up at all. The connect software for my Vista machine(main PC) failed because the router(Belkin F5D8231-4) can’t see the server.

    Tried to setup a static ip address (for Port Forwarding) but I stumble straight out of the blocks – I can’t seem to get a MAC address from my WHS machine. When I type ‘ipconfig /all’ into the command line, all that is returned is ‘Windows IP Configuration’.

    Any Ideas – I’m tearing my hair out!!!

  23. Ernie Says:

    Does anyone know if this linksys router WRT54G3G-ST handle static ip adress? If so how…thanks in advance.

  24. QSCS Says:

    Hello,
    I have also been having some issues with WHS. I have setup port forwaring via my DLink DIR-615 router. I can access internally via network / console or remote desktop but in the console it states that my router cannot verify accepting remote access or web site connections. I’ve been surfing for a week now to try and figure this out. I have a static IP address assigned to my WHS only with all my other machines obtaining automatically. I have spoken with my ISP and these ports are not blocked. I have shut down the firewall on WHS, I’ve even tried DMZ through my router and it still will not succesfully configure within the console. I’m now thinking it is my router but wanted some feedback to see if anyone else had any comments before i ditch the DLink.

  25. Moty Levy Says:

    Are there any new firms developing antivirus firewall applications? The old ones do not work for me


Leave a Reply