I'm glad that you were able to resolve your issue and thank you for posting your solution so that others experiencing the same thing can easily reference this!
Since the Microsoft Q&A community has a policy that "The question author cannot accept their own answer. They can only accept answers by others ", I'll repost your solution in case you'd like to "Accept " the answer. Accepted answers show up at the top, resulting in improved discoverability for others.
Issue: Cannot reach Azure File Private Endpoint from on-premises stations.
Solution: Customer shared - "This was resolved. A member of the company's IT staff advised that the CATO LAN socket was using the same IP. This is odd because the IP used for the private endpoint was assigned by Azure and didn't show up in the connected devices list on the NVet. However, recreating the endpoint with a static IP different from the previous IP resolved our issues."
If your issue remains unresolved or have further questions, please let us know in the comments how we can assist. We are here to help you and strive to make your experience better and greatly value your feedback.