Hi,
Thanks for your patience!
After research, I think you may have problems with static NAT configuration on your router. I suggest that you should configure a static NAT on your router instead of using your way, I guess, to configure IIS to forcibly bind the public. This is because even if IIS forcibly bind the public IP, router will not send traffic to it. You must first ensure that the route can reach the VM.
When we need to communicate with outside network, for instance, with public network or with another private network but need to go through public network first, we must configure NAT on the router inside your private network where your VM is located. The function of NAT (Network Address Translation) is to translate public IP 121.52.158.248 to your VM IP address domain (i.e. if your VM IP is 192.68.11.1, the public IP can be translated to 192.68.1.4) when traffic is coming from outside port. In addition, in terms of outside traffic, it is NAT works first and then the router select certain IP. On the other hand, when it comes to inside traffic, the process is reversed, that is, your router works first and then your NAT on your router.
The above example is based on routers that use IOS facilities. Different routers may have different rules for configurating NAT.
So, you need to firstly identify which kind of router your organization uses and then come to visit the corresponding vendor's website to find certain static NAT configuration handbook to configure your NAT.
Thanks for your support! Besides, would you please help me Accept Answer. An accepted blog can be put on top of our forum, so that people who have a similar issue can get access to their solution more quickly. I would really appreciate it if you could support my work.
BR,
Joan
If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.