Richard Thanks...
I did find the following message in the TSM Server log for the clients
that have been failing
with this issue.
ANR0480W for node Sul300 terminated - connection with client severed
03/16/08 04:01:16 ANR0480W Session 73321 for node Sul300 terminated –
connection with - connection with client severed.
ANR0480W Session 73424 for node Sul400 (WinNT) terminated - connection
with client rsevered.
ANR0480W Session 75643 for node Sul500 (WinNT) terminated - connection
with client severed.
ANR0480W Session 75800 for node Sul600 (WinNT) terminated - connection
with client severed.
Tim
Richard Sims wrote:
Tim -
The -50 return codes make me think of networking or pipe
communications failure, where the former would probably be a hardware
condition, and the latter could be OS congestion issues. Your
initial posting contained elements suggesting that the system
involved is rather busy chasing ITM and Network Associates monitoring
tasks, which might be getting in the way. You might check the TSM
server Activity Log, if not the Windows Event Log, to see if any
allied condition evidence there.
Richard Sims
