Hello guys,The reason of the issue is most likely usage of WDT version 19.09 (see comment from Moon James below).Fixing this issue is either installation of newer version 19.10 or rollback to previous 19.08.Both suggestions require from your side: Creation of new toolset request installation ticket and provide us timeslot to install it.Thank you"This issue was the reason WDT 19.09 was recalled. A bug was present in 19.09 that caused a failure to clear the original prismserver0 section, resulting in the subnet change attempting to contact the old PRISM server. Site should either move to WDT 19.10 which was released to fix this specific issue, or roll back to prior toolset.