We are seeing a strange situation with some of our clients. The trouble
starts when the client sees a TCP session fail and the server does not. The
client establishes a new session while the server keeps the old session
around with an ever-growing wait time. If the first session was writing to
disk (we use file device classes for incoming backups) the server will
assign a mount point to the replacement session and leave a mount point
assigned to the original session. At some point, the client reaches its
maximum number of mount points and we get ANR0539W messages like the
following:

ANR0539W Transaction failed for session 1234 for node NODENAME. This
node has exceeded its maximum number of mount points.

Our server is TSM 5.2.6.0 running under mainframe Linux. All of the
affected clients are using either 5.3.0.0 or 5.3.2.0 client code. Six
out of seven of the affected clients are Windows 2003 systems. The
seventh is an Intel Linux system. All of the affected clients are
managed by the same organizational unit, which has a history of
somewhat peculiar systems administration practices. I am still
waiting for information on which parts of the network infrastructure
are shared by the affected clients.

Is this a known problem? If not, does anyone have any suggestions for
trouble-shooting?