Answered by:
Cannot Connect to WHS During PC Restore

Question
-
After months of successful WHS operation, I finally had a need to restore a failed XP Pro SP2 machine that managed to corrupt a registry. I thought no problem. I loaded the Home Computer Restore CD, had my USB stick ready with all the drivers for the specific system and then went through the motions. After providing the WHS password during the restore process, I receive the error "An unknown network error has occured during PC Restore...Please verify that your network conntection is active and that your Windows Home Server is powered on."
The WHS System (built from the ground up with the latest WHS OEM distro and latest updates) is working fine. Nothing abnormal shows up in the logs. I can ping the server from other workstations and can also ping the failed XP Pro system. All the systems operate in a designated workgroup. I am using a D-Link DIR-655 Router and DGS-2208 Switches. All systems have Gig cards and are on the same subnet. I've turned the NetBIOS announcement both on and off to no avail.
One important note. When I initially brought up WHS, I had a lot of difficulty getting the Home Server Connector Software to discover the WHS server. I had this problem with all my networked clients (consisting of mostly Vista Ultimate and some XP Pro systems). After a lot of cursing, I decided to include the fixed IP address of the WHS server in the hosts table and life was then wonderful. All of the clients then recognized the WHS server.
I suspect that the Restore software cannot resolve the host name since I obviously had this problem on initial installation of the Connector Software. Obviously, no way to include a hosts table on the "crashed" PC I am trying to restore.
I've looked at all the MS Tech Briefs, KB items and posts until I am blue in the face and don't see similar problems (perhaps I didn't look hard enough). Thanks in advance for any help and/or direction. It would be greatly appreciated.
Saturday, December 22, 2007 8:59 PM
Answers
-
Try disconnecting the network from the Internet and trying again; it's name resolution that's the problem.
Saturday, December 22, 2007 9:33 PM
All replies
-
Try disconnecting the network from the Internet and trying again; it's name resolution that's the problem.
Saturday, December 22, 2007 9:33 PM -
Thanks. That fixed it. I should have worked through it one step further.
I can't believe MS intentionally designed it that way. There are so many other ways to do it without taking all the users down.
Again, thanks again.
Saturday, December 22, 2007 11:50 PM -
Glad that did the trick! MS didn't design it that way, but it seems the way some ISPs and/or routers are configured causes the problem.
Are you using OpenDNS? If not, it could be useful to know your ISP and router.
Saturday, December 22, 2007 11:53 PM -
Thanks for the feedback. I was just think about hosting my own DNS on the server. I'm not familiar with OpenDNS. I'll take a look.
Thanks again.
Sunday, December 23, 2007 12:50 AM -
I just made a post here under Hardware - Networking - Lessons Learned:
http://mswhs.freeforums.org/viewtopic.php?t=143
Different router but trying turning DHCP on and use static IP's that are out of range of the routers DHCP addresses. I'm now able to perform restores with no problems.
The other BobS.....
Sunday, December 23, 2007 2:56 AM -
Microsoft needs to fix this already.
For those who don't understand the issue: PC Restore will fail if your internet router / NAT box is set up to provide DNS servers over DHCP. For example, I named my home server "HOME". When I boot the client restore CD, it finds my server, then tries to talk to "HOME.rr.comcast.net", which of course is some random machine somewhere on the internet.
Compounding the problem is that the boot environment is set up to automatically append DNS suffixes, which it will cheerfully download from your DHCP server. There's no way to reconfigure this in the limited environment of the restore CD (shift-F10 doesn't work).
You can get the restore to work one of several ways:
1. Plus the computer you're trying to restore directly into the Home Server. That means taking a network cable and directly connecting the two computers, with no router or switch in between. This will force both machines to use Windows Private addresses. Obviously all other users will be disconnected from the server until you plug it back into the network.. real professional.
2. Get your own DNS server running, possibly on the WHS machine.
Attention stubborn WHS team at Microsoft: Notice how neither of these options are something a computer novice would even think of doing??
Fix this already. You shouldn't be trying to resolve a server name in DNS. Most people don't have any control over their DNS; they use DNS servers belonging to their ISP. Once you find a server using broadcast IP packets, just use the IP address you've already discovered.
Sunday, December 23, 2007 5:54 AM -
@Maniac - DON'T go for OpenDNS, it has proved to be very problematic for a number of posters here, which is why I wondered if you were using it.
If you're able to organise a DNS server there (as I have) then for my money that's the way to go.
Sunday, December 23, 2007 1:59 PM -
Crash2975 wrote: @Maniac - DON'T go for OpenDNS, it has proved to be very problematic for a number of posters here, which is why I wondered if you were using it.
If you're able to organise a DNS server there (as I have) then for my money that's the way to go.
Thanks for the "heads-up" and to everyone else that has posted. I have a copy of SimpleDNS Pro that in the past has runned flawlessly. I may give that a go until MS recognizes that this is a serious issue and fixes it.
Sunday, December 23, 2007 3:30 PM -
Crash2975 wrote: Try disconnecting the network from the Internet and trying again; it's name resolution that's the problem.
Apparently this is still an "issue"? I've never needed a restore and I figured I would through the process to avoid any surprises later if I really do need a full restore. I had to unplug the WAN cable from my Linksys router, otherwise I could not do the restore. As soon as I unplugged that cable the restore was fine.
My WHS is named "SERVER" and all my PCs are on the same LAN subnet. I'm running WHS with PP1 on a home built system. Is there another solution to this, router settings or something, that I should be trying?
Steve- Proposed as answer by CokoBWare Monday, January 26, 2009 12:02 AM
Thursday, August 28, 2008 11:36 PM -
I have been unable to run PC restore. My PC is running Vista with bitlocker. The hard drive has two volumes: C and S. The S drive is a bitlocker utility. It restores successfully. The C drive restore starts ok but then fails. Do you think that this is a name resolution issue or is it something relating to bitlock?
I tried direct connect from server to PC - no luck. I also tried disconnecting the internet connection - still no luck. I have read that the backup is not encrypted even when using bitlocker. So I don't think bitlocker is the problem. I would appreciate some advice on this issue. What good is a backup if you cannot use it to do a restore.
Note that I have DHCP on the server and static ip on the pc. I use DHCP reservation and a host file entry to keep the connection between the server and the pc. The PC restore cd will not find the server unless it is using dhcp. When I had previously set the server to static ip, the pc restore could not find it so I changed it back to dhcp.
I have changed the server name from the default name server to hpserver. Would changing the name to server help. I think maybe the pc restore uses the default name because there is no way it can use host file during restore - only a suspicion.Friday, October 17, 2008 4:12 PM -
Eddie88 said:
I have been unable to run PC restore. My PC is running Vista with bitlocker. The hard drive has two volumes: C and S. The S drive is a bitlocker utility. It restores successfully. The C drive restore starts ok but then fails. Do you think that this is a name resolution issue or is it something relating to bitlock?
I tried direct connect from server to PC - no luck. I also tried disconnecting the internet connection - still no luck. I have read that the backup is not encrypted even when using bitlocker. So I don't think bitlocker is the problem. I would appreciate some advice on this issue. What good is a backup if you cannot use it to do a restore.
Note that I have DHCP on the server and static ip on the pc. I use DHCP reservation and a host file entry to keep the connection between the server and the pc. The PC restore cd will not find the server unless it is using dhcp. When I had previously set the server to static ip, the pc restore could not find it so I changed it back to dhcp.
I have changed the server name from the default name server to hpserver. Would changing the name to server help. I think maybe the pc restore uses the default name because there is no way it can use host file during restore - only a suspicion.
No, it definitely has nothing to do with the default server name (mine is neither server nor hpserver and mine works).
Have you tried downloading the new Power Pack 1 restore CD?Saturday, October 18, 2008 5:11 PMModerator -
I found the solution to my problem. I just reformatted the destination volume for the restore to NTSF. Then the restore ran successfully. Apparently, when bitlocker encrypts a volume on the hard drive, the file system is changed from NTSF to raw. PC restore apparently can run restore to a destination volume unless it uses NTSF.
When I ran the restore wizard and got to the screen that shows the source and destination volumes, I clicked on drive management, corrected the drive letters, selected the bitlocker encrypted volume (the C volume), right clicked, and selected format. I made sure NTSF was selected and ran the formatting. After the formatting was finished, I continued the restore. The result was a restored but unencrypted pc. This is because the backup on the server is unencrypted. Now I need to run bitlocker again to reencrypt my hard drive.
I understand that server 2008 has the ability to perform encrypted backups. WHS is based on server 2003. Even when the hard drive on the pc is encrypted with bitlocker, the backup on the server is not encrypted. If anyone needs an encrypted backup for better security, he would have to use some third party software such as EMC retrospect, get server 2008, or backup to a second hard drive on the PC. Originally Vista's bitlocker feature did not permit an enrypted backup to a second hard drive. With SP1, it now does. This is a good solution but I like the way that WHS does automatic backups. I figure the password protection on the server gives me some protection, but I suspect that there is a way to get by the password, although I personally don't know how to do it. I hope microsoft includes encryption on its next release of whs.Monday, October 20, 2008 3:21 PM -
I noticed a typo in my last post. I should have said that apparently pc restore canNOT run successfully unless the destination volume is NTSF.Monday, October 20, 2008 3:25 PM
-
So after reading through numerous threads online, this seemed to be the most sensible thread to post my experience.
Situation:
Windows XP Pro SP3 laptop died. Needed to restore backup from Home Server. Quickly discovered I was unable to connect my laptop to the home server as I was getting the infamous name resolution problem. Tried drivers, plugging and unplugging the "internet" from my router. Nadda. Configuring the workgroup name in the "domain name" field in your router config is not a 100% sure-fire to get this all working. I tried it, and it failed miserably.
Solution:
Using a Fast ethernet switch and disconnecting the switch from my router (no other devices should be plugged into your switch), I plugged the Home Server and the laptop into the switch, and rebooted both machines. Once the Home Server was up, I booted up the restore CD and went through the motions. It detected the home server, and I was able to select the correct backup to bring the laptop back to life.
Problem solved.
WHS team, please look into fixing this for the next PP.
- Proposed as answer by CokoBWare Monday, January 26, 2009 12:02 AM
Monday, January 26, 2009 12:02 AM -
Unfortunately, name resolution issues are external to the server; they are usually the result of network configuration problems, which is not something that Microsoft can really correct.
I'm not on the WHS team, I just post a lot. :)Monday, January 26, 2009 12:26 AMModerator -
While name resolution issues may be external to the server, the server can use other methods for connection. The server name is only used to resolve to an IP address. Once that address has been found the address is used in the actual IP messages. At the time of the password entry screen in the restore software, the server has been found and identified. I assume a broadcast message has been sent to it and response received. The response should contain the address of the server. Since they have the address at that point they can send messages by address and not by name and this whole problem would be avoided.
The main point to all of this is that this is supposed to be a "Home" server and is being targeted at people who don't have a whole lot of skills with networks, etc. If this is a common problem with the home infrastructure then it becomes a problem Microsoft needs to resolve. They can't just say it isn't something they cannot correct. If there truely is an issue that they need to put a work around in for a restore (e.g., disconnect router WAN port) the recovery software needs to lead the user through this and not simply fail with no obvious path to follow.Monday, September 7, 2009 4:21 PM -
@Crash2975 Thanks! that fixed my problem too.Tuesday, October 27, 2009 8:19 AM
-
your missed the glaring TYPO of calling NTFS by transposing the last two characters repeatedly - NTFS = new technology files system
I am surprised that Home Server Restore cares what the drive is formatted with since it supposed to completely redo the formatting regardless. In fact if you are doing a disaster recovery to a new hard drive, you may be using an entirely unformatted drive out of the box.Sunday, November 29, 2009 6:01 PM -
Even if I've typed the known IP address of the Home Server (bypassing DNS and cache tables) into the 'find' box, it immediately has a problem finding it; it's as if no effort was even made.
WHS can provide the ability to diagnose if the NIC is functioning, verify it can see a DHCP server and a routing table, allow for a reload of a different driver, ...etc. But at this point your only option is to reboot and pray. This is an unacceptable waist of time IMHO.- Edited by Dale DU-IT Tuesday, July 13, 2010 2:10 PM
Sunday, November 29, 2009 6:06 PM -
Hi, as I went through the exact same problem for a vista 64bits laptop, I found and read this post (an unknown network error has occured during PC Restore...Please verify that your network connection is active and that your Windows Home Server is powered on."
However for my own I just had to download the new restore cd from microsoft (http://www.microsoft.com/downloads/details.aspx?FamilyID=26881305-91cc-4f37-b1fc-3813c423df2c&displaylang=en) and it solved all the problem.
I hope this info could be usefull for someone else.
cheers.
Thursday, March 4, 2010 12:55 AM -
I alos had a problem and recieved the same error message. In my case the solution was to use an external NIC (Toshiba L500 Laptop) The NIC in the laptop (Realtec) would not connect to the server. Installing a USB NIC with the drivers on a USB stick solved my problems. An hour later I was back up and running.
George
Sunday, April 25, 2010 1:43 PM -
I have downloaded the new restorecd.msi which is a .msi file. The original CD was a bootable CD. What do I need to do in order to boot from this new download ?Sunday, June 6, 2010 8:36 PM
-
I have downloaded the new restorecd.msi which is a .msi file. The original CD was a bootable CD. What do I need to do in order to boot from this new download ?
There are some nice instructions here: http://www.howtogeek.com/howto/10986/create-a-windows-home-server-home-computer-restore-disc/Friday, June 18, 2010 4:44 AM -
I have downloaded the new restorecd.msi which is a .msi file. The original CD was a bootable CD. What do I need to do in order to boot from this new download ?
There are some nice instructions here: http://www.howtogeek.com/howto/10986/create-a-windows-home-server-home-computer-restore-disc/
I'm having the same problem. I'm trying to restore my desktop computer and The restore cd comes up, but It will not locate my server either manually or automatically. I can not get anywhere. I have the latest restorecd software. I even tried from my laptop to see if it could find the server but that didn't work either. I can boot into windows on my desktop and get to my server just fine.Friday, July 9, 2010 1:32 AM -
I now have a related tip learned after now having used WHS to restore desktops and servers since my last post on this thread. From any WHS connected computer you can view the backup of any backup including the one of the now needed target of a recovery. From within that ‘Open’ ed backup you will see on the C:\ partition a folder intuitively labeled Windows Home Server Drivers for Restore. This has every driver you will need for the restore to be successful including any NIC drivers. Copy that entire folder onto a USB thumb drive. Use that USB thumb drive during your Home Server recovery and have the software scan it when the option is available.
The only other problem you could have beyond the drivers is that of routing. I've hit this myself in complex business network environments. You shouldn't experience such complexity in a typical home. So if you suspect routing issues are the case for you, then you can directly connect your target machine to the WHS via a crossover cable or place a switch in the middle and use standard Ethernet cables. Run the WHS restore CD again and it should work.
Tuesday, July 13, 2010 2:34 PM -
Great! Your are number 1! Thank you from Itay!!! After 2 hours of trying a restore I was going crazy!!!!Sunday, July 25, 2010 2:18 PM
-
I am having a great deal of trouble getting my client to connect to the server for a restore as well. I have retrieved the drivers and that didn't help, so I directly connected my server to my client using an ethernet cable and that doesn't work either. What is a crossover cable? Why do I need a "switch" if I'm connecting directly using an ethernet cable and what is a "switch"?
I'm confused since in the past I have used an ethernet cable to connect directly to my server to run the server restore software from my client. That worked fine. Why isn't this working when I need to restore a client machine of a backup on the server?
I welcome any ideas an explainations you might be able to provide.
Thanks in advance,
inouridr
Tuesday, August 10, 2010 3:56 AM -
Make sure that DHCP server is working correctly on your network. Your newly CD-booted machine needs a proper network IP address to find the server. Installation does not let you specify a static IP address, it has to be assigned by the server. From there on, smooth sailing.
Friday, September 30, 2011 3:20 PM -
Had same issue. Here is how I resolved it. On the PC Restore disk I found a windows/system32/Drivers folder. The HOSTS file is in this folder. I copied the entire disk to a folder on another computer. Then I edited the HOSTS file to include the IP address of my server.
I added the line:
HOMESERVERNAME 192.168.3.14
(Where HOMESERVERNAME=name of my home server and the IP address of my server. You'll need to determine your own server's IP address. )
I then copied the entire folder contents I created on a working computer to a CD that I used to boot from. Only now it used the altered HOSTS file and found my server.
Tuesday, November 22, 2011 3:08 AM