0 vote
For RDP connections (and others), it is possible to put an "alternate host" in the "description" section with a port scan. The idea being that when you connect, it does a port scan of the primary connection and if it's blocked, RDMS tries the alternate hosts instead - this works absolutely brilliantly.
But.... It doesn't work if the connection type is a website/URL. RDMS still does the port scan to check, but it doesn't actually try the alternate host if that port scan fails, it just trys to connect to the primary URL regardless of the port scan results.
I'd class this as a bug, but apparently that's the way it's meant to be. Any chance we can get RDMS to look at the port scan result and then act appropriately?
Hello,
I will create a bug ticket but it could be a feature request depending on why it does not work. Anyway, for us it will the same work but as a bug, we might class it with an higher priority
Regards
David Hervieux
Any updates here David?
Hello,
This should be fixed since version 2023.2.20.0. Could you update your version to the latest and see if it works for you?
Regards,
Hubert Mireault