Solved

Windows Complete PC Restore (Windows 2008) can't access network location after successfully finding it (error code 0x80070043)

Posted on 2008-06-10
27
7,016 Views
Last Modified: 2011-10-19
Hi Guys

We're thinking of upgrading to Windows 2008 server. As part of the testing, I've been creating complete server backups (block based) using the built in backup tool, and have successfully recovered them as new installations on other servers, using external hard drives. Works a treat.

As our backup will always be accesible from a NAS box (as tape drive is not supported directly by Win 2008 backup) we would do recoveries from there if need be also. We don't have the NAS box yet, so to simulate the situation I have setup a standard Windows network share on a system that is not part of the domain, and the share is accessible to everyone. I have tested it, and it can be written and read from any computer. I made sure it was a non domain joined computer, as this created seperate errors.

So, I start up our recovery test server from DVD, and boot to the start of the install. I select 'repair my computer' and the option for doing a complete restore. I then go through the various hoops, till i get an option to locate the restore file on the network. I select this option, and then stipulate the share. It must find this as it asks for username and password, which I give it. This is where it fails. It states:

"An internal error occured. The following information may help you resolve the error:

The network name cannot be found. (0x80070043)"

No matter what I do to the share, it doesn't like it. Do I have to use a host name in the locating? It would seem it should be fine with the IP in my mind. I'd try using the host name, but it is an Apple Mac system that I'm not 100% sure of the Win host name it uses, assuming it has one (and it doesn't register anything in our MS DNS server, as it routes DNS queries straight to our firewall / edge router). I couldn't put the share on a Windows machine, as they are all part of the existing domain and the restore software doesn't like this identifying a 'computer trust account' issue, or such like....

I bring up the console from the main recovery screen, and ping the host that has the backup on it. All comes back fine.

Incidentally, the recovery (and the original backed up server) are both virtual machines running udner vmware. I don't see why this should be a problem, a it is clearly getting network access, but if anyone can shed light on this, I'd be really grateful!

Many thanks,

Bluemercury
0
Comment
Question by:bluemercury
27 Comments
 
LVL 63

Expert Comment

by:SysExpert
ID: 21763661
It could be that win 2008, wants a more secure network device, perhaps one on a Domain .

I would test with a windows server rather than a  Mac, or perhaps a Linux machine with SAMBA.

Also check to see if you can lower the security requirements for a network connection during a restore.

   
I hope this helps !
0
 
LVL 1

Author Comment

by:bluemercury
ID: 21767916
Hey SysExpert - thanks for posting.

You'll see I mentioned in my post that I originally tried restoring a backup contained within a share on the domain. It didn't like this at all, claiming that the computer (itself) was not a trusted system on that domain, and refused to access the share (even though I'd given it full credentials). At some point I might run that test again, so I can post the exact error message and google it for other posibilities.

I agree that having the share on a PC rather than a Mac is more ideal, as I know Macs don't support Server Message Block signing (or certainly didn't on OS X.3 when I looked into this - they may be supported on Leopard which I now have, but haven't looked into it). In the last day I have created the backup again on a non-domain Windows system, shared the folder, and have exactly the same problem.

The only thing I can now think is that it really does want a host name included in the folder map, instead of an IP address. To do this, I'm setting up a system that I won't join to the domain, put will point to our DNS servers and allow it to register, so I can resolve based on Host name (I tried using host name before, but as it could only be seen by doing a broadcast, it didn't seem to find the machine)

It's all bit of mystery. Thanks for your points, but these are already in consideration - I'm going to run further tests and report back here.

Thanks for your time.

Bluemercury
0
 

Expert Comment

by:d_ruiz27
ID: 21814997
I'm having the same issue w/ doing a recovery from a network HD on Windows Server 2008.  It seems when you boot into the Recovery CD you're given a loopback IP interface.  No matter what I try I can't browse the network to my NetHD.  I'm prompted for a password when I shouldn't be.  I tried adding a new interface using the "netsh" command, but wasn't successful.  All the research I've done says Server 2008 only wants you to be able to do a recovery from an extra internal HD or an external USB drive.  If that is so, then why do they even give you the option of browsing the network to do a recovery?
0
 
LVL 1

Author Comment

by:bluemercury
ID: 21986351
This question is not abandoned. I'm still working to find a solution, but have failed to thus far. I'm hoping that someone on Experts Exchange may reach a conclusion at some point - other people are clearly having the same issue, but I suspect Microsoft have yet to resolve it for anyone. If the question can be left open for longer, I hope this will ultimately bring about a solution, or that I find a solution. Either way, I think the comminity will benefit.
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22168519
My status still remains the same. I've yet to find a solution, but there must be one at some point. Microsoft can't ignore this continued error, and I am pursuing it through other channels.
If you really have to close the question that is your choice, but I re-affirm that as soon as I have some kind of solution to this problem, I will post for the benefit of the community. I've found other people suffering with the exact same bug elsewhere, and we are all looking for a solution....
Best wishes,
Bluemercury
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22436763
Hi Tigermatt.
I still have yet to find a solution. Lots of other forums out there have postings in the same status of limbo. I think Microsoft still haven't fixed this problem, and others are still suffering - a shame because the feature would work great otherwise :(
I'll leave the deletion of the question at your discretion - I only left it open so that I could post to the community if a solution is ever found, and benefit Experts Exchange.
Best wishes,
Bluemercury
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22462714
No worries Tigermatt - thanks for your reply; I will watch this space!
Cheers,
Bluemercury
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22683367
Hi Tigermatt
I have found implication in VMware's documentation that the pre boot environment for Windows 2008 server is more widely supported (in VMware server 2). This has some implications that the network recovery support may be added.
It is worth noting however that this problem also occured on physical machines that could obtain a network connection, as well as virtual machines.
How about we leave the question open for 1 more week, and if I don't have something conclusive, let's bin it?
Many thanks,
Bluemercury
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 22684707
If that is what you would like to do, then that's what we'll do!

-tigermatt
0
Threat Intelligence Starter Resources

Integrating threat intelligence can be challenging, and not all companies are ready. These resources can help you build awareness and prepare for defense.

 
LVL 1

Author Comment

by:bluemercury
ID: 22685664
Thank Tigermatt - I'll be back :)
Best wishes,
Bluemercury
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22730480
Ok - here is my latest post. Within the new setup, I am still having the same problem. I now have Windows 2008 x64 booting in recovery mode inside a virtual machine running on VMware Workstation 6.5.
I enclose a screenshot. The purpose of the screenshot is demonstrate that there is clearly a network connection (note the console I have in the background, with basic IP stuff given out no probs from our DHCP server - I can also ping other IPs and host names from this console) When the path to the shared folder is put in, with all the correct credentials, the error message you see in the foreground appears. Very frustrating!
I have continued to google this, and find so few people with the same problem (and no resolutions). I'm downloading a new trial version off the MS website, in case there is something strangely wrong with this version I have - a free gift from Microsoft at the 'Heroes Happen Here' launch event back in March.
Will report further findings.....

Win-2008-x64---Failing-to-access.JPG
0
 
LVL 1

Accepted Solution

by:
bluemercury earned 0 total points
ID: 22875248
I have had some success with this problem! It would seem that whilst you should be able to log into a secured share with credentials from the recovery environment, it doesn't work. To explain further, the share that contains the backup has been previously setup as shared to everyone, but the NTFS security permissions are set more tightly. In the case of our network, I had set the share so that only admin accounts could access it.
When I browsed for the share and tried to do a restore, I got the above error message, even when entering the correct domain, admin user and password, as specified as possible with MS literature. It never worked though, hence I created this post.
The other day I had a brainstorm that this might be the bug, and I've now set security permissions so that the 'Everyone' group has full read / write NTFS permissions to the share. Whilst this is unsuitably insecure, I've made the security low to test this therory, and it works. The restore environment can now see the share, and correct accessed all the information on it.
I now have a new problem though, which I may post seperately. When I set the various options for restore, at the end I'm told my restore volume is not big enough. It is in fact more that big enough (100 Gb for a 30 Gb backed up partition), but this must be a problem to do with vmware virtualisation. The error box (which I have included) certainly indicates this. Another problem for another day - I'm working on a solution to this, so will comment again if I find one.
Going back to the primary issue, I think on another setup this restore would now work fine. I also expect that seting the security so that the 'Everyone' group just had general read rights only will probably be sufficient to work (with no need for write) but I haven't tried this yet. This is a sloppy bug on MS' part, and I hope they fix it with a revision of the Pre-boot environment in the future.
Incidentally, at the start of this post there may have also been an issue with VMware's software. As explain, I have upgraded to VMware Workstation 6.5 during the issue, and I read somewhere in their release notes that there are improvements to support the Windows 2008 / Vista Pre Boot Environment, which could have affected these things.
Thanks for all that offered any input on this.
Bluemercury

new-restore-error.JPG
0
 
LVL 58

Expert Comment

by:tigermatt
ID: 22878848

Bluemercury,

You found a solution! I'm quite glad you managed this actually, and that you kept objecting to my cleanup requests on this post - it will definitely be something other members of EE will need in the future, so thanks once again for posting this!

Cheers,
-Matt
--tigermatt
0
 
LVL 1

Author Comment

by:bluemercury
ID: 22879160
Many thanks, Tigermatt. Thanks for letting me keep it open so long! I thought I would find some kind of solution in the end, I'm just amazed there isn't more publicity on this on the Web. I can only assume that not many people are using the recovery console with Windows 2008 yet (or haven't had cause to, but may have an unpleasent surprise when they're in the midst of needing to recover a server!). Hopefully this post will be of some use to people when they do hit this hurdle.
All the best,
Bluemercury
0
 

Expert Comment

by:exzile1
ID: 23416174
Hi Guys,

I'm having problems with this also. I get a Loopback Pseudo-Interface 1" and I can't change it. We are only using static IP's so DHCP is not an option for me.


Can someone please tell me how to add a local area connection. I've tried with the netsh command and it gives me a error. " The Filename or volume syntax is incorrect"

Its not because it works in windows, just not with the windows 2008 setup disc
0
 
LVL 1

Author Comment

by:bluemercury
ID: 23445447
I have not tried setting up things with a static IP configuration. However, one quick step I can recommend is that you just setup a temporary DHCP server. The chances are you've already got a basic DHCP device kicking around (such as a cheap and cheerful router) or you could temporarily configure it from a Windows server.
Also, I suspect that the Windows Pre-boot environment doesn't support every NIC under the sun. It could be a problem with your card.
I haven't re-read the question I posted above (it was little while back) but hope that sheds some light. If not, I highly recommend you post a new specific question on EE regarding this, and someone else is more likely to come back to you.
Best wishes, Bluemercury
0
 

Expert Comment

by:tauruz74
ID: 24058786
I had the same problem and simply fixed it by deleting the existing network adapter that was created when I set up the Hyper-V machine and adding a legacy network adapter instead.
 
0
 

Expert Comment

by:yefrad
ID: 34142127
Most likely you tried to restore from network share stored on the Domain based PC:

http://technet.microsoft.com/en-us/library/cc755163.aspx


Part of the article:

If you use a domain in your environment, and if the backup storage location is on a computer that is a member of that domain, then computer containing the storage location should be on the IPsec boundary to be accessible by non-domain computers. When a computer boots into Windows Recovery Environment, it becomes a non-domain computer and cannot access the usual network shares. Only those computers that allow non-domain computers to access the share can be used as a backup storage location in this way.

You can also address this issue by adding the computer that is your backup storage location to a workgroup and placing the backup in a shared folder. A computer running Windows Recovery Environment behaves as if it is in a workgroup, enabling you to access the shared folder with the backup.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

Restoring deleted objects in Active Directory has been a standard feature in Active Directory for many years, yet some admins may not know what is available.
A procedure for exporting installed hotfix details of remote computers using powershell
This tutorial will walk an individual through locating and launching the BEUtility application and how to execute it on the appropriate database. Log onto the server running the Backup Exec database. In a larger environment, this would generally be …
This tutorial will walk an individual through the process of installing the necessary services and then configuring a Windows Server 2012 system as an iSCSI target. To install the necessary roles, go to Server Manager, and select Add Roles and Featu…

707 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

17 Experts available now in Live!

Get 1:1 Help Now