How to bind the Remote Desktop listening port to the specified Nic and IP address

The original post is as follows:
 
 
--------------------------------------------------------------------------------
 
The problem is that the server has two IP addresses, one is 192.168.x.x in the Intranet and the other is a public IP address. netstat-an finds that port 3389 is bound to the IP address in the intranet:
 
TCP 192.168.62.29: 1433 192.168.62.148: 4595 ESTABLISHED
 
TCP 192.168.62.29: 3389 0.0.0.0: 0 LISTENING
 
This is the case. Now the terminal cannot be connected from the internet. I have never seen such a situation before.
 
Some people who have seen this situation know what is going on? Or how can this problem be solved?
 
Added:
 
I want to know how the terminal port is bound to an IP address, or how to cancel the patch.
 
 
--------------------------------------------------------------------------------
 
I dare say that 99% of people do not know this technique, or they have never heard of it. Ah, let me give an authoritative answer and faint.
 
The port listened by the remote terminal to the specified Nic, IP address, Remote Desktop Nic, multiple IP addresses, Remote Desktop Nic, and Remote Desktop IP address.
 
In the terminal service configuration (tscc. msc) configuration (RDP-tcp properties \ Nic), select a NIC or all NICs, as shown in:
 
 
 
In this case, the server usually has multiple IP addresses, both the Intranet and the Internet. For security reasons, the Administrator only wants to log on to the Intranet IP address, select the NIC with the Intranet IP address to listen to. In this way, the Internet IP address cannot be connected.
 
From lcx. cc