Remove From My Forums

Recovery disk fails

Question
0

Sign in to vote

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 "An unknown network error has occurred during PC restore. Please verify that your network connection is active and that Windows Home Server is powered on". Yes the connection is active and yes the WHS is on.

Running the troubleshooter 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?

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it
Bud - Alameda, CA

Thursday, March 12, 2009 11:16 PM

Answers

0

Sign in to vote
budgall said:

You said "If you try this please make sure you set server IP and DNS address assignment to automatic.". How do I do this?

Bud - Alameda, CA

I think the problem is the DNS server addresses assigned by DHCP. These are all addresses outside your local network. If the restore CD starts looking for your server it will do so on public DNS servers outside your network. Since these don't have any knowledge of your private network this will fail.

The best thing to do would be to enter your routers DHCP server settings, then change primary DNS server address to 192.168.1.1.

If the static IP's are assigned by DHCP (the static IP addresses are assigned by the router based on the MAC addresses of the clients) you can stop here. If the static IP addresses on the server and clients were set manually you should (at least on your WHS) change the primary DNS server to 192.168.1.1. To do this:

Logon to your WHS desktop (remote desktop is fine)
Then Start, Control Panel, Network Connection, right click Local Area Connection, select properties
On the General Tab Scroll down to Internet Connection (TCP/IP), select, click Properties
Select "Use the following DNS Server addresses"
Enter 192.168.1.1 for preferred DNS server
If you click Advanced you can also add the other DNS server addresses on the DNS tab
You can do the same on the clients that do not get IP address and DNS server by DHCP
- Proposed as answer by brubberModerator Monday, March 16, 2009 7:41 PM
- Marked as answer by Lara JonesModerator Friday, April 10, 2009 4:39 PM
Sunday, March 15, 2009 10:31 AM

Moderator

All replies

0

Sign in to vote

budgall said:
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 "An unknown network error has occurred during PC restore. Please verify that your network connection is active and that Windows Home Server is powered on". Yes the connection is active and yes the WHS is on.

Running the troubleshooter 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.

That is a known issue. You can ignore it.

budgall said:
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?

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it

Bud - Alameda, CA

For questions 2 and 3, since you used a hacked version of the WHS DVD (which includes a number of unsupported modifications), you should contact the person who made those changes (or use a properly configured WHS DVD written by MS and reinstall).

Friday, March 13, 2009 12:34 AM

Moderator
0

Sign in to vote

kariya21 said:

budgall said:
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 "An unknown network error has occurred during PC restore. Please verify that your network connection is active and that Windows Home Server is powered on". Yes the connection is active and yes the WHS is on.

Running the troubleshooter 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.

That is a known issue. You can ignore it.

budgall said:
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?

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it

Bud - Alameda, CA

For questions 2 and 3, since you used a hacked version of the WHS DVD (which includes a number of unsupported modifications), you should contact the person who made those changes (or use a properly configured WHS DVD written by MS and reinstall).

Re: Questions 2 & 3: I did use the original WHS DVD and got the exact same results. It was after the original dvd's didn't work I tried the X:File addition. Once again idential results and identical problems.
:
Bud - Alameda, CA

Friday, March 13, 2009 3:16 AM
0

Sign in to vote

budgall said:

Re: Questions 2 & 3: I did use the original WHS DVD and got the exact same results. It was after the original dvd's didn't work I tried the X:File addition. Once again idential results and identical problems.
:
Bud - Alameda, CA

Prior to installing the modified server build, you received the exact same network error? Are your server and your client on the same router (wired)?

Also, you can find all the documentation and builds we have posted to the download center here: http://www.microsoft.com/downloads/en/results.aspx?freetext=Windows%20Home%20Server&productID=2191C786-5371-4F57-8C1F-9E8F052AC847&categoryId=&period=&sortCriteria=popularity&nr=20&DisplayLang=en

Thanks!
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home Server

Friday, March 13, 2009 3:38 AM

Moderator
0

Sign in to vote
budgall said:

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it

Bud - Alameda, CA

Try:

Get hold of Windows XP drivers (or 32 bit Vista drivers) for your NIC

Copy the drivers to a USB Flash drive (copy them once to the root of the USB Flash drive and also to a folder named "DRIVERS"

When the recovery disk has detected the hardware do:

Click the Details Button

Click Install Drivers (you may need to select the NIC in this Dialog before doing this)

Click Scan

If the drivers are OK it will tell you it found drivers for your hardware.

Click OK and proceed with restore.
Friday, March 13, 2009 5:55 AM

Moderator
0

Sign in to vote

Lara Jones said:

budgall said:

Re: Questions 2 & 3: I did use the original WHS DVD and got the exact same results. It was after the original dvd's didn't work I tried the X:File addition. Once again idential results and identical problems.
:
Bud - Alameda, CA

Prior to installing the modified server build, you received the exact same network error? Are your server and your client on the same router (wired)?

Also, you can find all the documentation and builds we have posted to the download center here: http://www.microsoft.com/downloads/en/results.aspx?freetext=Windows Home Server&productID=2191C786-5371-4F57-8C1F-9E8F052AC847&categoryId=&period=&sortCriteria=popularity&nr=20&DisplayLang=en

Thanks!
Lara Jones [MSFT] | Program Manager
Community Support and Beta | Windows Home Server Team
Windows Home Server Team Blog
Connect Windows Home Server
Windows Home Server

Lara

Yes I get the same error - I think the problem is the Feb update, prior to that everything worked without problems including a restore on the same system I'm trying to restore now.

Thank you the download center link.

My current plan will be do do another reinstall but without the Feb updates over the weekend
Bud - Alameda, CA

Friday, March 13, 2009 8:36 PM
0

Sign in to vote
brubber said:

budgall said:

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it

Bud - Alameda, CA

Try:

Get hold of Windows XP drivers (or 32 bit Vista drivers) for your NIC

Copy the drivers to a USB Flash drive (copy them once to the root of the USB Flash drive and also to a folder named "DRIVERS"

When the recovery disk has detected the hardware do:

Click the Details Button

Click Install Drivers (you may need to select the NIC in this Dialog before doing this)

Click Scan

If the drivers are OK it will tell you it found drivers for your hardware.

Click OK and proceed with restore.

I'll give it a try. Thank you for the suggestion
Bud - Alameda, CA
Friday, March 13, 2009 8:41 PM
0

Sign in to vote
brubber said:

budgall said:

3. What is an unexpected network error, the message gives no clues of what the problem is or how to fix it

Bud - Alameda, CA

Try:

Get hold of Windows XP drivers (or 32 bit Vista drivers) for your NIC

Copy the drivers to a USB Flash drive (copy them once to the root of the USB Flash drive and also to a folder named "DRIVERS"

When the recovery disk has detected the hardware do:

Click the Details Button

Click Install Drivers (you may need to select the NIC in this Dialog before doing this)

Click Scan

If the drivers are OK it will tell you it found drivers for your hardware.

Click OK and proceed with restore.

Did not work. The recovery disk did discover the NIC drivers without looking at the flash drive. I told it to search anyway and it reported back that it found drivers, I told it to install but still failed
Bud - Alameda, CA
Saturday, March 14, 2009 7:10 AM
0

Sign in to vote

budgall said:
Did not work. The recovery disk did discover the NIC drivers without looking at the flash drive. I told it to search anyway and it reported back that it found drivers, I told it to install but still failed
Bud - Alameda, CA

Unknown network error is in most cases a driver problem. The restore CD will show detected NIC's and harddisks even if it doesn't have the appropriate driver. You need to make sure you have a 32 bit driver (Vista or XP) so NOT 64 bit Vista driver. The Restore CD boots 32 bit WINPE so 64 bit drivers will not work.

Can you please post details of your NIC and drivers you are using?

If it's not a driver problem there could also be some problem with obtaining IP address or name resolution. The easiest way around this would be to connect the server and the client with a crossed pair UTP cable (with most Gigabit and also some modern 10 / 100 NIC's a straight UTP cable will also work). If you try this please make sure you set server IP and DNS address assignment to automatic.

If you don't want to do this please have a look at the configuration of the DHCP server in your network (router). Check if the primary DNS server is pointing to your router and not to an external address. You can simply check this by running ipconfig /all from a command prompt on a client connected to the router. The DNS server address should be in the same range as the IP address. In most cases the DNS server address is identical to the default gateway address.

Saturday, March 14, 2009 12:55 PM

Moderator
0

Sign in to vote

brubber said:

budgall said:
Did not work. The recovery disk did discover the NIC drivers without looking at the flash drive. I told it to search anyway and it reported back that it found drivers, I told it to install but still failed
Bud - Alameda, CA

Unknown network error is in most cases a driver problem. The restore CD will show detected NIC's and harddisks even if it doesn't have the appropriate driver. You need to make sure you have a 32 bit driver (Vista or XP) so NOT 64 bit Vista driver. The Restore CD boots 32 bit WINPE so 64 bit drivers will not work.

Can you please post details of your NIC and drivers you are using?

If it's not a driver problem there could also be some problem with obtaining IP address or name resolution. The easiest way around this would be to connect the server and the client with a crossed pair UTP cable (with most Gigabit and also some modern 10 / 100 NIC's a straight UTP cable will also work). If you try this please make sure you set server IP and DNS address assignment to automatic.

If you don't want to do this please have a look at the configuration of the DHCP server in your network (router). Check if the primary DNS server is pointing to your router and not to an external address. You can simply check this by running ipconfig /all from a command prompt on a client connected to the router. The DNS server address should be in the same range as the IP address. In most cases the DNS server address is identical to the default gateway address.

Thank you for hanging in here with me. I am going to defer my reinstall as I think I'm about to learn some more about networking. My current knowledge is enought to get a simple network running but not enought to keep me out of trouble.

You said "If you try this please make sure you set server IP and DNS address assignment to automatic.". How do I do this?

The following is the result of a ipconfig /all command:

Windows IP Configuration:
            Host Name                        PCTREE
            Primary DNS Suffix            (blank)
            Node type                         Unknown
            IP Routing Enabled           No
            WINS Proxy Enabled         No

Ethernet Adapter Local Area Network Connection:
    Connection Specific DNS Service:
            Description                    Broadcom NetXtreame Gigabit Ethernet
            Physical Address           00-E0-81-XX-XX-XX
            DHCP Enabled               No
            IP Address                    192.168.1.82
            Subnet                          255.255.255.0
            Default Gateway           192.168.1.1
            DNS Servers                    24.143.xxx.xxx
                                                  204.174.xxx.xxx
                                                  204.174.yyy.yyy

NIC Information taken from Device Manager:
        Broadcom NetXtreame Gigabit Ethernet
        Driver: provider Broadcom Corp.
        Version : 8.22.1.0
        Dig Signed : Microsoft Windows Hardware Compatibility

Router Information:
    Linksys BEFSR41 V4.1
    Firmware : 1.04.09 dated 9/13/06 (latest available)

    Local DHCP Server Enabled
    DHCP Range    192.168.1.100  to 192.168.1.149
    Lease Time      65535 minutes
    DDNS Service   Disabled
    Server Static IP (WHS)      192.168.1.75
    Client Static IP (PCTREE)    192.168.1.82
    Default Gateway                192.168.1.1
    DNS Servers                        24.143.xxx.xxx
                                              204.174.xxx.xxx
                                              204.174.yyy.yyy

All computers on the network have static IP's except a laptop that is DHCP

Again thank you
Bud - Alameda, CA

Saturday, March 14, 2009 7:22 PM
0

Sign in to vote
budgall said:

You said "If you try this please make sure you set server IP and DNS address assignment to automatic.". How do I do this?

Bud - Alameda, CA

I think the problem is the DNS server addresses assigned by DHCP. These are all addresses outside your local network. If the restore CD starts looking for your server it will do so on public DNS servers outside your network. Since these don't have any knowledge of your private network this will fail.

The best thing to do would be to enter your routers DHCP server settings, then change primary DNS server address to 192.168.1.1.

If the static IP's are assigned by DHCP (the static IP addresses are assigned by the router based on the MAC addresses of the clients) you can stop here. If the static IP addresses on the server and clients were set manually you should (at least on your WHS) change the primary DNS server to 192.168.1.1. To do this:

Logon to your WHS desktop (remote desktop is fine)
Then Start, Control Panel, Network Connection, right click Local Area Connection, select properties
On the General Tab Scroll down to Internet Connection (TCP/IP), select, click Properties
Select "Use the following DNS Server addresses"
Enter 192.168.1.1 for preferred DNS server
If you click Advanced you can also add the other DNS server addresses on the DNS tab
You can do the same on the clients that do not get IP address and DNS server by DHCP
- Proposed as answer by brubberModerator Monday, March 16, 2009 7:41 PM
- Marked as answer by Lara JonesModerator Friday, April 10, 2009 4:39 PM
Sunday, March 15, 2009 10:31 AM

Moderator
0

Sign in to vote

Well I am now backup and running. I managed to totally trash my network and internet connection. So I shutdown everything including the cable modem and router. Restarted them all, which got the network and internet back. Made you suggested changes. Retryed the recovery and got a successful restore. So then I tried to reinstall the connector on my laptop which had been refusing to install and that worked. It appears that all is well again.

Thank you for all your help
Bud - Alameda, CA

Monday, March 16, 2009 6:14 PM
0

Sign in to vote

budgall said:
Well I am now backup and running. I managed to totally trash my network and internet connection. So I shutdown everything including the cable modem and router. Restarted them all, which got the network and internet back. Made you suggested changes. Retryed the recovery and got a successful restore. So then I tried to reinstall the connector on my laptop which had been refusing to install and that worked. It appears that all is well again.

Thank you for all your help
Bud - Alameda, CA

OK, glad it all worked out in the end!

Monday, March 16, 2009 7:24 PM

Moderator

Answered by:

Recovery disk fails

Question

Answers

All replies