1 Answer
- Newest
- Most votes
- Most comments
0
Hi, generally you would see this error when the storage gateway is not allowing all the three required NFSv3 ports. I would suggest verifying the gateway EC2 instance security group and check if it has allowed ports 20048, 111 and 2049 in its Inbound rules from the client IP address that you are trying to mount. You can verify network connectivity to these ports using Test-NetConnection PowerShell commands from the Windows client. Example command : Test-NetConnection -ComputerName <Gateway IP> -Port <PortNumber>
answered 2 years ago
Relevant content
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated 2 years ago
I've ensured that all three inbound rules are present in the security group. Ports 20048 and 111 are of type Custom TCP, protocol TCP and the source is set to only my IP address. Port 2049 is type NFS and protocol TCP with the source set to only my IP address as well. In powershell all the netconnections failed. Is there something I have to configure in order to connect successfully?