Most probably the issue is related to the Active Directory. You can engage your AD team for assistance.

WorkaroundOne of the work around for this issue is to use the IPAddress of the Machine where the n/w share is location.