Hi Betsy!
99% chance that the computer name of this client is changed.
The ADSM client tries to connect to the ADSM server using a new client name
(since the nodename is the computername if not specified otherwise in the
dsm.opt) while the server contacts the client using the old client name.
I have seen this here too. The solution is to rename the ADSM client at the
server side. Don't forget to rename de filespaces too since the computer
name is part of the UNC name.
Kindest regards,
Eric van Loon