There are a number of potential causes for being unable to access your file system, each with their own resolution, as follows. Show
Topics
The file system elastic network interface was modified or deletedYou must not modify or delete the file system's elastic network interface. Modifying or deleting the network interface can cause a permanent loss of connection between your VPC and your file system. Create a new file system, and do not modify or delete the Amazon FSx elastic network interface. For more information, see File System Access Control with Amazon VPC . The Elastic IP address attached to the file system elastic network interface was deletedAmazon FSx doesn't support accessing file systems from the public internet. Amazon FSx automatically detaches any Elastic IP address, which is a public IP address reachable from the internet, that gets attached to a file system's elastic network interface. For more information, see Supported clients, access methods, and environments for Amazon FSx for Windows File Server. The file system security group lacks the required inbound or outbound rules.Review the inbound rules specified in Amazon VPC Security Groups, and make sure that the security group associated with your file system has the corresponding inbound rules. The compute instance's security group lacks the required outbound rulesReview the outbound rules specified in Amazon VPC Security Groups, and make sure that the security group associated with your compute instance has the corresponding outbound rules. Compute instance not joined to an Active DirectoryYour compute instances might not be correctly joined to one of two types of Active Directory:
Make sure that your compute instances are joined to one of two types of directory. One type is the AWS Managed Microsoft AD directory to which your file system is joined. The other type is a Microsoft AD directory that has a one-way forest trust relationship established with the AWS Managed Microsoft AD directory. For more information, see Using Amazon FSx with AWS Directory Service for Microsoft Active Directory. The Microsoft Windows file share that you're attempting to access doesn't exist. If you're using an existing file share, make sure that the file system DNS name and the share name are correctly specified. To manage your file shares, see File shares. Active Directory user lacks required permissionsThe Active Directory user that you're accessing the file share as lacks the necessary access permissions. Make sure that the access permissions for the file share and Windows access control lists (ACLs) for the shared folder allow access to the Active Directory users that need to access it. Allow Full control NTFS ACL permissions removedIf you remove Allow Full control NTFS ACL permissions for the SYSTEM user on a folder that you shared, that share can become inaccessible and any file system backups taken from that point onwards may not be usable. You will need to re-create the affected file share. For more information, see File shares. After you recreate the folder or share, you can map and use the Windows file shares from your compute instances. Can't access a file system using an on-premises clientYou're using your Amazon FSx file system from on-premises using AWS Direct Connect or VPN, and you're using a non-private IP address range for the on-premises client. Amazon FSx only supports access from on-premises clients with non-private IP addresses on file systems created after December 17, 2020. If you need to access your FSx for Windows File Server file system that was created before December 17, 2020 using a non-private IP address range, you can create a new file system by restoring a backup of the file system. For more information, see Working with backups. New file system is not registered in DNSFor file systems joined to a self-managed Active Directory, Amazon FSx did not register the file system DNS when it was created because the customer network does not use Microsoft DNS. Amazon FSx does not register file systems in DNS if your network uses a third-party DNS service instead of Microsoft DNS. You must manually set up DNS A entries for your Amazon FSx file systems. For Single-AZ 1 file systems, you will need to add one DNS A entry; for Single-AZ 2 and Multi-AZ file systems, you will need to add two DNS A entries. Use the following procedure to obtain the file system IP address or addresses to use when manually adding the DNS A entries.
Can't access the file system using a DNS aliasIf you're unable to access a file system using a DNS alias, use the following procedure to troubleshoot the issue.
Which command can you use in Linux to give the current logged on user temporary root permissions?The Unix command su, stands for “substitute user,” “super user,” or “switch user,” and allows you to log in as root and do whatever you want with the system. Sudo stands for either "substitute user do" or "super user do" and it allows you to temporarily elevate your current user account to have root privileges.
What file should you edit to configure an SMB share on Linux?To configure shares and users, edit the /etc/samba/smb. conf file. The default file has several good examples of common options, including provisions for shared printers and home directories. There's a global section, which defines a workgroup.
Which of the following is the native Linux UNIX file sharing protocol?NFS is that native Linux/UNIX file sharing protocol and is supported by Windows and Mac OS X.
Which network component allows computers to communicate on a network without being connected directly to each other?A Wireless Area Network (WAN) has the same function of connecting computers on a home or office network as a LAN, but it distributes the signal wirelessly. A wireless connection allows compatible desktop computers, laptops, smart phones and tablet devices to connect with one another.
|