OSA / SmartStart for SEDs - Communication Issue (failed to mount shared directory)
Issue: User receives error message "Error": failed to mount shared directory"
NOTE: This advisory applies to SES V5.3, and may or may not apply to future versions.
For the full illustrated version of the following, see a PDF version of this article here:
SmartStart for SEDs-Communication Issue.pdf
SmartStart for SEDs - Communication Issue Document (PDF) (77.43 KB) Not downloaded yet
Cause(s) and Resolutions: There are two possible causes for the error message "Error: failed to mount shared directory”.
Cause 1:
When using computer name, SmartStart for SEDs may not communicate properly so it will not register on the SES or get the configuration files from the shared folder. If you use IP address, the communication works as expected.
Reason 1:
The DNS for the Windows Server was not setup. This tool is important because it allows the computer to distribute the Name of the PC instead of the IP Address.
Resolution 1:
- Enable the DNS feature through the manage server role Administration setting located in Administrative Tools.
- Assign an IP address to the DNS through the TCP/IP setting
o Network connections
o Right click connection-properties
o Click on TCP-IP and setup and change the IP address on the DNS tab.
o The below are corresponding snapshot (See PDF for illustrated version of this article).
- Enable NetBIOS over TCP/IP which enables PCs to Ping Names with IP address.
o Network connections
o Right click connection-properties
o Click on TCP-IP and setup and the WIN tab
o At the bottom enable NetBIOS (Middle Option)
Cause 2:
IP address or Computer name in the configuration files may be incorrect.
Reason:
If the IP or computer name is incorrect then the install process will not be able to communicate to the server properly.
Resolution:
- Open the SDProfile.spf file in notepad and double check the configuration to make sure that it contains the proper IP address or computer name.
- Open the SES console and check the Profiles communication setting to make sure that it has the proper information
o Double click the profile
o Click on General Options
o Check the IP or Servers network name
- Recreate the install package and replace the old one with the newly created one.
(Notes: Windows to Windows machine name resolution may work fine in a normal environment, since Windows can use WINS/NetBios platform specific protocols.
Linux needs standard cross platform protocols, like DHCP and DNS to assign an IP address and to perform Name Resolution of Windows devices, respectively. |
Custom Fields - Error message or code: Error: failed to mount shared directory
- Version: SecureDoc 5.3 SR1, SecureDoc 5.3 SR2
|