Check passes in FSx Windows Server, but I can't deploy.

0

I am thinking of using a self-managed Windows Server with FSx for WindowsServer. It works fine from an EC2 inside the same VPC, checked with AmazonFSxADValidation. However, when I try to create it, I get the following error

File system creation failed. Amazon FSx is unable to communicate with your Microsoft Active Directory domain controller(s). 
This is because Amazon FSx can't reach the DNS servers provided or domain controllers for your domain. 
To fix this problem, delete your file system and create a new one with valid DNS servers and networking configuration that allows traffic from the file system to the domain controller as recommended in the Amazon FSx user guide: https://docs.aws.amazon.com/fsx/latest/WindowsGuide/self-manage-prereqs.html.

Do you know the cause?

Note that we are using Route53 for DNS, not Windows Server, and the necessary records in netlogon have already been created. I really appreciate any help you can provide.

已提問 1 年前檢視次數 274 次
1 個回答
0
profile picture
專家
已回答 1 年前
  • I thought I had succeeded because the check tool showed no errors. ....

  • I suggest you troubleshoot according to the troubleshooting instructions in the document I shared.

  • I followed the recommendations and wrote FireWall, etc., but it remained the same.

您尚未登入。 登入 去張貼答案。

一個好的回答可以清楚地回答問題並提供建設性的意見回饋,同時有助於提問者的專業成長。

回答問題指南