- 최신
- 최다 투표
- 가장 많은 댓글
I see you mentioned Windows 10 and the NFS ports. For NFS on Windows it would require the Services for NFS feature be installed on the client.
Though if you are using Windows as the client I would recommend SMB over NFS.
If you are still having issues if you can PM me your instance ID along with Gateway ID information I can take a look on my side to help troubleshoot.
Thank You,
Brian C. (AWS)
Hi Brian,
Sorry for my late reply. I am still having issues setting up the storage gateway for a windows 10 NFS client. I am trying to implement the storage gateway as a network drive to access my files stored in S3.
The example I am referencing can be seen in the youtube video here in this link: https://www.youtube.com/watch?v=tP5edaxBEEI
I want to implement the file and storage gateway exactly as is shown in the youtube video.
Can you please help me?
Sincerely,
Adithya
Adithya,
While the video you linked is great, it was made before we offered SMB as an option for File Gateway. For Windows we'd recommend SMB over NFS.
From the setup it sounds like you are wanting to use the gateway in EC2 but the client be onprem. For best performance. the gateway should be as close to the clients as possible and if the client is onprem then we recommend running the gateway onprem in one of our supported hypervisors such as VMware, Hyper-V, or KVM. This is due to NFS and SMB being latency sensitive when it comes to performance.
With that said, if you are wanting to test this on Windows with NFS, the Network Error 53 generally means a connectivity issue. The Windows NFS client is limited to NFS 3 only so you'd need to make sure that ports 111, 2049, and 20048 are open between the gateway and your client.
If you are still getting that error with all 3 ports open, please PM me your EC2 instance ID along with the Gateway ID and region.
Thank you,
Brian C.