Just for a chuckle ... i was wrestling with this error message myself ... on
the server, the node ABC was creating sessions every 10 seconds at the
server, finally, i realized that the IP address in the ANR0484W error
message was not the same as the actual node should have been. (i.e. pinging
ABC revealed a diff IP) ... turns out someone had turned on the old "ABC"
server (under a different NT name, but the node name ABC was static in the
dsm.opt) that was backed up under that node name and was trying to contact
the ADSM server.  What a doozie!

Ilona Kersey
Siemens Westinghouse Power Corporation
Orlando, FL

> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
> Richard Sims
> Sent: Thursday, March 04, 1999 1:09 PM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: ADSM v3.1.2 (NT - type)
>
>
> >A scheduled Archive of a server failed with Message: ANR0484W - Protocol
> >violation detected.
>
> ANR0484W Session ____ for node ______ (___) terminated - protocol
> violation
>          detected.
>         Usual cause:  The specified client is attempting to
> establish a session,
>         but no password has been established.  When you
> registered the client on
>         the server you established a password, which must be used when the
>         client session is invoked, either implicitly with
>         "Passwordaccess Generate", or explicltly with
> "Passwordaccess Prompt".
>         Do 'dsmc q sch', a basic client-server query which goes
> through all the
>         password and network stuff that backup does, and will
> prompt for and
>         establish the password in the client area if
> "Passwordaccess Generate"
>         is in effect.  If such a password is in effect, a good
> response will
>         verify the client-server interaction.
>         Another cause:  A Client Schedule is defined with
> ACTion=Macro and the
>         macro whose file name is coded in OBJects= contains administrative
>         commands instead of client commands.  (Use Administrative
> Schedules for
>         executing administrative commands.)
>         Another cause:  An ADSMv2 HSM defect in which it caused
> the password
>         entry in /etc/security/adsm to be obliterated.
>         Accompanied by message ANR0444W.
>
> Richard Sims, BU
>