boot disk
when booted with my bootable rescue media usb stick TIB2016 cannot find my WD EX2100 NAS - I get a choice of computers near me / nfs (whatever that is)
I cannot enter \\wdmycloudex2100 as it will not acceopt the \\
I tried to create a new win PE boot disk after latest download but it says I need to install windows ADK or AIK... but when I try it says it is not compatible with my system !! (Win 10 pro)
It works OK from within windows but I need to do it from a boot drive
help please
Thanks for that..... that did not work (see pic) - interesting to note the directions of the slash marks !
I tried browsing again and this time the NAS drive DID appear in the list !!!
I tried many times last light before posting
Hello David,
The program does not block \\, you should be able to enter it freely. It is possible that after trying to expand the list of computers "near me" user interface stops responding for a few seconds and you are unable to type anything into the address field.
I suggest you booting into bootable media again, wait 5 minutes to make sure that all network connections are initialized (especially if there is Wi-Fi connection), then try accessing the network drive again, try both name and ip-address of the network drive, e.g. \\10.250.0.12, replace 10.250.0.12 with ip-address of wdmycloudex2100.
Please find additional troubleshooting steps at https://kb.acronis.com/content/57992
Regards,
Slava
Thanks Slava.... but I think you missed the bit about "when I boot from my rescue disk" ..... the Bonjour service would not be running then would it ?
Network addressing is done using forward slash marks (//) and is the correct format for establishing network path. Just have a look at the address bar in your browser for this webpage and you will see this is the case. The error displayed in your screen image is telling you that the path \\wdmycloudex2100\ is an invalid path.
If changing the slash marks does not work for you then you have other network problems. You are using a network host name as the path in your example and if that fails when using the correct path format this would indicate an issue with resolving that name into an IPaddress on your device on your network. That in turn indicates you have an issue with DNS on your network.
Recommend that you either fix the DNS issues on your network or substitute the IPaddress in place of the hostname for your device.
Hello David,
"Automatic NAS detection" is done through Bonjour service in Windows and by Universal Plug and Play service under Linux-based media. That only makes your NAS appear at "My NAS connections" section in Browse dialog boxes.
When you enter ip-address directly, e.g. \\192.168.0.1, in the address bar and click on green arrow icon or hit Enter, the program does not use neither Bonjour nor UPnP. It attempts to connect to NAS through standard SMB protocol. When you use NAS name instead of ip-address, there is one additional step: before connecting the program asks DNS server what is the ip-address of the machine name you have entered (wdmycloudex2100 in your case) and then attempts to connect to that address. Name resolution into ip-address is done seamlessly for you. I suggested you trying ip-address because in some network environments name resolution is not configured properly and causes NAS devices to be inaccessible by name, while connecting by ip works fine.
Regards,
Slava