Home > Windows Home > Windows Home Server Connector Setup An Error Occurred

Windows Home Server Connector Setup An Error Occurred

I'm in the same boat of "none of the above works', even after a clean install on a client.Mark Wednesday, August 18, 2010 6:40 PM Reply | Quote 0 Sign in I had only left in one of the drives (1TB) in my server (HP Data Vault X510 2TB). Error code 1603. Salvatore Nestor |July 12, 2016 at 7:20 am I am also experiencing the inability to get the client installed. this content

I have 4 computers on our WHS network: three running Win7 Home Premium, and one XP machine. Can anyone give me any suggestions? I was almost running insane after allowing the upgrade and suddenly Domain Clients seemed to just vanish in the Dashboard. so that hopefully someone will explore any problem resolution hint and will then please share it with this community. visit

Try these. You can follow any responses to this entry through the RSS 2.0 feed. Reboot then try to install from http://servername:55000/ You might also want to turn off any A/V or firewall before trying the install. -- Thursday, April 08, 2010 11:49 PM Reply |

During troubleshooting I released my domain name. There is no workaround for this other than not to edit these files on the homer server. An update package is available to improve the setup and configuration of Windows Home Server (941913) Describes about the September 2007 High Priority Update for Windows Home Server. Many thanks!

Who, abruptly sent me back because they do not support WHS2011, a consumer product, to the consumer tech folks. So Microsoft still has a lot of work to do, to get this right Mark Berry |January 18, 2016 at 1:41 pm Roger, do you have the Essentials edition of Server Is your server fully patched? http://forum.wegotserved.com/index.php?/topic/15457-cannot-install-home-server-connector-software/ I have double checked the user accounts and the details are correct (would I get this error if they were wrong or would it tell me?) 4.

The service that is not running is 'Active Directory Certificate Services'. Deleted the PC from the WHS console (even when it fails it still adds it to the server so make sure its gone) 3. There is only one error listed in the dashboard - One or more services are not running. Once the server is restarted, install the WHS Connector software on the PC, and all should be well. original post here (http://social.microsoft.com/Forums/en/whshardware/thread/914ec833-df7a-4c4f-933d-c6a8334176bc ) This workd for me, so may

  1. or from a local copy of the connector software? –Omar Shahine May 2 '09 at 15:33 I've tried both server:55000 and \\server\Software. –Matt Hanson May 2 '09 at 15:39
  2. I have tried getting the Connector working of a variety of machines now, so I don't believe that the error exists on the client end.
  3. Lists the improvements that are included and the issues that are fixed in this update.
  4. I tried everything suggested here to no a-vail (pun intended) After much frustration I decided to just do a re-install and that fixed the issue, everything is now running fine!
  5. Can you explain your question about accessing the WHS on a different IP subnet?
  6. Also, it fails even if you run the connection setup software from the command line on the local machine.
  7. Very irritating.
  8. I have monitored the temp folder the wizard downloads the patch.
  9. pointing the DNS to the server when on the LAN:  stopped.

This is supposed to be a product that is only for OEMs. So much for promoting this as a setup and leave it alone solution for the family. YMMVWhat you need:WHSParagon Partition Manager 8.5 Enterprise Server Edition Recovery CD.Time (lots of time)What I used to do: (no longer recommended)01) Install WHS and upgrade drivers, etc. (don't fill up your Please try again later.

The WHS has been running PP3since November, so it's not any of the PP3 time issues. news This results in the need to enter the Server password which is then rejected as being invalid; to verify, I it changed it on the server and tried again with the I tried wiping the server OS and reinstalling several times already...some with an unattended install off a USB and other times off the install DVD. Oct 25, Windows 10 Enterprise updated.

Thanks, Tom Monday, April 05, 2010 6:52 PM Reply | Quote All replies 0 Sign in to vote Are the time and dates on the server and client correctly set?-- Edit....You may have a point IF the server doesn't recognize another machine has been connected......but mine always has. Never a dull moment Wednesday morning in our IT department. have a peek at these guys A combination of that IIS error, the WHS connector error message and some googling turned up basically replacing (renaming) a current IIS file with a previous one.

I guess you used https://server:56000/enroll/id.xml and not //server:56000/enroll/id.xml? Attached my Screenshots and the Log-File into this posting : http://www.mediasmartserver.net/forums/viewtopic.php?f=5&t=8585 Edited by Ingo Schreiber Thursday, August 26, 2010 5:03 AM added a link to attachments Wednesday, August 25, 2010 The fact that I hit a brick wall when trying to communicate to my server via an IPv6 address then the issue corrects itself after I try it through an IPv4

I noticed that my local account didn't have the correct permissions to the Program Files\Windows Home Server folder (It couldn't display the correct owner for the directory in the security tab),

system. It was one of those "If it ain't completely broke - Don't fix it" sort of things. To do this, right click on My Computer,go to Manage, then expand Local Users andGroups, then go to the Users folder, then right click on the Administrator account, then go to Maybe I should roll back WHS to a state before this occurred?

It seems that MS are trying to make it idiot proof and in the process creating the need for these workarounds. Try again later.   Home Services About Contact User Blog Tech Blog Copyright © 2016 MCB Systems. Not necessarily the best way but it worked for me. http://trigonahosting.com/windows-home/windows-home-server-2011-connector-error.html beelzibub, Jul 24, 2012 beelzibub, Jul 24, 2012 #1 Jul 25, 2012 #2 benogil Limp Gawd Messages: 143 Joined: Sep 28, 2006 If you look on the MS 2011 forum there

You cannot connect to a computer that is running Windows Home Server (939758) - Describes that you cannot connect to a computer that is running Windows Home Server.