How Can Clients Use TLS 1.2 When the Server Only Supports TLS 1.0 (Windows Server 2003)?

Seen this kind of thing in both banking and healthcare providers, and windows is the least offensive product to work with, but also the most cringe for CVE’s. The data and the software have somehow gotten into a time bubble because the organisation chose not to migrate their data while the full workforce of integrators was focused on that particular migration. All the tools to do the job, the developers, the dba’s, and even the vendors no longer exist - but for some reason - patient or customer lifetime + 10 years ( can’t remember) means the data has to live on because of regulation. It starts as a risk issue and continues to be a risk issue, rinse and repeat every couple of months ad-nauseam… The cost gets higher and higher as the system sits there - oddly being used in-spite of any reason that would say put another system in front of it and only pull and migrate data as needed - as a minimum. The old system remains as the reference as the updated systems aren’t the official system of record for the old data, just the new data. Things get fun when you’re four generations on and the old system is still in the heart of the solution somewhere but no one knows absolutely anything about it. Including super user or system accounts. So, standing on a soapbox saying it’s wrong - lol - yep - everyone knows that. But the decision to not progress was probably made in 2005 by someone that is now dead and buried probably before most current IT generation got out of nappies. It’s not totally unusual to have to deal with systems that date back to the 1980’s or 1990’s. I had to do work with systems that went EOSales in 1979 - that got migrated and shutdown post 2015. We were repairing boards and subsystems like you would an expensive stereo system - pulling boards, testing, and replacing components old school using multimeter and soldering iron. There’s almost always someone riding their way out to retirement on the back of these systems - and you can never find them to get proper answers about the systems. One place we worked we figured out the guy ran maintenance scripts in cron, when he went on holidays he disabled them. That way he was always taking calls to rescue the business and reaffirm his importance - but these are different stories and the advent of Linux has bought in a whole truckload of additional talent in the *nix space. I’ll stop now before I really start ranting about this entire space… but to say yes, it’s a bugbear for a lot of people.

They live behind a firewall and you use an sslvpn to tunnel traffic into them.