>Richard,
>Here is an example:
...
>                    TCP/IP Name: ECHNATON_GYN
>                 TCP/IP Address:
...

Gerhard - Thanks much for taking the time to prepare the sample.

I'm not sure what to make of the empty TCP/IP Address field, which should
rightly contain the address of the client node as of the last time that it
contacted the server.  It might possibly be the case that the client software
does not support providing this information to the TSM server, or it is having a
problem obtaining it.  It might also relate to your anomaly...

>Sometimes we see the message:
>
>07/16/04 13:06:29     ANR1639I Attributes changed for node GYN.ECHNATON: TCP Ad
>                        dress from  to 149.148.171.22. (SESSION: 24044)

I wonder if this is appearing because a reverse lookup...

        /usr/bin/host 149.148.171.22
        echnaton.gyn.akh-wien.ac.at is 149.148.171.22

yields a network hostname which, within your TCP/IP domain, differs from the
client TCP/IP Name?

    Richard Sims