Linked by Thom Holwerda on Wed 22nd Aug 2007 22:36 UTC
Windows "Details about the first OEM systems equipped with Windows Home Server are leaking out on to the 'net, and it looks like HP is going to get the ball rolling with its MediaSmart Home Server. Prices for the units were accidentally posted on several sites, such as PC Mall and onSale.com, and it looks like the server will have a US list price of USD 596 for the 500GB version and USD 745 for the 1TB version."
Thread beginning with comment 265343
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[11]: Comment by Almafeta
by segedunum on Thu 23rd Aug 2007 20:43 UTC in reply to "RE[10]: Comment by Almafeta"
segedunum
Member since:
2005-07-06

You don't have to worry about that with WHS. Just plug the box in and it's on your network. You don't need to mess with DHCP or ip addresses.

You do know how networks work, right, as well as having nice, simple DNS names for your machines which is pretty much a given?

Out of interest, where is your DHCP server located?

Reply Parent Bookmark Score: 2

RE[12]: Comment by Almafeta
by archer75 on Thu 23rd Aug 2007 20:56 in reply to "RE[11]: Comment by Almafeta"
archer75 Member since:
2005-10-17

The router assigns IP addresses. Which is located in the same room as the WHS and my desktop.

I just plugged the thing in and I was set. Picked up the shares on the computers fine and had no issues with remote access. Didn't have to configure DHCP, IP, DNS, subnet, etc.

Edited 2007-08-23 21:03

Reply Parent Bookmark Score: 1

RE[13]: Comment by Almafeta
by segedunum on Thu 23rd Aug 2007 22:07 in reply to "RE[12]: Comment by Almafeta"
segedunum Member since:
2005-07-06

The router assigns IP addresses. Which is located in the same room as the WHS and my desktop.

Yep, which means you've got a dynamically assigned network, and that means IP addresses only - certauinly internally. It's not very user friendly, nor are any of those IP addresses guaranteed to be consistent. You're going to need a static IP for your server, ideally.

A really simply walkthrough of network set up and DNS is a given here, since people want to call all their machines nice, easy to remember names on the internal network. In essence this means a centralised Active Directory, which WHS does not have - for obvious reasons. On a network, that's what I'd find most useful.

Looks like I'll be keeping BIND around for while then.....

...and had no issues with remote access.

That's assuming it runs UPnP. You got lucky:

http://forums.microsoft.com/WindowsHomeServer/ShowPost.aspx?PostID=...

Reply Parent Bookmark Score: 2