It’s the Windows Home Server Data Sheet!

Sat, Sep 1, 2007 | Terry Walsh

I’m having a bit of a spring clean around We Got Served over the weekend, and I came across this Windows Home Server product data sheet, which was sent through to me last week in the midst of all of the IFA fun and games. Here it is for you to check out.

WHS Product Data Sheet - PDF

This post was written by:

Terry Walsh - who has written 651 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

1 Comments For This Post

orcmid Says:
September 2nd, 2007 at 6:14 pm

Oh Oh! I never did come up with a test box to try out WHS beta on, so I’ve been waiting to see how the commercial offerings sort out. I might still build a box but I suspect off-the-shelf will be better.

But I just saw the spec item that says the machines on the LAN must get their IP addresses from the hub/router. I use fixed IP addresses on my local home LAN inside the residential firewall/router. (These are all in the 192.168.*.* group.) I guess this does require the ability to set the IP address for the WHS as well. Why not?

I could switch to letting the residential firewall/router issue addresses because I don’t really require the functionality I had introduced fixed IPs for (having incoming HTTP requests routed to a particular machine).

But is that really a WHS limitation?

orcmid Says:
September 2nd, 2007 at 6:14 pm
Oh Oh! I never did come up with a test box to try out WHS beta on, so I’ve been waiting to see how the commercial offerings sort out. I might still build a box but I suspect off-the-shelf will be better.

But I just saw the spec item that says the machines on the LAN must get their IP addresses from the hub/router. I use fixed IP addresses on my local home LAN inside the residential firewall/router. (These are all in the 192.168.*.* group.) I guess this does require the ability to set the IP address for the WHS as well. Why not?

I could switch to letting the residential firewall/router issue addresses because I don’t really require the functionality I had introduced fixed IPs for (having incoming HTTP requests routed to a particular machine).

But is that really a WHS limitation?

We Got Served