Nonstandard port lost when using template
When using a different port in the remote desktop address (ex: 192.168.1.1:3390) and using a template to connect it seems to lose the port. I've also noticed issues when using the vpn ping before connect tool when using a different port. Is there a workaround? Is there a way to enter the port in a separate field, that seems like it would be the best way to do it.
All Comments (5)
Hi,
For the VPN ping, I'm not sure that we can do anything because ping by default does not support a port. It uses the ICMP protocol and not TCP or UDP.
For the other problem, I understand and I have opened a bug request.
Thank you
David Hervieux
a similiar issue I have found is when using the Autodetect (ping) option under alternate hosts it fails with a nonstandard port
Hi,
Do you have a solution for me because it's not possible to specify a port with a ping.
David Hervieux
the solution is to not specify a port with the ping. As in it should strip out the :port when doing the ping command.
Ah, sorry about that. I was not aware that the port was not removed. I will fix this.
David Hervieux