System error 1231 when in MVP WinPE environment attempting to connect to a network share

Ken, how are you connecting to your NAS when in Windows, and when using the rescue media?

It is best to use a wired network connection for the rescue media, and you can check that you have network access by launching the web browser in the MVP media.

In windows I am mapping the drive (right click on This PC)

In rescue media I have loaded the credentials into Map.cmd script.  The error message occurs during the boot up sequence for the MVP tool.  

Interesting that you mention that it is best to use a wired connection.  I have been using the WiFi connection on one of the computers and the ethernet connection on the other.  Long story.  

Do you recommend using the ethernet connection on both.  Would the WiFi connection on one effect the connection to the NAS share on the other.  I get the 1231 error on both computers.

More information:  I switched to the ethernet on the one computer and tried the boot in to rescue media.  Now I get Error 1312 instead.  Is it important that the ethernet be enabled when creating the media?

Ken,

Have you upgraded your ADK to the latest 2004 version along with the latest WinPE module?  If not you should do so and then rebuild your media.  That should do the trick for you I believe.

Ken, the main reason for using a wired connection is the lack of wireless support in most types of rescue media, including the MVP media unless you have jumped through all the hoops needed to get wireless working!

It isn't necessary to have the ethernet enabled or connected when creating the media but it should be connected when booting from the rescue media ideally.

I haven't used the map.cmd script either as it is as easy to just use normal commands once you confirm that you have a working network connection.

In the MVP media, open a command prompt and first type in ipconfig /all to confirm that your NIC has been given a valid IP address, i.e. 192.168.0.33, then type in ping 192.168.0.29 (using your own NAS IP address) to check you can reach the NAS across the connected network.

Once you have a network connection, then you can use the Browse button in the main ATI panels to open the connection to your NAS and provide the necessary credentials.

I do have the latest ADK and WINPE add on.

I do have network access while booted with the rescue media. 

I will try Steve's latest suggestion.

I have the internet.  Ping to 192.168.0.29 timed out.  Could not browse to NAS share.  No entries in NAS connections or Network locations.

Ken, what is the IP address of your NAS here?  192.168.0.29 was the IP for my own NAS and will be different for you / other users.

OK, I am a bit of novice when it comes to networking.  My network share IP is obviously different than yours.  I will try to ping that!

OK my NAS returned the PING with no loss.  

... and it still does not show in My NAS Connections or on the Network/Entire Network.  

Is it possible that this issue is related to Work Groups?  My computers are both members of a Workgroup.  This was not an issue before, but could it be now?

It sounds to me like the network is not initialized when the attempt to connect is being made here.

Since you are using the MVP media here you should try using the built in network tool to make connection to the mapped drive.  In the task bar look for the 4 monitor icon to launch the tool.

I have tried this tool without luck.  This is what I did.  

Click on tool icon, tool opens.

Click on "Network Drives" and enter credentials of Network share in upper box.

Click on Connect; a window opens that has the following message:  A specified logon session does not exist.  It may already have terminated.  

Also, now that both computers are on Ethernet connections they both are generating System Error 1312 (instead of 1231) when attempting login to NAS drive in MVP WinPE environment. 

Ken,

You are using a CMD script added to the MVP tool to establish the mapped drive in the media correct?

The 1312 error means that the specified logon session does not exist meaning that your script has errors.

Below is an example script that may help you.  Adjust accordingly for your path.

If your password has any spaces or percent signs or other special characters, you cant put it in the command line - it confuses the command line parser.

Make a command script like this:

rem Make sure P Drive does not exist

net use P: /D

rem Delete any secure channel connections

net use \\ServerName\IPC$ /D

rem Map the drive

net use P: \\ServerName\ShareName /user:Username Password

Ken, did you try just using the Browse option in the ATI GUI (as shown in my screen images in post #5 above)?

I did not create a script.  I am using the one downloaded with the MVP WinPE and located in the Mapped Drive folder.  It looks like this with my edits:

@echo off
FOR /F "skip=2 tokens=2*" %%i IN ('REG QUERY "HKLM\SOFTWARE\MVPTool" /v WinRE') DO (SET WinRE_Used=%%j)
IF %WinRE_USED%==YES SET DELAY=60
IF %WinRE_USED%==NO SET DELAY=10
echo.
echo Waiting %DELAY% seconds to ensure network services have started. 
echo After that, your network share will be mapped as drive Z:
echo.
ping -n 10 127.0.0.1 > nul
IF %WinRE_Used%==YES ping -n 50 127.0.0.1 > nul
echo.
echo Mapping network drive as Z: with the information
echo you previously provided in the 
echo MVP_ATIPEBuilder\MappedDrive\map.cmd file.
echo.
REM --> Down below, enter the CORRECT information for your network share.
REM --> Items needed - NAS IP Address, NAS share name, NAS username and NAS password
REM --> Example:    net use Z: \\192.168.1.100 (<--NAS IP) \AcronisBackups (<--NAS share name) /user:USERNAME (<--NAS username) PASSWORD (<--NAS password)
@echo on

net use Y: \\192.168.1.3\NAS_Folder /user:kenneth *********

@echo off
echo.
echo Please see "Start Menu\Administrative Tools\Map Network Drive" to map
echo additional network shares.
echo.
pause
echo.
exit

The asterisks are in the place of my password so that I don't share it here.  The password contains only letters, capital letters and numbers.  

I hope that you can find where I am making a mistake here!  This script has worked well for me in the past.  

I have the internet.  Ping to my NAS IP was successful.  Could not browse to NAS share.  No entries in NAS connections or Network locations.

Ken, as per my screen image, you need to type in the UNC address of your NAS for it to be found - my own NAS did not show under NAS connections or Network locations, but was found when I typed \\192.168.0.29\Backup in the browse address panel text entry box.

Ken,

Is the media you created a WinRE or a WinPE?  The script you have shows a delay for WinRE but nothing for WinPE.  I do not use this myself so am guessing here to some degree.  I an thinking that the reason you do not have an established session connection is possibly that not enough delay is in place to establish networking functionality before the net use map command is being run.

You can run the net use command from the command prompt in the MVP media to test it.  After everything loads run the net use command in the command prompt window.  If that works then I would say it is a delay issue.

Enchantech,

Yes, that works.  Sorry I didn't pick up on that approach to browsing from your earlier post.   

I remain curious about why the old approach using the your script in the MVP download does not now work. 

Thank you very much, once again, for solving my problem.  And I appreciate your patience.  

Ken S

Ken,

Your welcome, I do think it is the delay not being long enough to allow the networking components to bet established during the boot process prior to the script running the net use command.  adding more to the time should fix it.

@Ken S

A wild guess !!

Your folder on the NAS contains an _ (underscore) - could that be a problem ???

<<  net use Y: \\192.168.1.3\NAS_Folder /user:kenneth *********  >>

I myself, had a problem with a 'blank' in the foldername (Ghost Win10), and had

to change it to:

net use w: "\\192.168.123.210\Ghost Win10" MyPw /user:MyUser

Enchantech said in post #15:

If your password has any spaces or percent signs or other special characters, you can't put it in the command line - it confuses the command line parser.

Underscores, al least in my experience, are not an issue in path statements unless they are left out.

To reinforce Enchantech's comment, I have been using "NAS_Folder" for a long time (years) and have only experienced an issue since ATI 2021.

Ken,

I'm having trouble understanding why your problem only occurs with ATI 2021. It should be no different than ATI 2020 under WinPE.

It's more likely your problem stems from the version of WinPE/RE used to create the media. I'm assuming you're on ethernet and the adapter has an IP address.

Try this:

1. Boot the ATI 2021 MVP media and close the TI GUI.

2. Open a command window and enter:

      net use

   You should see "There are no entries in the list."

3. Enter:

   net use \\NAS_Name

   Note there is no share folder or user information.

4. Enter user name and password at the prompts. You will either see an error message or "The command completed successfully."

If you get an error and can't connect, you will know ATI 2021 has nothing to do with the problem. You need to look elsewhere.

See screenshots of the above command connecting to Windows network. Also see screenshots of ATI 2021 browsing to a network share.

The procedure was:

1. Open the Browse to file to recover window.

2. Click the drop down arrow to the left of Network and wait for the hour glass to disappear.

3. Click on the words Entire Network under Network and wait for a folder named System to appear in the right pane.

4. Click on the System folder icon in the right pane. \\ will appear in the File name box. Enter the NAS name after \\ followed by \. Two authentication boxes will appear. Close the one on top (it will not work). It will take two tries to close it. Enter the user name and password in the other box. You should see Connection completed successfully.

5. Share name should appear below the File name box. Click on the share with the backup files. 

Mustang,

Following "Try this:"  I reached step 3. and after entering net use \\192.168.1.3, I received a System error 58.  I also tried again with net use \\WDMYCloud just in case I was misundstanding what you meant by \\NAS_name.  I still received System error 58.  So I assume from this that ATI 2021 is not the problem based on your post above.  

Following "The Procedure was:"  I followed the instructions successfully and was able to browse my backups on the Network share.  I also indicated above that this procedure was successful for me

My statement about my problem arising only since ATI 2021 has to do with trying to use the the Map.cmd script in the Mapped Drive folder contained in the MVP WinPE download.  I have used that approach successfully over the years without problem until ATI 2021.  Enchantech suggests above that the problem may be with the delay parameter in the Map.cmd script and not ATI 2021.  Perhaps that is the case.

At this point I will go forward using the browse in ATI app approach and cease to rely on the Map.cmd script in the Mapped Drive folder.  

Thank you very much for your help.  

Ken S.  

You can tell if the delay time is an issue very simply. Just open a command prompt after WinPE have been running for some time (wait 5 to 10 minutes if you like). Then try to use the net use command to connect to the NAS share or map a drive letter to the share. The MAP command in the MVP Tool does nothing special except force a delay. It just uses the standard windows net use command.

The net use command depends heavily on entries in the WinPE registry. The fact that it worked for you in the ATI 2020 media and doesn't work in the ATI 2021 media strongly suggest the two media are not based on the same WinPE/RE version. I would suggest you try making the ATI 2021 media so that it is using the same version of WinPE/RE that was used to create the ATI 2020 media. If that works, maybe we can delve into the different WinPE versions you used and see why net use is working in one and not in the other. 

Mustang,  As you will note above, Enchantech suggested that I update to ADK 2004 and its WinPE add-on.  I was at that time experiencing this problem with the ADK WinPE combination that had worked in earlier versions ATI (2020 and earlier).  So, I conclude that it was going to ATI 2021 and not the change of ADK that caused the problem since I updated ADK only after ATI 2021 was issued.  

I will try to wait after booting into WinPE as you suggest to see if net use command will work.   Ken S. 

I can see your logic, but I can't figure out how the change to ATI 2021 could cause the problem if you use the MVP Tool with the same ADK. If you were using the Acronis Media Builder, there could be the possibility that Acronis made changes to WinPE files or WinPE registry entries. The only thing possible to change with the MVP Tool would be the two services installed (fltsrv and snapman). It's hard to see how different versions of fltsrv.sys and snapman.sys could cause a problem with the net use command. I can tell you the MVP Tool makes the changes to install the services in the WinPE registry. That means all Acronis related changes to the WinPE registry are exactly the same for ATI 2020 and 2021 when the MVP Tool is used.

Why don't you try something interesting? Try building the MVP Tool media without ATI included. Then see if the net use command works for you.

Here's how to exclude ATI from the MVP Tool media. In Explorer navigate to C:\Program Files (x86)\Acronis\TrueImageHome\WinPE. Rename winpe_resources.dll to Xwinpe_resources.dll. Now when you build with the MVP Tool ATI will not be found. Remember to correct the name of winpe_resources.dll after you do the test build.

OK, I tried a build of the WinPE tool without ATI with the same result.  Sys Error 1312 from the CMD script.  And Sys error 58 using net use \\192.068.1.3 from the command prompt.  

That being the case I'm ready to throw in the towel.  I guess the script is only failing for me.  And I can access my NAS share using the browsing method that you and Enchantech have taught me.  I find that to be entirely acceptable, maybe even to be preferred. However, in the future I will continue to edit the script with my share name and credentials and perhaps one day with changing Windows 10 updates and changing ATI versions it will work for me again. 

I thank both of you very much for getting me back to where I can use ATI with my NAS.  Your help has been essential to my success with ATI for backup from the beginning.  

Ken S. 

Thank you for reporting. Your problem is really difficult to pin down. Let us know if anything does change in the future.

Ken,

Thanks for getting me thinking about this issue. I did some testing of the MVP Tool Map command using WinPE created with the 2004 ADK. The command failed with a system 1312 error. I waited some time and entered the net use command from a command window. It failed with the same error message. Then I entered the net use command without the user name and password. The system prompted for user name and I entered it. The system prompted for password and I entered it. The connection completed SUCCESSFULLY!

There is something going wrong with the net use command in the MVP Tool using recent versions of the ADK. I'm going to dig into it to find the cause. It may take a few days. In the meantime would you please try a test. Boot up the MVP media and open a command prompt. Enter the net use command you used in the Map command WITHOUT the user information. Enter the user name and password at the prompts. Let me know if that works.

Mustang,

I tried a few different net use commands at the command prompt with following results:

net use Y: \\192.168.1.3\NAS_Folder     result:  Sys error 58

net use Y: \\192.168.1.3\NAS_Folder\     result:  Sys error 67

net use Y: \\192.168.1.3                          result:  Sys error 67

net use Y: \\192.168.1.3\NAS_Folder /   result:  /option unknown;  but then i got a list of allowed syntax  for "net use" none of which look familiar to me, but all of which seem to require the password before the user name.  

This last example may be useful for you to see, maybe not.  

I hope that the first example above is what you wanted me to try. If not, let me know.  

Ken 

Ken,

Working on the issue.

Here's something you can try:

net use Y: \\192.168.1.3\NAS_Folder /user:\username <password>

Enchantech, 

I tried your suggestion.  There was no sys error but much like the last example in post #34 above a the message that "the correct syntax for this command is:"   And what follows is a statement of the required syntax for using "net use" which I cannot decipher.  But I don't think it is what I have been doing.

Ken.  

Ken,

Enchantech and I have been working on this. He suggested that adding a Domain Name in front of the username might work. He was right, it worked. I also found that it didn't need to be a correct Domain Name. In fact any word would work. I also found that just adding the \ in front of the username worked.

His example above needs to have a space between Y: and \\192.168.1.3\NAS_Folder. Try it again. 

I finally deciphered the syntax.  This is what worked for me:

net use Y: \\192.168.1.3\NAS_Folder /user:domain\username password

The differences from this and your example are the forward slash after Folder and the insertion of the word domain after the colon.

Success here!

Ken

Glad it's working. I didn't notice the \ instead of the required / in front of user in the above command.

I found it also worked without specifying domain in the command as long as the \ was placed in front of username like this:

net use Y: \\192.168.1.3\NAS_Folder /user:\username password

The problem is that Microsoft made changes in recent ADK's to cause the original Map command to fail.

Ken,

Apologies for getting the syntax of the command wrong.  It has been a hectic day for me and being in a hurry was not a good idea today in doing this.

I have adjusted the syntax in my post #35 to be accurate.  As you have found you can add a DomainName prior to the UserName in the syntax but that name is only needed if the server you are connecting to is on a Domain like an AD. 

The real change here is that a forward slash (/) must be inserted before the user option in the syntax.  This is a security enhancement for the SMB 3.0 protocol.  By adding the forward slash you are specifying connection logon as the Username <password>.  If the forward slash is not included then the logon reverts to the current user which in this case is the WinPE admin.  The WinPE admin has not authentication to the share so therefore the error Sys 58 is generated.  The Sys 67 error is due to syntax mistakes.

I will make the change in the script and remake the recovery media and I assume that all will work. 

Thanks again for sticking with me on this.

Ken

Enchantech,

No apologies are necessary.  I wish I could count the number of times I have typed that syntax incorrectly over the past few days.  I am very happy that you guys now have a real understanding of the cause of my original problem.  

Many Thanks,

Ken