For us updating the ID was easy, but it didn't solve the problem. I was connecting remotely to a client's computer using Visual Studio and the right click wasn't bringing up the menus, or more specifically context menus were not visible during the remote connection. Because of this, I used Remote Utilities to connect to the computer, get the [censored] ID and password and connect using [censored] where I could see the menus.
While using [censored] , my connection was never reset and operated smoothly for hours at a time. Large file transfers were possible without interruption, but the Remote Utilities connection was unstable for more than a few minutes at a time (5-20).
I still use Remote Utilities and like it, but this problem is not a networking issue, or at least it isn't an issue that isn't solvable by better try/catch blocks within Remote Utilities. My office is on a Fiber network which has only gone down 2-3 times within the last 4 years. The problem exists between each location I connect to and is limited to Remote Utilities and not [censored] connections.
I had considered setting up my own Remote Utilities relay host to see if that would help, but have just been too busy. It could be a connectivity issue between Utah and where ever the Remote Utilities server is hosted.