.
Although I can't offer any explanation, I'm definitely seeing this too.
Been going on for quite a while. TSM 5.3.4.0 on AIX 5300-05-05. Large
number of Windows clients, running every client release from the newest
build of 5.4 back to V2. When I noticed it before, I had filed that
knowledge away as "Just One Of Those Things" to be investigated when I
had a little spare time someday. Now I'm curious.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu
==== "If you knew as much as you think you know, You would realize =====
=== that you don't know what you thought you knew!" -- George Ankner ===


On Fri, 14 Sep 2007, Steven Harris wrote:

>I've got some new windows nodes just defined  on two different AIX TSM
>servers, and they are getting ANR8214E errors with the 127.0.0.1 address on
>their overnight schedules. This is the same issue that Allen Rout posted
>about on July 31 (post included below).  Now the funny thing is that I set
>up a clientaction backup yesterday on these nodes, recycled the CAD Service
>and the clientaction backup ran with no problem, the client then found its
>next schedule and all appeared to be well, but then, last night more
>ANR8214 errors.
>
>Client 5.4.1.2 Server both AIX 5.2.4.1 (yes an upgrade is in the works)
>
>Allen - Did you ever get a resolution to this?
>
>Regards
>
>Steve
>Steve Harris
>TSM Admin
>Sydney Australia
>
>Allen Rout posted this on July 31
>
>>So my 'INT' TSM server has been up for working on two months.  Current
>>sessions are in the 220K zone.  Yesterday, I noticed an odd pattern,
>>which has evidently been happening for some time.
>
>
>>07/30/07   18:00:02     ANR8214E Session open with 127.0.0.1 failed due to
>
>>connection refusal. (SESSION: 1209)
>>07/30/07   18:00:02     ANR2716E Schedule prompter was not able to contact
>
>>client [some client name] using type 1 (127.0.0.1 1501). (SESSION: 1209)
>>07/30/07   18:00:33     ANR8214E Session open with 127.0.0.1 failed due to
>
>>connection refusal. (SESSION: 1209)
>>07/30/07   18:01:03     ANR8214E Session open with 127.0.0.1 failed due to
>
>>connection refusal. (SESSION: 1209)
>>07/30/07   18:01:33     ANR8214E Session open with 127.0.0.1 failed due to
>
>>connection refusal. (SESSION: 1209)
>
>>Continuing every 30 seconds until midnight.
>
>>The client in question has a perfectly normal (private) IP in its'
>>node entry.
>
>>The session quoted in the connection refusal message seems ludicrously
>>low.  I'm not sure where that came from.
>
>>Apparently the box has been doing this for months. :) Anybody have a
>>clue what's happening in there?
>
>
>>- Allen S. Rout
>