1.  The admin client is usually installed in the saclient subdirectory.
You must customize the dsm.opt file in that subdirectory to have the correct
TCPSERVERADDRESS.
If you don't it causes the client to start up, prompt for your id and
password, then disappear as you describe.

2. Check the saclient subdirectory for the dsmerror.log file.  It should
have an error message in it describing the problem.

************************************************************************
Wanda Prather
The Johns Hopkins Applied Physics Lab
443-778-8769
wanda_prather AT jhuapl DOT edu

"Intelligence has much less practical application than you'd think" -
Scott Adams/Dilbert
************************************************************************




> -----Original Message-----
> From: Eckert, Allan [SMTP:t0185 AT PSCO DOT COM]
> Sent: Friday, July 30, 1999 5:35 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Administrative Client on Windows NT Workstations
>
> We have a number of Windows NT Workstations with ADSM installed on them.
> One
> of these works perfectly fine when we use the ADSM Administrative Client.
> Two of them, one of them is mine, when you attempt to use the
> Administrative
> Client look fine when you are logging in, but shortly after that
> everything
> disappears without a trace. The setup to install ADSM appeared the same on
> all of these. Any suggestions or hints as to where we may have gone wrong?
> Thanks.