How to access my NAS from a WinPE boot disk?

Edwin,

1. When TI opens click on the Recovery tab in the blue section.
2. Look to the right and click on Browse for backups
3. In the new window click on the arrow to the left of Network.  You should see an hour glass appear while the app searches.  Be patient
4. When Entire Network appears click on the arrow to the left of it. An hour glass will appear again, be patient
5. In the right pane you will see System Folder with an up folder icon. Click on that icon and look in the path bar at the bottom of the window.  You should see \\. 
6. Click inside the path box and begin typing the path to your NAS.  Example \\devicename\folder\
7. At some point while typing the path a credentials box will appear,  Enter the username/password for your NAS and click OK
8. once authenticated folders holding backup files should appear in the window.
9. Navigate to your desired backup and click to select it.
10. Verify that the path includes your desired backup file in the path statement.
11. Click OK and continue with the Recovery Wizard procedures.

OK thank you very much!

Enchantech,

Your input helped me up to point 6 - but to no avail.

I typed my NAS's address:

\\192.168.123.209\Ghost Win10\   and also

\\192.168.123.209\Ghost Win10\My disks.tibx

But the OK button never got active.

Closing the the ATI 2020, I could from the CMD window

do a Ping to the NAS, which was OK.

Any suggestion or why I couldn't get forward, testing a DR situation.

Could it be, I'm on a trial ??

Best regards - Leif

Leif,

Using the trial version should not be at issue here.  I would say there is something not quite right in your path statement.   Is your NAS user account password protected?  If yes the credentials prompt should appear when you reach the point in the path where authentication is required.  If there are folders in the path those need to be included.

The fact that ping succeeded tells me that you have a connection to the NAS so getting the path right is the key.  How does you NAS appear in Windows Explorer?  Does it show by name or IP Address?  I'm betting it show by name, if yes replace the IP Address in your path with the deivce name.  Make sure any special characters or numbers that appear in Explorer are included.

Hi Enchanteck and thanks for your reply ...

Here it goes with answers to your Q's:

>>Using the trial version should not be at issue here.

My opinion too.

>>I would say there is something not quite right in your path statement. 

Yes, but what ??

>>Is your NAS user account password protected?  
>>If yes the credentials prompt should appear when you reach the point
>>in the path where authentication is required.

Yes, my QNAP is user protected, but no login splash screen shows up.

>>If there are folders in the path those need to be included.

No folders in the path ( \\QNAP-I\Ghost Win10\ ) or ( \\192.168.123.209\Ghost Win10\ )

The folder "Ghost Win10" only contains: "My disks.tibx" which seems ok.

>>The fact that ping succeeded tells me that you have a connection to
>>the NAS so getting the path right is the key.

Tried the ping with QNAP-I and the result was ok, showing 192.168.123.209.

>>How does you NAS appear in Windows Explorer?

With the name QNAP-I

>>Does it show by name or IP Address?

With the name as above. 

>>I'm betting it show by name, if yes replace the IP Address in your
>>path with the deivce name.

Tried it, but again to no avail. Same situation as using the IP address.

>>Make user any special characters or numbers that appear in Explorer are included.

Can only see the "-" and "spaces" as spec chr's.

Hmmm... could it be a CodePage problem, as I boot up with an unknown CP ??

The "-" could be translated to something "nuts" ??

Best regards - Leif

So your NAS shows up as QNAP-I in Explorer.  Then your path statement given what you have told me should be \\QNAP-I\Ghost Win 10\backupname

After you type the last backslash in the path, the one that appears just before backupname, A Credentials Prompt box should appear allowing you to input your authentication credentials.  I have had to wait a few moments for the prompt to appear on my systems.  I tried it just now and the prompt displayed immediately.  I know that is not always the case though.  In addition, the folder name (Ghost Win 10) should appear in the right hand window pane after you type this much as well.

You're saying that none of the above happens?

If you can see the Ghost Win 10 folder in the right hand window pane double clicking it should open a credentials prompt in a command prompt window.  Use the Tab key to reach Cancel and hit Enter.  Be patient and see if the TI Prompt appears

OK, I'm remembering a similar issue I had a year ago. I'm trying to find my old emails with one of the MVPs on this issue but can't yet find them to be more specific.

But the solution to get access to the NAS was to use the net command. For example

net use z: "\\QNAP-I\Ghost Win 10" /user:<username> <password>

Assuming you are using the Acronis built media (not the MVP version), you need to exit out of the ATI program to get back to the command prompt, enter the net use command, and then restart ATI. Then you could get to the NAS from the drive letter you assign (Z: in the above example).

If I can find my old emails, I will try to elaborate more.

@BrunoC

You're correct. The path needs to be included with ".. .." if spaces exist in the path. Thanks.

@Enchantech,

A Credentials Prompt box should appear. Yes.... but it does not appear :-(

Have given up the "simple" boot process from Acronis. Right now I'm testing the MVP ATI Pe Builder v. 186

which I think you're into with "Mustang". After my testings, I'll inform you :-)

Leif

Leif,

Something to check is if your NAS has a firewall, it might be blocking access.  Another thing to consider is if you are using wifi to connect to your NAS, this might be at issue as well.  Seeing how you can ping the NAS yet get no login prompt this is leaning toward a permissions issue at this point.

@Enchantech,

No Wifi, No NAS firewall (all in my LAN 192.168.123.0/24 are allowed). Connections (in this case) is my Desktop PC via Switch to the QNAP, all ETH.

After my change, trying MVP ATI PE Builder v. 18.6, I can now get to the Log In (Credentials Prompt box)

Unfortunatly, I just get a msg.box, saying: Connection failed - Verify username and password !

Found a DOS-box, with some interesting info:

>>Mapping network drive as W: with the information you previously provided in the
>>MVP_ATIPEBuilder\MappedDrive\map.cmd file.

>>X:\windows\system32>net use W: "\\192.168.123.209\Ghost Win10" /user:myUser myPassword
>>System error 384 has occurred.

>>You can't connect to the file share because it's not secure.
>>This share requires the obsolete SMB1 protocol, which is unsafe and could expose your system to attack.
>>Your system requires SMB2 or higher. For more info on resolving this issue, see: https://go.microsoft.com/fwlink >>/?linkid=852747

That could be the culprit !

Found that I only had the SMB1 Client running. Have changed it, and now SMB1 Server is running too.

Will test that tomorrow. Thanks

I believe you have found your permissions issue. Staying tuned in. :)

@Enchantech,

Some new informations.... and the culprit is the SMB v.1

Have other QNAP's with SMB v.2>, but my old (2007) QNAP (TS-209 Pro) only have SMB v.1 which I use to backups (and disaster/recovery). And this device are not supported any more :-(

Loaded via USB (MVP ATI PE Builder) into a newer NAS, and 'lo and behold' .... no problems.

Strange thing... both SMB server and -Client are running in my enviroment at v.1 (and v.2), but v.1 seem to have no effect.

Thanks :-)

Btw: have some suggestions/problems with the making a boot device from MVP, but it will come in another topic.

Leif,

Glad you got that issue sorted.  The issue with SMB v1 is I believe that the version of WinPE/RE, whichever you created, no longer supports the SMB v1 protocol.  This is due to Microsoft removing support for it.  The minimum now is SMB v2 and in environments where multiple devices support SMB v3 and higher, all devices supporting the highest version use that version for data transfer. 

The latest SMB version is 3.1.1 so if you have two Win 10 machines both supporting version 3.1.1 they will use that Protocol when transferring files via SMB.  Because the highest level of SMB is selected for use by default dependent on device support is the answer to your statement:

Strange thing... both SMB server and -Client are running in my enviroment at v.1 (and v.2), but v.1 seem to have no effect.

Have you checked with Qnap for a firmware update for your older NAS to bring it up to SMB v2 standard?  If they offer one I advise that you install it as it will extend the life of the device and offers much better security.

I will watch for your post on the MVP Media Builder tool.

@Enchantech,

Thanks for your comments ....

>>Have you checked with Qnap for a firmware update for your older NAS to bring it up to SMB v2 standard? 

>>If they offer one I advise that you install it as it will extend the life of the device and offers much better security

1) I'll try over at the QNAP forum, but dont think the dev's cares about an "old" QNAP from 2007 ;-)

2) The problem with SMB v1 and the "MITM" thread, is crap... in my closed LAN (just my opinion ;-)

Oh well... see what comes up tomorrow :-) Thanks

2) The problem with SMB v1 and the "MITM" thread, is crap... in my closed LAN (just my opinion ;-)

The problem is a bit more than MITM.  Have a look at the link below :-)

Here

SMB itself has vulnerabilities that persist even after MS applying much mitigation.  The latest as of 3/12/2020 can be found in the link below:

Here

Best to be as secure as possible.  I agree that on a closed LAN with good practices and a decent firewall your vulnerability is small.

@Enchantech

Thanks for the links - will dig into them, probably learning a little more :-)

Back to the "Epic Center" SMBv1: Activating SMBv1 within the creation (MVP) of a boot USB-stick.

I can successfully initiate SMBv1 with the following command (PowerShell):

PS C:\WINDOWS\system32> Enable-WindowsOptionalFeature -Online -FeatureName SMB1Protocol

Path          :
Online        : True
RestartNeeded : False

Q1: Can I include this command in the build USB-stick

Q2: If not.... can I include this command in the build on my Win10 folder for MVP ??

Q3: If not... can I get a test version, with this command included from the MVP-team ??

The above command is only for Win10, but have the others for Vista, 7, 8.1 too.

/Leif

Leif,

By default PowerShell is not available in WinPE/RE.  So the command you have will not work.

My advice is that if you want to use SMB v1 then you can build MVP WinPE media using an older version of PE prior to Win 10 1709 when support was dropped.  That Win 10 version is 1607.

You will need to download and install version 1607 on your machine so the the MVP Media Builder tool can use it to create WinPE.  If you have another version of WinPE installed you will need to uninstall it first.

You can download the Win 10 ADK install file for Win 10 1607 Here

Make sure you choose the right build (x-86 or x-64) depending on your machine.

When you install the ADK you only need to check the first three boxes when selecting components to install.

Once installed, run the MVP Builder tool and choose to build WinPE.  The resulting media will have support for SMB1

@Enchantech

Thanks for all your info's and suggestions. Much appreciated. Have been thinking for a couple of days about... what brings the future (SW updates from Win10 and Acronis ect. and an "old" WinPE version). Have made my decision and go for the SMB v2 >

I reorganize my data within two of my QNAP's

1) QNAP-1 (with SMB v1) contains data, not using SMB.

2) QNAP-2 (with SMB v2>) contains my backup's from Acronis 2020.

Thanks again - Leif

Lief.

Very good decision.  That should work for you and address the security concerns.  Glad I was of assistance.

@Enchantech,

Again... you were very helpfully, and thanks for that :-)

And now back to my problems with my keyboard setting in another blog =:-)

Thanks /Leif