Where to start if http://servername:55000 and connector install doesn't work but everything else is fine? (WHS 2011)
16 martie 2012 02:37
I have spent a considerable amount of time reading through these forums and reading through solutions as connectors not installing seems a common issue but I can't find a solution for the problem I'm having.
Basically when I first installed WHS 2011 I put the first machine on which installed its connector without issue (a Windows 7 Pro machine), since then I've made a few more configuration changes although nothing major but I cannot get any other machine (XP or Windows 7) to install the connector. The error I get is the seemingly infamous 'This operation cannot be completed at this time - Please try again later. If the problems persists, please contact Product Support' I've tried searching manually
In a bit more detail, the machine is an HP Microserver N36L upgraded to 4GB ram and an ATI 6450 graphics card, it's connected locally to a gigabit switch which is then connected to a Draytek 2710n ADSL router. The network seems to be fine in that I can ping the server without issue, I can remote desktop on and I can get to the shares plus the original one machine with the connector installed has no issues with the launchpad/dashboard either.
Yet I cannot access http://myservername:55000 (I am putting my own server name in there), I just get an error that the page cannot be found. If I go to http://servername it comes up first with a certificate error but this seems simply because the local name does not match xxx.homeserver.com name, if I click to continue to the webpage I can get into the webpage without issue. The world wide web service is definitely running but the IIS logs are not showing anything wrong nor are the main computer logs. The clients are all running Microsoft Forefront and Windows firewall, disabling that on both the client and server doesn't seem to make any difference. I can't telnet onto port 55000 either as I get a connect failed.
I don't know what could be causing the problem and reading through the message board here, most people can seem to get to the servername:55000 site but then have other issues but I can't even get that far. Some posts referred to checking the registry but that seemed to be a particularly client issue, I've checked it on my machines and they seem to have the correct settings for installing the connector. One fix I saw was to rename the server to the default server name and rename it back but I'm not sure how that can be done as the option is greyed out on my server because of the certificate authority running. I did see some steps to bypass this issue in the same way as changing the workgroup but the process was not recommended as it could cause serious problems with the certificate.
Reinstalling the server is looking like my only option which isn't too bad in one sense as the configuration is pretty simple at the moment and there's only the one computer backing up but my main concern is if I reinstall the OS and hit the same problem again I'm nowhere. Given it's not a complex install I can't see what has broken it aside from enabling remote access perhaps?
Thanks for any thoughts,
15 aprilie 2012 22:38
Well unsurprisingly I gave up on this and rebuilt the server, since then I have had no problems installing the home connector. I haven't re-enabled remote access yet which may still turn out to be the culprit but there's clearly nothing wrong with my network setup, I'm assuming the servername:55000 is only for WHS v1 as that still doesn't work on any of the machines even though they are working fine with the connector.