Hello,
  I am having problems setting up a specific NT node using the latest 3.7.2
windows backup client.
I have a client which is called Argon and can be resolved from the tsm
server. The node has been setup on the server. I can also backup the machine
from the console of the node itself and the tsm server sees it as the
correct node in the logs.
The problem is when I try to set up a schedule on the server to kick off the
incremental backup on Argon, I get the following message in the logs:
ANR82093 Unable to establish TCP/IP session with 127.0.0.1 - connection
refused.
Now I know that this is the localhost address and the server is trying to
backup itself, but my question is why is it associating Argon with the
localhost address (127.0.0.1)???
If I run an nslookup on Argon from the server, it will resolve as the
correct address.
If I register it as a different node name, the same thing happens. And in a
50 node environment, why is it only happening to this one?

Has anyone seen this problem before?
Any help would be greatly appreciated.

                                                -john