Problem:

This is the scenario

Server 1

Local CCITCP2 or mfds running

CCITCP2 environment variable set to point to local CCITCP2

Fileshare running registered against local CCITCP2

Server 2

Local CCITCP2 or mfds running

CCITCP2 environment variable set to point to local CCITCP2

Fileshare running registered against local CCITCP2

In this scenario, on some versions of Server Express, if a client running in Server 1 tries to open a file under the remote Fileshare running in Server 2, it will fail with a 9/124 error. The same viceversa.

If both Fileshare register against the same CCITCP2, that is the CCITCP2 environment variable has the same value when they start, this problem doesn't occur, but with this setting, the server that is running the only CCITCP2 can not be down, otherwise servers won't be able to access to any file, local or remote.

Resolution:

This is due to a problem in CCITCP2 / mfds that is fixed in Server Express 5.0 WS3 in the platforms were it is available, otherwise it is fixed in WS4.