1 Respuesta
- Más nuevo
- Más votos
- Más comentarios
0
Hello.
Why not try connecting using the FSx IP address instead of the DNS name?
If you can connect using the IP address, there is a possibility that name resolution is not working properly.
Contenido relevante
- preguntada hace 5 días
- preguntada hace un mes
- preguntada hace un mes
- Como solucionar el error: Supplied Policy document is breaching Cloudwatch Logs policy length limit.Respuesta aceptadapreguntada hace 12 días
- OFICIAL DE AWSActualizada hace 8 meses
- OFICIAL DE AWSActualizada hace un año
- OFICIAL DE AWSActualizada hace 4 meses
- ¿Cómo puedo resolver el error “Failed to start the job flow due to an internal error” en Amazon EMR?OFICIAL DE AWSActualizada hace 2 meses
I figured that the IP address could serve as an alternative, but when finding instructions to attach the FSx file system, it showed a few approaches that utilized either the DNS name or DNS alias.
Much to my surprise, I actually came to find a solution to my dilemma! Turns out that my security group had the inbound rule limited on that end, while my outbound rule was configured correctly. Once I added another inbound rule to the security group, the mapping of the network drive finally worked!