TSM Server 5.2.0.0 on WIndows2000.
TSM Client 5.2.2.5 on Windows2000.

This was working just fine until yesterday. Started getting ANR8212W
messages about unable to resolve an address for this node, but the message
looks strange:

ANR8212W Unable to resolve address for is
spike.
ANR2716E Schedule prompter was not able to contact client SPIKE using type 1
(is
spike 4932).
ANR8212W Unable to resolve address for is
spike.


And yes the line feeds are correct! I have a -console session running
looking at this. I just don't understand where TSM is comming up with a name
if 'is spike' for this node! From a command line I can PING SPIKE with no
problems. I've even added DNSLOOKUP NO to the server option file. I've
queried ADSM.ORG, but dont' find any hits on this type of error(?).

Anyone seen anything like this before?

Bill Boyer
"An Optimist is just a pessimist with no job experience."  - Scott Adams