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
anonymous
  • Under Review
Avatar
0
Thomas-Louis Laforest

Good day,


@kirsten Martinez : what does that mean under review, it is a progression or a setback versu considering for future release ?


Thanks you

Avatar
0
anonymous
Quote from Thomas-Louis Laforest

Good day,


@kirsten Martinez : what does that mean under review, it is a progression or a setback versu considering for future release ?


Thanks you

Thomas,

It means we are revisiting the topic and will have discussions around it. Usually, these discussions are centered around how we can possibly design and build the feature/enhancement into the product. If it plays out well, we'll schedule it on our roadmap.

Avatar
0
Shane

For whatever it's worth, failover capability would be a strong incentive for me to renew my license next year. I've only had to make a domain change very suddenly once so far, but it can happen and it was both memorable and time-consuming to manually update all of my clients. Being able to use a secondary to simply go "here's a new config with the new primary, queue update all" would have saved a lot of messing around.

Avatar
0
Thomas-Louis Laforest

Good day,

Any update on this we are in the process of planing change to the port and domain we used when did the original setup. We are looking at a way to completed an update without breaking anything. 

Right now I’m planing to use some form of port redirection to kept the old configuration working when the client are receiving the updated information but this feature will help a lot. 


Thanks you

Avatar
2
Jason Tenpenny

This would be super helpful for us as well. We host our CWM instance in-house. We have a failover internet circuit, but Control can't take advantage of it. As Control is our primary means of connecting to our client machines, if they can't checkin to the Control server, it's perfectly useless. Having the ability to have a secondary IP for the clients to try to connect with would be a hugely beneficial enhancement.

Avatar
2
Jamenn Van Grinsven
This would be very helpful as we allow clients to use the Connectwise Control software to remotely access their office computers. If DNS goes down, these clients are unable to use the service. If we had a failover then clients would not even notice and there would be less heartburn when these issues do occur. 
Avatar
0
Brent59

Failover WAN is a must have in todays Remote Support World and getting a secondary Cable Modem is cheap. Please add this feature ASAP, cannot be that hard to code just have a Primary DNS Name and a Secondary DNS Name and have the client poll when it does the Screen Update in the Console. We had an issue today with an outage and were unable to connect until I updated our external IP and we had to call remote customers to reboot their PC's, this is not an efficient method to explain to customers why. Please add a multihomed Client so we can add in Primary and Seondary DNS Names.or IP Addresss.

Thank you for Consideration.

Avatar
1
Caitlin M Barnes Team Member
  • Considering for Future Release
Avatar
0
JoM
Quote from 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.

Yes, that would be useful, being able to add an IP address would means that even without DNS machines would still connect.



Top contributors

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