Access SMB over a custom port

I have the fileserver hosted on AWS. I was using smb port 445 to access the fileserver. I found out that some ISPs have blocked port 445, so I set up my fileserver instance behind AWS network load balancer and create a custom listener port on NLB and forward the request on this port to fileserver instance on 445. But windows share uses port 445 by default, so is there a way to make a request to nlb on a custom port and indirectly to my fileserver since I have a forward rule on NLB. Is this possible?

Note: I know that there is no syntax for alternate ports on windows share. I am looking for a workaround

SMB is generally not a protocol used over the internet. You should set up a VPN between your client (laptop?) and AWS and tunnel SMB through the VPN. Then you won’t have to worry about ISPs blocking port 445, won’t need the AWS fileserver open to the world and also will have an extra layer of security. There are many options for VPNs, both open source and commercial.

Hope that helps :)