AWS FSx on windows file server : Error : System error 53 has occurred. The network path was not found

Hello Troy...

I understand you're encountering a "System error 53: The network path was not found" error while trying to mount your FSx for Windows File Server on your EC2 instance.

Double-check:

• FSx DNS name (from FSx console)
• "File and Printer Sharing" enabled (on your EC2 instance)

Verify:

• NetBIOS Helper service running (on your Windows server)
• Security groups allow inbound traffic on ports 2049, 111, 20048.

AWS documentation on troubleshooting FSx access issues: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/unable-to-access.html

Troubleshooting network errors on Windows Server: https://learn.microsoft.com/en-us/troubleshoot/windows-server/networking/system-error-51-53-access-shared-resources

This error typically occurs when the Windows machine is unable to locate or connect to the specified network path or resource. Here are some actions you can try to troubleshoot and fix the issue:

• Check Network Connectivity: Ensure that your Windows EC2 instance has proper network connectivity to the FSx file system. Verify that the security groups associated with your EC2 instance and the FSx file system allow the necessary inbound and outbound traffic for the required ports (e.g., SMB, DNS, etc.).

• Verify DNS Resolution: Double-check that the DNS name you're using to connect to the FSx file system is correct and resolves properly. You can try pinging the DNS name from your Windows EC2 instance to ensure it's accessible.

• Check Active Directory Integration: Confirm that your FSx for Windows File Server is properly integrated with your Active Directory domain. Ensure that the FSx file system and your Windows EC2 instance are part of the same Active Directory domain.

• Check File System Permissions: Verify that your Active Directory user account has the necessary permissions to access the FSx file system. You may need to grant specific permissions or add your user account to the appropriate security group.

• Check File System Status: Ensure that the FSx file system is in the "Available" state and not in any error state. You can check the status of the file system in the Amazon FSx console.

• Restart SMB Services: Try restarting the Server and Workstation services on your Windows EC2 instance. Open the Services management console (services.msc), locate the "Server" and "Workstation" services, and restart them.

• Check Firewall Settings: Ensure that the Windows Firewall on your EC2 instance is not blocking the SMB traffic. You may need to create an inbound rule to allow SMB traffic (ports 445 and 139).

• Use UNC Path: Instead of using the DNS name, try connecting to the FSx file system using the Universal Naming Convention (UNC) path. The UNC path format is \<DNS-name><share-name>.

• Check Event Viewer: Check the Windows Event Viewer on your EC2 instance for any relevant error messages or warnings that could provide more insight into the issue.