Moir,Elizabeth wrote:
>
> Here's what I've done so far.
>
> 1.  I pinged VM (that's the alias for our ADSM server) - That worked okay.
> 2.  I pinged the ADSM server IP address - That worked okay.
> 3.  I  changed the TCPServerAddress in the options file to the full address
> instead of the alias.  I tried to execute the ADSM Client.  It blipped on the
> screen and disappeared.
> 4.  I uninstalled the NT Service and tried to execute the ADSM Client.  Same
> blip.
> 5.  I uninstalled the entire ADSM client and reinstalled it.  (Compact
> install, all defaults accepted.)  Tried to execute the ADSM Client.  Same
> blip.
>
> When I look at my ADSM server logs, this node isn't even making it to the
> server.  There's no activity there at all.
>
> At one point when I was just trying to look at the registry entries (via
> dsmcscvi) it showed the clientnodename as being one of those playing card
> unprintables (a spade, I think) which leads me to believe the registry isn't
> getting updated.

Did you try with setting the node name using the utility because I had
the same problem.