PM76509: Shipping server needs to account for Windows 'deferred bind on connect' behavior when strict port allocation in use.

Rational ClearQuest Fix Pack 10 (7.1.2.10) for 7.1.2
Rational ClearCase Fix Pack 10 (7.1.2.10) for 7.1.2
Rational ClearQuest Fix Pack 06 (8.0.0.6) for 8.0
Rational ClearCase Fix Pack 06 (8.0.0.6) for 8.0

APAR status

• Closed as program error.

Error description

• When using the IBM Rational ClearCase MultiSite shipping server
  in a firewall-enabled configuration with strict outbound port
  allocation on Microsoft Windows 2008 R2 Server, connection
  errors may occur, causing hosts to be incorrectly flagged as
  down.
  
  This issue is caused by a new Windows Sockets behavior in the
  most recent version of Microsoft Windows.
  
  The current workarounds are:
  1) Do not use MSSHP_STRICT port allocation.
  2) Use a Unix or Linux host to provide firewall-compatible
  shipping server services.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  shipping server fails on connect command even if with a
  valid binding port
  

Problem conclusion

• A fix is available in ClearCase versions 7.1.2.10 and
  8.0.0.6
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  CLRCASE MSITE W

• Fixed component ID

  5724G3200

Applicable component levels

• R800 PSN

     UP