Closed ArlenRicard closed 6 years ago
If not all of your clients are running the version that includes this feature, it will not work. I am guessing that is the problem.
I understand, but an out-of-date client would cause this possible error when trying to connect to the upgraded server? I'm working on a feature to be able to update all outdated clients, I have hundreds. It is impossible to update all of them individually. But that may be the cause of the mistake.
I feel like that would be suted well with a scheduled task but it wouldn't be too hard to incorporate update feature.
To answer your question yes it would since I added new client code.
Yes, I'm currently using the schedule. But I need to greatly improve the feedback form of the script, since some of them did not reconnect after the process. So I'll run several tests before, until I have a definitive solution. Better to use the schedule really. Because if we add so many resources to the client and server, they will soon become xD operating systems. And they will lose that simplicity. I will update all the terminals, and I will return soon with the feedback.
Okay, the problem is solved. It really was because of outdated clients. After everyone was updated, the error did not occur again.
After adding the client hostname display feature, this error has occurred a lot while trying to list the connections: Prior to adding this feature, such an error never occurred.