Mount FSx File System on Windows EC2 Instance

Thank you for providing the steps you've taken to mount an FSx file system on your Windows EC2 instance. It seems you're on the right track, but there are a few additional steps and considerations that might help resolve the issue you're experiencing.

1. Ensure that your EC2 Windows instance is joined to the same Microsoft Active Directory that you associated with your FSx file system. This step is crucial for proper authentication.

2. Verify that the security group associated with your EC2 instance and the FSx file system allows the necessary network traffic. For FSx for Windows File Server, you need to open the following ports:

   • TCP 445 (SMB)
   • TCP 5985 (PowerShell remoting)

3. Double-check the DNS name you're using in your net use command. Make sure it matches exactly with the DNS name provided by FSx for your file system. You can find this in the FSx console or through the AWS CLI.

4. Instead of using the command prompt, you might try using File Explorer to map the network drive:

   • Open File Explorer
   • Right-click on "Network" and choose "Map network drive"
   • Choose a drive letter and enter the UNC path (\DNS_NAME\share)

5. If you're using FSx for OpenZFS (which isn't typically used with Windows), you'll need to ensure that the Client for NFS is installed on your Windows instance and that additional ports are open (111, 2049, and 20001 for TCP, and 111 and 20001 for UDP).

6. Make sure your EC2 instance has internet connectivity to reach the AWS services, or ensure you have the necessary VPC endpoints configured.

If you've verified all these points and are still encountering issues, you may want to check the FSx file system's status in the AWS console to ensure it's available and not undergoing any maintenance.

Remember, when troubleshooting network connectivity issues, it's often helpful to start with the basics: check your network settings, security groups, and ensure all necessary services are running on your EC2 instance.
Sources
Mounting FSx for OpenZFS fails on Windows EC2 instance | AWS re:Post
Accessing data using file shares - Amazon FSx for Windows File Server
Mapping a file share on an Amazon EC2 Windows instance - Amazon FSx for Windows File Server
Mounting volumes on Microsoft Windows clients - FSx for ONTAP

1. First, verify domain join status:

systeminfo | findstr /B /C:"Domain"

Ensure your EC2 instance is properly joined to the domain.

2. Check DNS resolution:

nslookup amznfsxrvgindtl.test.windows.com

Verify it resolves to the correct FSx IP address.

3. Correct share path syntax: The correct format should be:

net use Z: \\amznfsxrvgindtl.test.windows.com\share

Note the double backslashes (\) at the beginning.

4. Security Group Configuration:

• Ensure the EC2 security group allows:
  • TCP/UDP 445 (SMB)
  • All traffic from FSx security group
  • All traffic from AD DS security group

5. Network Configuration:

• Verify VPC settings
• Check route tables
• Ensure FSx and EC2 are in same VPC or have proper routing

6. FSx Configuration:

• Verify the share name is correct
• Check FSx file system status in AWS console
• Confirm AD authentication settings

7. Additional Troubleshooting Commands:

Test network connectivity:

Test-NetConnection amznfsxrvgindtl.test.windows.com -Port 445

Verify AD connectivity:

nltest /dsgetdc:test.windows.com

Check share visibility:

net view \\amznfsxrvgindtl.test.windows.com

8. Common fixes:

• Restart the Windows Server service

net stop server
net start server

• Reset DNS cache

ipconfig /flushdns

• Verify Windows firewall settings
• Check Event Viewer for related errors

9. If still not working:

• Try mapping with IP address instead of DNS name
• Use full credentials:

net use Z: \\amznfsxrvgindtl.test.windows.com\share /user:test.windows.com\admin password

10. Final verification:

• Check if the EC2 instance can ping the FSx DNS name
• Verify network ACLs if using any
• Review FSx audit logs in CloudWatch