By using AWS re:Post, you agree to the AWS re:Post Terms of Use
AWS re:Postre:Post

Issue on map shared drive to Windows instances, despite configuring Amazon Fsx correctly?

0

Hello! So I'm following an AWS workshop that involved the creation of an AWS infrastructure that applied Terraform to build it (https://catalog.us-east-1.prod.workshops.aws/workshops/e5122482-ded0-4259-94f0-c373f23c5257/en-US), and since the Amazon FSx file system had already been created and running, I used Fleet Manager to connect to the EC2 windows server instance via RDP and attempt to map a shared network drive on the server machine. However, in my attempts, I received errors saying that "the network path was not found", along with an error code of 0x80004005. I've already verified TCP/IP NetBOIS Helper service already being online and running, along with correctly entering the DNS name that was retrieved from the Amazon FSx console. I checked the security groups too, and didn't find an issue there, since I was able to easily connect to the instance, so I'm not sure what the issue is. Can anyone provide any help or guidance on this dilemma?

Topics
ComputeStorage
Tags
Amazon EC2Windows ProvisioningAmazon FSxTerraformWindows
Language
English
RetroSpect
asked 19 days ago282 views
1 Answer
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.

profile picture
EXPERT
Riku_Kobayashi
answered 18 days ago
profile picture
EXPERT
Giovanni Lauria
reviewed 17 days ago
  • RetroSpect
    18 days ago

    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!

Relevant content