I am trying to load my clean install of windows into a Virtual Box configuration. I have created rescue media from within Macrium Reflect. I am able to boot from rescue media inside of virtual box. 

I go to add the network path, and I get the message PE EXplorer  The network path was not found.

I have a local windows account, that is a basic account. I have added this account to the shared folder where my images are stored.
Everything in network sharing and discovery is set up correctly. So I have no idea what I am doing wrong.
A few months ago, I had Macrium support help me, but they deleted the secondary account in windows that they created.

I have no idea what they did to get it working.
Lets say my computer name is george. When trying to map the network drive in macrium PE, I type in: \\george\images
Then I enter in the username and password.
The account has full read\write access to the shared folder.

RescueMedia has no idea of shares established in normal Windows, unless in normal Windows running Relfect you enter the share information (and a user name/password that can access that share) in the Settings and Defaults -> Network Share Settings.

Another way to access it when booted into RM is to use the terminal window of RM to run the following command: (use any available letter instead of z: and use the path to the shared folder)
net use z: \\george\images
You will be prompted for a user name and password to get access to the share.   Then edit the list of folders in the list of backups to add z:\ to the list, refresh the view and you should then be able to access your images to do a restore (if that's what you want to do).  This is what I have to do when Reflect doesn't pass the default network share information to the booted RM. 


L.W. (Dan) Danz, Overland Park KS

By the way, if you opened the support ticket with a login on https://support.macrium.com (or https://help.macrium.com), you should be able to use that account to view closed tickets, and maybe that will give you a clue to what support folks did.  Remember: the login there is different than the login for this forum.


L.W. (Dan) Danz, Overland Park KS

+x

 

Dan Danz - 18 November 2023 6:06 PM

RescueMedia has no idea of shares established in normal Windows, unless in normal Windows running Relfect you enter the share information (and a user name/password that can access that share) in the Settings and Defaults -> Network Share Settings.

Another way to access it when booted into RM is to use the terminal window of RM to run the following command: (use any available letter instead of z: and use the path to the shared folder)
net use z: \\george\images
You will be prompted for a user name and password to get access to the share.   Then edit the list of folders in the list of backups to add z:\ to the list, refresh the view and you should then be able to access your images to do a restore (if that's what you want to do).  This is what I have to do when Reflect doesn't pass the default network share information to the booted RM. 

I tried what you suggested, using the command line.
I get the following two messages:
System error 53 has occurred.

The network path was not found.

+x

 

robertsaron - 18 November 2023 6:13 PM

+x

 

Dan Danz - 18 November 2023 6:06 PM

RescueMedia has no idea of shares established in normal Windows, unless in normal Windows running Relfect you enter the share information (and a user name/password that can access that share) in the Settings and Defaults -> Network Share Settings.

Another way to access it when booted into RM is to use the terminal window of RM to run the following command: (use any available letter instead of z: and use the path to the shared folder)
net use z: \\george\images
You will be prompted for a user name and password to get access to the share.   Then edit the list of folders in the list of backups to add z:\ to the list, refresh the view and you should then be able to access your images to do a restore (if that's what you want to do).  This is what I have to do when Reflect doesn't pass the default network share information to the booted RM. 

I tried what you suggested, using the command line.
I get the following two messages:
System error 53 has occurred.

The network path was not found.

Do you have network connectivity inside RM?  It seems to me there is a high-level menu in RM that displays it but I'm not in a position to boot RM to show it exactly.
You're also going to have to configure the network in Virtual Box (which is beyond my capabilities).


L.W. (Dan) Danz, Overland Park KS

Try using George’s IP address instead of the host name. The correct IP to use for talking to George from inside a VM would depend on how you’ve configured your virtual networking. But as Dan said, also verify that you have network connectivity at all by trying to ping an IP that should be reachable based on your configuration. If that doesn’t work either, run ipconfig to see if your VM has an IP address assigned at all.

Doing it by IP address instead of the folder path worked, which is odd. but Thanks so much for the help. I will have to remember this solution.