Connecting to the host xxxxx.com is failed. While modifying the client WIZARD

Kindly help us (and therewith yourself) by providing more information what you have tested and validated, besides a working backup, stating also how things are actually setup?

For example is the NMC that you connect to running on a different system than the NW server? This as the NMC needs to be able to directly connect to the client in question (whereas it might have been more logical to have all the communication go through the NW server). For us that meant a re-design of where to host an external NMC, intended to manage various NW servers, by not putting it in a management subnet, able to only reach the NW servers, but to host it in the backup subnet that multiple NW servers are hosted in from where all the clients can be reached. Also besides using the external NMC, one can also still run NMC on the NW server itself and use that mainly for NW Client Wizard if the external NMC is not able to contact the clients directly... we initially wanted to decouple backup management via NW NMC from the backup subnet, but alas that is not how NW is actually build, so for the NW Client Wizard it needs to be able to connect directly to the NW clients from (external) NMC server end (not the NMC client where the java based NMC client is started in case you might not start the NMC client on the NMC server itself, we use separate management systems for that).