WHS behind SBS 2003 Server

All replies

• 

  

  0

  Sign in to vote

  The easiest thing to do would probably be to use other ports for WHS website and forward these ports to WHS in your router. Make sure your WHS always gets same IP from SBS or set fixed IP on WHS outside range used by SBS.

   

  You can set ports in IIS manager on WHS. Make sure you're not using any ports that are used by apps on SBS (typically webbased management programs (antivirus suites) to avoid problems. The only downside is that you always have to supply appropriate port number when accessing WHS remotely.

   

  Alternatively you could use hostheaders:

   

  http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true

   

  http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true

   

  http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/596b9108-b1a7-494d-885d-f8941b07554c.mspx?mfr=true

   

   

   

  • Proposed as answer by Al West Thursday, February 11, 2010 9:12 PM
  • Marked as answer by Jonas Svensson -FST- Tuesday, February 23, 2010 11:02 PM

  Friday, November 9, 2007 11:38 PM

  Moderator
• 

  

  0

  Sign in to vote

   

  Just wondering if you have been able to make this work yet. I have SBS Premium 2003 at home as well and would like to publish the web site on the WHS so family members can view pictures.  

   

  I was also wondering if we could set up any rules in ISA to make this happen. Currently I don't have a ***.homeserver.com domain but when I try to connect through the console to sign up for one, it gives me an error. I'm sure it's because it's expecting the ports to be open.

   

  Anyone?

   

  Mike

  Thursday, November 29, 2007 10:19 PM
• 

  

  0

  Sign in to vote

  When you say 'remotely', do you mean Remote Desktop?  I think I know a way you could do this.  When I had SBS2003 and a Media Center PC, I always wanted to RDP to the MCE2005 machine, but go through the SBS2003 box for security purposes.  Since MCE2005 cannot be part of a domain, this procedure worked well.  I have since taken the SBS2003 machine down, converted over to WHS, and moved my website to an external hosting company.  I like being able to hold someone elses feet to the fire with regard to backing up my email, uptime of my website, someone else dealing with the constant web attacks against thier hardware versus mine, and I get to do that for $70 a year!  SBS2003 was fun, but WHS is cooler!

   

  This should work for getting your WHS machine to be seen via SBS2003 remote web workplace:

   

  Log onto your SBS 2003 server as a member of the Domain Admins group.

  Make sure your WHS machine can be reached via a DNS name. You should be able to "ping" the WHS by name 

  Install the Support Tools (SBS2003) from the install CD if you haven't already done so. You'll be using the ADSIEDIT tool.

  Manually create a computer account for your WHS computer as follows:
  Open Active Directory Users and Computers.
  In the console tree (left pane), right-click "Computers".
  Point to "New", and click "Computer".
  Type the name of your WHS box

  Click "Next".
  Leave "This is a managed computer" unchecked, and click "Next".
  Click "Finish".
  Close Active Directory Users and Computers.

  Now, modify the Computer Account to convince RWW that the computer can be used for Terminal Services.
  Use ADSIEDIT as follows:
  Click "Start" -> "Run..."
  Type "adsiedit.msc" (without the quotes).
  In the console tree, expand the "Domain" node.
  Expand the node for your root domain (something like DC="mydomain",DC="local").
  In the console tree, click on CN=Computers.
  In the right pane, right-click CN=<your_WHS_box_name>

  Click on "Properties".
  In the Attribute Editor tab scroll down the list of attributes, and click on the "displayName" entry.
  Click "Edit".
  Enter the name of your WHS box with a dollar-sign appended

  Click "Ok".
  Scroll down to the list of attributes, and click on the "operatingSystem" entry.
  Click "Edit".
  Type "Windows Home Server" (without the quotes).
  Click "Ok".
  Scroll down the list of attributes, and click on the "servicePrincipalName" entry.
  Click "Edit".
  In the "Value to add" textbox, type "HOST/<your_WHS_box_name>"

  Click "Add".
  In the "Value to add" textbox, type "HOST/<your_WHS_box_name>.<your_domain>" (without quotes; in our example, it would be HOST/MEDIA.mydomain.local).
  Click "Add".
  Click "Ok".
  Click "Apply".
  Click "Ok".
  Close ADSIEDIT.

  That's it! You're ready to rock-n-roll! Log into Remote Web Workplace, and click on "Connect to Client Desktops" (if you're an administrator; non-admins click on "Connect to my computer at work"). Your WHS box should be in the computer-selection menu.

   

  Is that what you are looking for?

  Friday, November 30, 2007 1:59 PM
• 

  

  0

  Sign in to vote

  You should be very careful with this. I believe the end result is that your WHS PC will believe that is has been joined to your AD domain, which is a violation of your license and which will eventually cause WHS to reboot every hour. It would be great if someone could prove me wrong, however...
  

  Friday, November 30, 2007 6:09 PM

  Moderator
• 

  

  0

  Sign in to vote

  mdevinc wrote:

  Just wondering if you have been able to make this work yet. I have SBS Premium 2003 at home as well and would like to publish the web site on the WHS so family members can view pictures.     I was also wondering if we could set up any rules in ISA to make this happen. Currently I don't have a ***.homeserver.com domain but when I try to connect through the console to sign up for one, it gives me an error. I'm sure it's because it's expecting the ports to be open.   Anyone?   Mike

   

  Funny, I'm in the same "Boat" and was wondering the exact same thing. I'm getting close to dumping SBS 2003 in favor of WSH (which I'm just starting to evaluate). I too am tired of fighting the SPAM, attacks, email blacklisting and other Internet-facing issues. I get enough of that at work every day

   

  Stuart.

  Friday, November 30, 2007 8:09 PM
• 

  

  0

  Sign in to vote

  I'm planning to deploy WHS in this setting, but have not yet done so.  I do have WHS running at home.

   

  I was not planning to use the remote access facilities on the WHS--just primarily the backup facility, and secondarily the redundant storage for large collections of media files.

   

  If I wanted to get to the WHS remotely, I think I would connect to my SBS server by VPN, and then connect to the WHS server once the VPN was connected, just as I would be able to within the office.

   

  So--that's one approach that works with one set of constraints.  If you need full web access from the outside world, I think you need to set IIS to use alternative ports for HTTP and HTTPS, and to publish the server(s) on those ports via the ISA firewall on the SBS server.  I think that some dynamic DNS services, such as TZO, will allow you to redirect ports, so that you could use port 80 to connect to the TZO address, and it would redirect to 8080 or whatever on your SBS server--if remembering the alternate port is an issue.

  Friday, November 30, 2007 11:38 PM
• 

  

  0

  Sign in to vote

  I'm learning on how to adm servers, my question is can I use WHS add-on on Server 2003? Or how can I acheived on making Server 03 to act like WHS? 

  Thursday, February 11, 2010 7:05 PM
• 

  

  0

  Sign in to vote

  Hi,
  
  You'll probably have more joy in the Windows Server 2003 forums.  Add-Ins for Windows Home Server can't be run on other Operating Systems.
  If you want to learn about servers then just get one and start breaking it :-)
  Cheers,
  Al

  ---

  --

  Thursday, February 11, 2010 8:31 PM
• 

  

  0

  Sign in to vote

  THX for the info

  Friday, February 12, 2010 2:44 AM