According to the documentation forwardIp could only be an IP, but when looking to the source it is read into the parameter remoteServerHostNameOrAddress.
This is a very nice feature when the target ip is changed very often (dyndns) because the built-in netsh portproxy is not able to use dns as a intermediate layer. I think it should be mentioned in the docs!
According to the documentation forwardIp could only be an IP, but when looking to the source it is read into the parameter remoteServerHostNameOrAddress.
This is a very nice feature when the target ip is changed very often (dyndns) because the built-in netsh portproxy is not able to use dns as a intermediate layer. I think it should be mentioned in the docs!