I have been having WHS problems trying to restore a backup. After messing around big time I managed to basically kill the WHS. So today I spent the day doing a reinstall using the WHS X:File Edition (WORKED GREAT).
After the install I ended up with the following Version Numbers:
Console 6.0.1800.0
Backup/Restore 6.0.1800.36
Drive Extender 6.0.1800.24
Remote Access 6.0.1800.0
Storeage Manager 6.0.1800.24
Client Computer has Vista Ultimate OS
I boot from the recovery CD (either the X:File or the WHS version - same results). The process is normal until you enter the server name. After clicking OK the process continues and shortly displays a cannot connect to the network error. End of recovery session.
Please note that the connector software installed without complaint and the WHS works appears to work just fine except for recovery.
Running the toolkit reveals two problems: The second problem is a DHCP error where it cannot find a DHCP server. The problem here is that all my computers have static IP addresses except for my laptop which is DHCP and has no problem getting an IP address. The Toolkit message that comes with the DHCP error says to ignore the error message if you are using static IP's.
The first problem deals with connector versions. First off, the connector software was installed after accessing it through IE using //SERVER:55000. Installation was normal and the connector works as expected. The Toolkit error message says that "connector software does not match version of WHS" and suggests you delete the WHS folder on the home computer located at %programfiles%/Windows Home Server. It then asks you to connect to \\SERVER\software\WindowsHomeServerConnector and run setup. Which I did. Still does not work
So the questions:
1. With a clean reinstall of WHS and a clean reinstall of the connector software, why does the Toolkit say the versions don't match? I believe I installed the connector in an approved manner.
2. However, it is not the client connector that is having the problem (in my opinion), it is the recovery disk connector that is not able to connect to the server. I think I need a new recovery CD, one that matches the installed WHS connector. Where do I find the latest & greatest Recovery CD?
Page 1 of 1
Connector software does not match
#2
Posted 11 March 2009 - 05:06 AM
As far as I know, the recovery disk has not changed. I have a PP1 recovery disk and it worked just fine with the recent updates
#3
Posted 11 March 2009 - 06:58 AM
Try uninstalling and then reinstalling the connector to see if the mismatch goes away.
#4
Posted 11 March 2009 - 07:41 AM
Brent, on Mar 10 2009, 08:58 PM, said:
Try uninstalling and then reinstalling the connector to see if the mismatch goes away.
I am having the same problem. The connector trouble shooter says that "The version of the Connector software does not match the version of Windows Home Server". I have run setup from the server several times and it completes with no errors but the problem persists. The trouble shooter says to delete the /Program Files/Windows Home Server folder but I cannot do that. I get a permissions error even though I am runing as an administrator. I will try uninstalling to see if that helps. However, even with the suposed mismatch the connector runs just fine.
#5
Posted 11 March 2009 - 11:00 AM
#6
Posted 11 March 2009 - 11:53 AM
What are the incompatibilty issues with x64?
I had my server up and running fine, did Windows Update and after a few reboots server was a happy bunny with all latest updates/patches. Turned my PC on the next day and a message popped up that new connector software was available and to download from server. Clicked yes, and it failed to do the last step configuring backups. I had Event log messages saying that the protocol doesnt match the server(!).
I first tried re-installing the connector software from the WHS disk, no joy.
Tried the Connector software from the Software share, no joy.
Found on the server a WHS directory (C:\WHS) copied it to my Software share (called it Home Connector2), run setup.exe and the client XP x64 machine went through the motions and connected fine.
I had my server up and running fine, did Windows Update and after a few reboots server was a happy bunny with all latest updates/patches. Turned my PC on the next day and a message popped up that new connector software was available and to download from server. Clicked yes, and it failed to do the last step configuring backups. I had Event log messages saying that the protocol doesnt match the server(!).
I first tried re-installing the connector software from the WHS disk, no joy.
Tried the Connector software from the Software share, no joy.
Found on the server a WHS directory (C:\WHS) copied it to my Software share (called it Home Connector2), run setup.exe and the client XP x64 machine went through the motions and connected fine.
#7
Posted 11 March 2009 - 04:49 PM
Etoa (WGS), on Mar 11 2009, 12:41 AM, said:
I am having the same problem. The connector trouble shooter says that "The version of the Connector software does not match the version of Windows Home Server". I have run setup from the server several times and it completes with no errors but the problem persists. The trouble shooter says to delete the /Program Files/Windows Home Server folder but I cannot do that. I get a permissions error even though I am runing as an administrator. I will try uninstalling to see if that helps. However, even with the suposed mismatch the connector runs just fine.
Been there, done that. Had to go into save mode to delete the WHS directory. Still does not work.
#8
Posted 11 March 2009 - 04:54 PM
Brent, on Mar 10 2009, 11:58 PM, said:
Try uninstalling and then reinstalling the connector to see if the mismatch goes away.
It's been uninstalled and reinstalled multiple times. The connector works as expected on the client except when you boot from the recovery CD to restore. I think the connector on the recovery disk is not compatible with the server connector software.
#9
Posted 11 March 2009 - 04:56 PM
#10
Posted 11 March 2009 - 05:01 PM
far2wired, on Mar 11 2009, 04:53 AM, said:
What are the incompatibilty issues with x64?
I had my server up and running fine, did Windows Update and after a few reboots server was a happy bunny with all latest updates/patches. Turned my PC on the next day and a message popped up that new connector software was available and to download from server. Clicked yes, and it failed to do the last step configuring backups. I had Event log messages saying that the protocol doesnt match the server(!).
I first tried re-installing the connector software from the WHS disk, no joy.
Tried the Connector software from the Software share, no joy.
Found on the server a WHS directory (C:\WHS) copied it to my Software share (called it Home Connector2), run setup.exe and the client XP x64 machine went through the motions and connected fine.
I had my server up and running fine, did Windows Update and after a few reboots server was a happy bunny with all latest updates/patches. Turned my PC on the next day and a message popped up that new connector software was available and to download from server. Clicked yes, and it failed to do the last step configuring backups. I had Event log messages saying that the protocol doesnt match the server(!).
I first tried re-installing the connector software from the WHS disk, no joy.
Tried the Connector software from the Software share, no joy.
Found on the server a WHS directory (C:\WHS) copied it to my Software share (called it Home Connector2), run setup.exe and the client XP x64 machine went through the motions and connected fine.
No this issue is 32 bit issue and with the recovery CD not connecting to the server. I am having a 64 bit issue trying to install the connector on another computer. Will try your suggestion.
#11
Posted 14 March 2009 - 07:34 PM
The connector troubleshooter will always report this issue, as it's lookin for version 6.0.1800.0 which was updated almost immediately after PP1 was released. Its an expected result and is harmless for the connector troubleshooter.
As for the other issue (network connection issue), you may need to find the exact drivers for your client computer's motherboard, and use the Vista x86 drivers (put them on USB drive, or add them to ISO).
As for the other issue (network connection issue), you may need to find the exact drivers for your client computer's motherboard, and use the Vista x86 drivers (put them on USB drive, or add them to ISO).
#12
Posted 14 March 2009 - 11:56 PM
Drashna (WGS), on Mar 14 2009, 12:34 PM, said:
The connector troubleshooter will always report this issue, as it's lookin for version 6.0.1800.0 which was updated almost immediately after PP1 was released. Its an expected result and is harmless for the connector troubleshooter.
As for the other issue (network connection issue), you may need to find the exact drivers for your client computer's motherboard, and use the Vista x86 drivers (put them on USB drive, or add them to ISO).
As for the other issue (network connection issue), you may need to find the exact drivers for your client computer's motherboard, and use the Vista x86 drivers (put them on USB drive, or add them to ISO).
Did that, the recovery CD finds the NIC without problem without the USB drive. I did also put them on a USB drive root directory and also created a DRIVERS directory and put them there also. I told the recovery CD to search and install the drivers. The process continues as expected, prompts for the server password and starts the recovery wizard. It goes as far as the screen that displays the available backups. No available backups appear, I have left it sitting there for over 4 hours hoping it would display them. The recovery CD does not appear to work. I have also tried the recovery CD on another system and get the same results. Someone else has reported what appears to be the exact same problem on the connect web site. I have added a me too comment to connect.
#13
Posted 15 March 2009 - 04:55 AM
Drashna (WGS), on Mar 14 2009, 09:34 AM, said:
The connector troubleshooter will always report this issue, as it's lookin for version 6.0.1800.0 which was updated almost immediately after PP1 was released. Its an expected result and is harmless for the connector troubleshooter.
And what is MS doing about this? What good is a trouble shooter if it gives you wrong answers and tells you there is trouble when there is none?
#14
Posted 15 March 2009 - 07:00 PM
so to be clear here, when you can connect to the server, no available backups appear, for *any* computer?
#15
Posted 16 March 2009 - 07:25 AM
Drashna (WGS), on Mar 15 2009, 12:00 PM, said:
so to be clear here, when you can connect to the server, no available backups appear, for *any* computer?
Problem solved, details in another post. I can't confirm it now but i had installed a OS on the computer I was trying to recover. When I finally got the recovery CD to work the the point displaying the pick a backup screen they was nothing there because I told it to recover "this computer" (used same computer name as original), I should of selected "other computer". When I did that the backup displayed and I was able to recover. I think now the real cause of all my problem were that the cable modem and the router had a disconnect and was the cause of my problems.
Share this topic:
Page 1 of 1




Sign In »
Register Now!
Help

Back to top











