Return
-
Title
Local Mount Utility fails to mount Recovery Points for Cores not joined to a domain -
Description
Local Mount Utility (LMU) fails to mount Recovery Points (RPs) for Cores not joined to a domain and the LocalMountUtility.log file has the following errors:
ERROR 2020-12-22T11:26:08 [19] - LocalMountUtility.ViewModels.DataViewModels.VolumeViewModel ()Cannot mount a volume X:\ at C:\RapidRecoveryRestoreSystem.AggregateException depth 0: One or more errors occurred. (0x80131500) ---> (Inner Exception #0 depth 0) System.InvalidOperationException depth 1: Core service cannot be reached. Please check the network connection and if the service is running. (0x80131509)ERROR 2020-12-22T11:26:08 [19] - LocalMountUtility.Implementation.Mounts.RemoteMountService ()Cannot get the replay engine endpoint configuration of the host 10.0.0.10System.Net.Sockets.SocketException depth 0: No such host is known (0x80004005)On the core the ReplayEngine IP was already set to 10.0.0.10 for instance and it is not saying "Automatically Determined".
-
Cause
When trying to mount Recovery Points (RPs) using the Local Mount Utility (LMU) from a machine in a domain and registered on a certain DNS server, which the Core is neither added to (domain) nor registered on (DNS), you will encounter problems connecting to the Core server and the remote mount will fail. You will need to add host file entries on both machines so that the computer where LMU is running from is able to resolve the Core's name and vice-versa. -
Resolution
In order to mount RPs remotely from Local Mount Utility (LMU), an entry with IP and Hostname of the Core Machine needs to be added to the host file of the machine running Local Mount Utility and the IP and Hostname of the Machine running LMU needs to be added to the Core's host file.
Please refer to the following webpage for instructions to modify the host file:
>> How to edit host file in Windows 10 - Microsoft Community