What the messages guide'll tell ya!

ANS1872E Unable to connect to NetWare target service 'server-name'. Make
sure the TSA NLM is loaded on the specified machine.

Explanation: ADSM interacts with the Target Service Agent (TSA) and the
connection cannot be made to the Netware server-name.
System Action: Processing stopped.
User Response: Ensure that the TSA is loaded and retry the ADSM command


Things to try...

Run an "load dsmc" and run some quick queries to see what information it is
prompting for, if any (Netware/ADSM passwords/ids), etc

Make sure the "server" address matches what's returned by "getipxad" on the
Server(SP2).
getipxad can be found in the server install dir (/usr/lpp/adsmserv/bin).  If
you
can have your network people issue IPX Pings, do it between the two systems.

Make sure your machinename and/or nodename is set to the nodename registered
on the server.

Try running a "q tsa" to check to see ADSM is interacting
properly with the modules.

If you can run IP, try that....

Would have to see at least options file before commenting further.

ADSML

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Thomas Bull
> Sent: Wednesday, September 01, 1999 5:00 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Netware 5
>
>
> Hello All,
>         I'm running ADSM 3.1. level 2.40 on Windows NT 4.0 (SP3)
> - I'm presently
> backing up about 12 Novell servers - 3.x and 4.x. I have a new Netware5
> (w/SP2) box that i'm trying to backup. I have installed ADSM client
> version 3.1, level 0.7e. a 'load dsmc i' returns the error:
>                 ANS1872E Unable to connect to NetWare target
> service 'ANSOS'.
>                 Make sure the TSA NLM is loaded on the specified machine.
>
>
>
> some nlm info:   TSANDS.NLM v5.00 9-10-98
>                   TSA500.NLM   v5.01 2-19-99
>                    SMDR.NLM  v5.03  3-12-99
>
> i have verified that the tsa's are loaded
>
> i have verified the node (ANSOS) is registered with my adsm server
>
> some dsm.opt info:
> COMMMETHOD is IPXSPX
> IPXSERVERADDRESS is correct
> Admin login w/correct password
>
> I have a ticket opened w/adsm support on this. they had me run a trace,
> and are looking at it now.
> i thought i'd throw this out on the chance somebody else has had a
> similar problem.
> any ideas would be appreciated!
>
> Thanks,
>
> Tom Bull
> Salem Hospital
> Information Services
> (978)741-1215 x2033
> tomb AT nsmc.partners DOT org
>