Add the ability to set an alternate relay address

Avatar
  • updated
  • Considering for Future Release

Our situation :
We have 3 offices in Canada (HQ, A, B)
HQ-A have MPLS link between them,
HQ-B use VPN over internet.
All location have independent internet access.

We use access session on all system in all location, but the relay is located in the HQ.

Curent setup.
1 DNS name to the server that resolve to an external IP when out of the local infrastructure and an internal IP when inside the infrastructure.
- This way system on our internal network dont use the public internet access, it more secure, reduce the global bandwitch and load on our front end firewall.
The issue, if the inter-site link go down, the access session will not be able to connect, as the DNS will still resolve to the internal IP, resulting in disconnection.

Our need, be able to setup 2 URL for the a access session, as such when the 1st is irresponsible the client can try connecting to the second one, with a retest every X to go back to primary.
With this we could setup our client with a internal URL as primary and an external URL as secondary and still reach our system if the VPN or MPLS go down, but not the internet.

Duplicates 3
Have relay traffic listen on two different ports

Partner was having a problem with a access agent connecting to the ScreenConnect server using port 80 for the relay server.


He thought port 80 would be okay on all networks but some routers handle it differently. He mentioned that having two relay ports it could listen over would help with that situation


add failover options for the ScreenConnect server

add failover options for the ScreenConnect server, parnter has a backup ISP and would like ScreenConnect to failover to the other ISP when the primary one goes down

Allow ability to have 2 relay URI's

Partner would like the ability to have 2 relay uri's for easier/safer Uri migrations, as well as allowing for more disaster recover situations.

Avatar
1
Kurtis Kain

We have just installed a backup VDSL connection and would love for ScreenConnect to have installed a secondary DNS name to try, e.g Backup.company.com to allow the clients to connect to if the main connection is lost.


This means we don't have to wait for the DNS change to replicate is we go to a dynamic system, even then we'd have to reinstall all the clients to a new DNS name anyway.


Really looking forward to this!

Avatar
1
Michael Suiter

This would also need to have alternate ports in case the network a device is on has restrictions preventing the default port from working (such as mobile users, or one-off systems on networks you don't have control over).

Avatar
0
anonymous
  • Completed
Avatar
0
anonymous
  • Started
Avatar
0
anonymous
  • Planned
Avatar
0
anonymous
  • Pending Review
Avatar
2
Thomas-Louis Laforest

Good day,

Do you have any update as the status change a lot on this request (from Completed, to Started, then Planned and now Pending Review)

Avatar
0
Mark Bell

Here's another application for this feature... My SC server hosts other applications using both IPv4 and IPv6. I would like to be able to provide specific IPv4 and IPv6 addresses for both the relay and web server to listen on. While I understand I could use the "WebServerAlternateListenUri" parameter to specify and IPv6 address, I am currently using that for port 80 so my users can just enter the server's FQDN and not have to type in "https" in the URL when accessing a support session.

Avatar
3
Derm

I would like to see an option for fallback addresses similar to how LabTech does it. remote.mydomain.com|backup remote.mydomain.com|1.2.3.4 etc. You can add additional names/ip addresses in order you would prefer it to check in.

Avatar
2
anonymous
  • Considering for Future Release


Top contributors

Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar
Avatar