We had this exact same issue with a very similar setup at the end of last year.
Was finally fixed by applying the October Windows update rollup - KB4041691 - although I guess this is now superceded by the update from this January.
Are all your 2016 servers (particularly the ones with the RDSH role) fully up to date?