Salta al contenuto principale

Rescue media not seeing network share

Thread needs solution

I just used True Image 2016 (build 6569) to create rescue media from a USB drive.  When I booted from it and ran the program, it didn't show any of the PCs (all Windows) on my LAN... the only thing listed under "computers near me" was "NFS," but I don't have anything NFS on the network.  

Another USB drive had the 2014 edition of True Image rescue media on it, and it was able to see the network shares from that one. 

Anyone else see this?

0 Users found this helpful

When you boot the media, up at the top is "network options".  Click on it and it will open up a network configuration box.  Does it show you have an IP that matches your network (169.x.x.x or nothing would mean you're not getting an IP).  If so, do you have another machine that can ping that IP as a test.

Keep in mind it only works with wired NIC's - wireless is not supported so you have to be physcially connected too.

If you have an IP and network access, you should still be able to connect to shares by going to Recovery >>> browse for location.... in the file name, type the UNC path or IP of the remote share and you should get prompted for credentials:

Example:  \\my-pc\sharename                 username = my-pc\username    (replace my-pc with your PC's name, sharename with the actual share name, and username wit a username that has write access to that share)

What's your NIC?  Did 2014 work with the same NIC or is this a different machine?  6569 has pretty good driver support out of the box now, but if you have a newer machine, it's possible the NIC is newer than the drivers in the build. If that's the case (you're not getting an IP address), then you want to download and install the Windows 10 ADK from Microsoft.  Then rebuild your resuce media and select WinPE and it will build a Windows PE version of the rescue media that will most likely have the drivers by default since the Windows 10 ADK has pretty good driver support out of the box too. 

It shows correctly, 192.168.1.whatever, with default gateway and DNS as 192.168.1.1, as they should be. FWIW, there is an option on the left pane for wifi too (inside the network options), and it did see the available wireless networks, though I am using a wired connection here.

The tip for using the UNC pathname worked... I do that all the time from Windows Explorer; I don't know why I didn't think of it here, but it did work. 

The 2014 worked with the same PC only a few minutes earlier, just booted from the 2014 rescue media (USB drive) instead of the 2016.  It happens that way on both of my PCs on which I tried it... one a Sandy Bridge desktop with the onboard Intel Gigabit ethernet, one my Core 2 Duo laptop with the onboard Realtek Gigabit.  Neither of them is new.

Thanks for the info-- it still should be fixed, but at least I have a workaround now!

 

 

 

 

Glad to hear it.  I'll have to go back and check the wireless settings myself.  I've never seen it, but if it's there and picks up the networks too, that's great.  I just checked WinPE and it does not pick up the wireless or have a wireless option there though, but there are third party tools or portable apps that can be used with the WinPE to do this as well.