Identify how the files are being offered
Write down whether the media is on a USB drive, a network file share, a DLNA server or a Plex Media Server. These are different delivery arrangements. A computer being able to browse the NAS proves one file-access route, not that Aero has the matching browser or media client.
Manhattan’s current guide identifies a Plex application on Aero for media supplied by an existing Plex Media Server on a computer or NAS. That is a server-client path, rather than an instruction to paste an ordinary shared-folder address into an unrelated television application.
Check the server before the receiving app
On a server you are authorised to use, confirm that the desired library and media item are available through its normal management or client interface. Then identify the matching Plex app on Aero. Keep the server identity and intended user access with the comparison, without publishing private server addresses or tokens.
If posters or library names appear but a file cannot play, record that later playback stage separately. A completely absent library, a mismatched account and a media item that fails after selection are different observations. Avoid changing NAS permissions broadly before establishing which stage actually failed.
Use USB for a different source arrangement
Manhattan also documents local media playback from the data USB-C port with specific drive requirements. That can be an independent route for an authorised local file; it does not turn the box into a general NAS browser or add recording support.
For support, state the server software, storage location, receiving application and whether discovery, library browsing or playback fails. If the only thing configured was a DLNA share, the absence of a built-in DLNA browser is already a meaningful product boundary. Treating that as an unknown internet-speed fault can send the investigation toward the wrong device and account.