Oracle Cloud Infrastructure Documentation

Windows 2008 R2: UNC Access Delayed; "Network Error 53 Network path not found"


To connect to file systems from Windows instances, the NFS Client must first be installed. Be sure to follow the installation procedure found in Mounting File Systems From Windows Instances before proceeding with troubleshooting.

Symptom1 : After installing NFS client on Windows 2008 R2 servers, mount fails with "Network Error 53 "Network path not found".

Symptom 2: After installing NFS client, connection to a file system using a Universal Naming Convention (UNC) path, is significantly delayed on Windows 2008 R2 servers.

Cause 1: Windows Network Provider has higher priority than Client for NFS Network Provider.

Solution 1: Change the Network Provider Order so that Client for NFS Network Provider is tried first.

To change the Network Provider Order on Windows 2008 R2

Cause 2: The security list rules for the subnet where the mount target resides are not correctly set up.

Mounting a file system requires stateful ingress TCP ports 111, 2048, 2049, and 2050 as well as stateful ingress UDP ports 111 and 2048.

Stateful egress from TCP ports 111, 2048, 2049, and 2050 and stateful egress from UDP port 111 is also required.

Solution 2: Use the instructions in Configuring VCN Security Rules for File Storage to set up the correct security list rules.