File Share through Storage Gateway mounted successfully, files populated, accessible from Windows Network Drive, but files are unable to be accessed

Question

File type: .mp4
Within AWS Storage Gateway, we have a file share setup linked to an S3 bucket utilizing a known working gateway. After mounting the file share to a network drive within Windows utilizing the example command listed on the file share page (net use [WindowsDriveLetter]: IPADDRESS\BUCKETNAME/USER\smbguest), the file share appears to be working properly as the file share is accessible from Windows File Explorer and files are being updated in real time compared to the S3 bucket. However, when attempting to download a copy of a file from the file share, I receive an error stating "This is no longer located in (Windows File Path). Verify the item's location and try again."

Additionally, the time stamp of all of the files within the file share when accessed through Windows, is being updated to whatever the current time of accessing the file share from Windows File Explorer is.

When attempting to just open a file from the file share, I receive this error: "We couldn't open (File Name) as we can't get to your network storage right now. Check your network connection, then try again. 
0x80070002"

Does anyone know what is going on here? It seems that all of the permissions on the AWS side of things are set properly as the bucket and files can be listed, but when attempting to access through Windows File Explorer, everything fails.

Additional S3 Bucket Information:
Bucket Versioning is enabled,
Encrypted with default encryption: Server-side encryption with Amazon S3 managed keys (SSE-S3),
Public Access is Blocked

Additional File Share Information:
Guess MIME Type: Yes,
Export as: Read-write,
Access Control: POSIX permissions,
Force case sensitivity: Deactivated,
Opportunistic Lock (oplock): Activated,
Authentication Method: Guest Access,

File Share IAM Role:
{
    "Version": "2012-10-17",
    "Statement": [
        {
            "Action": [
                "s3:GetAccelerateConfiguration",
                "s3:GetBucketLocation",
                "s3:GetBucketVersioning",
                "s3:ListBucket",
                "s3:ListBucketVersions",
                "s3:ListBucketMultipartUploads"
            ],
            "Resource": "arn:BUCKETNAME",
            "Effect": "Allow"
        },
        {
            "Action": [
                "s3:AbortMultipartUpload",
                "s3:DeleteObject",
                "s3:DeleteObjectVersion",
                "s3:GetObject",
                "s3:GetObjectAcl",
                "s3:GetObjectVersion",
                "s3:ListMultipartUploadParts",
                "s3:PutObject",
                "s3:PutObjectAcl"
            ],
            "Resource": "arn:BUCKETNAME/*",
            "Effect": "Allow"
        }
    ]
}

Thank you!

Accepted Answer

Cause of Issue:
Amazon Connect outputting files to the S3 bucket utilizing a naming convention including a ":" (Colon) which is a reserved character within Windows.

Answer

IAM role permissions for S3 looks good. Generally, when using ```smbguest``` as file share authentication method, by default the file permissions are ```smbguest``` user and group and reading the files should have no issues.

May I know the below:
1. Can you confirm, the windows client has not connectivity issues to the Storage Gateway on port 445 ?
You can test the connectivity using ```telnet``` or ```TestNetConnection```.
2. Is the file share created with existing files on the S3 bucket. If so how are the files copied to the S3 bucket? What are the file permissions when you see on the windows explorer ?
3. Does your work flow or use case requires direct access to the S3 bucket for data copy/upload ?
4. Based on what you mentioned about time stamps being updated to current date when viewed/accessed from the windows explorer. Do you have [automated cache refresh](https://docs.aws.amazon.com/filegateway/latest/files3/refresh-cache.html#auto-refresh-console-procedure) enabled on the file share ? Generally, this behavior is seen when objects are uploaded directly to S3 and gateway tries to refresh the contents from S3 for the first time.

Based on the description and the error messages you were receiving when reading the file, I would recommend to please  to open a case with support to have it investigated further.

File Share through Storage Gateway mounted successfully, files populated, accessible from Windows Network Drive, but files are unable to be accessed

Relevant content