The first thing to do is solve the 'blips'.  Can you change the parameters
so that the command window doesn't close when the program terminates?  Or
open a command prompt from the start button and run dsmc there.

I don't use NT, I use OS/2, but I have had the 'blipping' problem many
times with different products, and the first step I do to debug something
is to change the properties so that the window doesn't close.

Bill Colwell
The Charles Stark Draper Laboratory
Cambridge Ma.
_________________________Reply Header_________________________
Author: ADSM-L AT vm.marist DOT edu
Subject: Re: ADSM and the NT Service
11-12-1997 02:25 PM

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.

Also, I made sure this person had administrator and backup operator rights.

Everything seems to be working except ADSM and I am at a complete loss as to
why.  Does anybody think I should try Version 3.  At this point, I don't.  My
instincts tell me this has something to do with NT not ADSM.  I even
uninstalled my own NT machine and reinstalled it just to make sure everything
still worked on my machine.  It did.  We have lots of NT servers using ADSM,
but only a couple workstations (mine being one of them).  Two of these
workstations won't work.  I'm open to any and all, creative or bizarre ideas.

Thanks.





ADSM-L AT VM.MARIST DOT EDU on 11/11/97 09:16:56 AM
To: ADSM-L AT VM.MARIST DOT EDU @ INTERNET
cc:
Subject: Re: ADSM and the NT Service

We had this problem.

In our case, DNS was not resolving the ADSM Server machine name as specified
in
the dsm.opt file.

Check this by issuing a PING command from your client to the server to check
the
network connectivity between the machines.

Regards

Phil

Phil Chissell       phil.chissell AT research.natpower.co DOT uk

This represents the view of the author alone and is not to be
considered as the position of National Power PLC