Rescue Media is refusing to let me access my NAS


- Se connecter pour poster des commentaires

I meant to post here awhile back too, and totally forgot.
FYI, Bruno and i did some offline testing. Long story short, he can reach his NAS in 2019 ATI with WinPE using ADK 1803 or 1809. But in 2018 ATI, he has the same issue regardless if using ADK 1803 or 1809. So, ultimately, 2018 rescue media with WinPE seems to be buggy as compared to 2019 - at least with some NAS devices.
- Se connecter pour poster des commentaires

Hey, just curious if BrunoC or someone else wants to test... I was just playing around in the Custom MVP winRE I built and testing wifi with Penetwork.
1) It made connecting to wifi really easy just by selecting the wireless adapter in the dropdown, picking my SSID (which it found easily) and entering my password
2) I went to the network drives tab and entered my NAS share path (it let's me put the full path in too so suspect this would work well for BrunoC) then my username and password and it mapped it as Z: without any issues. Acronis found it easily and it worked great.
- Se connecter pour poster des commentaires

Bobbo, I'd be happy to test but I know nothing about PENetwork. Are you looking for a situation where the drive is connected through WiFi? You can PM me with further details.
- Se connecter pour poster des commentaires

Bruno,
Nothing special needed, and no, does not require wireless - just found it useful to connect to wireless as well and while I was testing that, noticed it has a "network drives" feature too.
In you're case, just curious to test the connection of mapping a drive with penework instead of command prompt "net use" or A43. It seems to allow you to enter the complete path of the share and credentials before ever trying to connect so may make the process easier in some cases when mapping as a drive letter.
PEnetwork is an application built right in the MVP tool at the bottom of the rescue media taskbar when you boot up. Just double click to open. Then select the "network drives" option on the left side and enter your info.
- Se connecter pour poster des commentaires

I just booted my MVP boot drive to try this. After doing so, I realized that I had edited map.cmd to provide access to my NAS, although I did not actually assign a drive letter. When I then ran PENetwork, it already had my NAS listed, although the first column did not show a drive letter (as expected).
- Se connecter pour poster des commentaires

Ah, OK. Well, if you ever need to map a drive differently and aren't using the automated mapping, looks like it could be an option. I'm pretty impressed with it's ability to connect to wireless (in WinRE) and to connect to mapped share drives (on the LAN or WLAN).
- Se connecter pour poster des commentaires

Thanks for the insight, Bobbo. I will keep it in mind.
- Se connecter pour poster des commentaires

Clearly from all the lingo here and having access to GUI and a true DOS prompt, this situation is not the same as mine.
HOWEVER, I got the same error message when trying to 'restore' and image that I had copied to a USB flashdrive using the 'backup' utility that is found in Window10.
(unfortunately most of my issue stems from the backup utility being developed for its predecessor Windows 7 environment and not all applicable to today's technology.)
***
I created an image on a USB drive to transfer to a new SSD drive.
The recovery disk could not automatically find the USB connected flashdrive to perform this action. and when I choose 'Advanced' to provide a network path. I thought I was making progress when it got to the credentialing in the DOS(like) window, but It would not acknowledge the network path provided led to my Windows Image .
...
- Se connecter pour poster des commentaires