Click filename to download:
nsync1.exe; 116845 bytes; Date/Time: 07-30-1997/04:03PM

NETSYNC4.NLM version 1.11, NETSYNC3.NLM version 1.11, and REMAPID.NLM version 1.01 are updated NLM's associated with NETSYNC. The main problem resolved by this update is in relation to password synchronization.

NOTE: Always make a backup of applicable files before applying new fixes.

1) On NetWare 4.1 servers, flag NETSYNC4.NLM contained in the SYSTEM directory normal or sharable, read/write.

     FLAG NETSYNC4.NLM N -or- FLAG NETSYNC4.NLM S RW

2) On NetWare 3.x servers, flag NETSYNC3.NLM and REMAPID.NLM contained in the SYSTEM directory, normal or sharable, read/write.

     FLAG NETSYNC3.NLM N -or- FLAG NETSYNC3.NLM S RW
     FLAG REMAPID.NLM N -or- FLAG REMAPID.NLM S RW

3) On 4.1 servers, rename NETSYNC4.NLM contained in the SYSTEM directory to NETSYNC4.ORG. On 3.x servers, rename NETSYNC3.NLM and REMAPID.NLM contained in the SYSTEM directory to NETSYNC3.ORG and REMAPID.ORG respectively. This is for backup purposes.

4) On NetWare 4.1 servers, copy NETSYNC4.NLM provided with this update into the SYSTEM directory. Flag NETSYNC4.NLM as sharable, read only.

     FLAG NETSYNC4.NLM S RO

5) On NetWard 3.x servers, copy NETSYNC3.NLM and REMAPID.NLM provided with this update into the SYSTEM directory.. Flag NETSYNC3.NLM and REMAPID.NLM sharable, read only.
     
     FLAG NETSYNC3.NLM S RO
     FLAG REMAPID.NLM S RO

6) To activate the new NLM's, on the 4.1 servers, unload NETSYNC4.NLM. This should in turn unload the nlm's on the 3.x servers.

7) To avoid memory table corruption, down and restart all 4.1 and 3.x servers that are associated with NETSYNC.

Changing a password on the 3.1x server did not result in the password expiration date getting synchronized to the 4.10 server and thus it didn't make it to any of the other 3.1x servers either.

Failures in password synchronization on 3.1x servers. Password synchronization would fail if NetSync3 was loaded and used a connection where the LogKey information was still set. We now free that data (if it exists) when NetSync3 loads.

Cleaning up a users mail directory on the 4.10 server after the user had been deleted did not always work. The current working directory of the thread group was sometimes getting changed out from under us by another thread, causing the deletion of files and the removal of the directory to fail. We now use full path/file names in a deletion.

Fixed a problem where login scripts on the 3.1x server were not getting deleted when the "Login Script" attribute was deleted on the 4.1 server.

NetSync4 was abending when it tried to use some data that NDS was suppose to give to us but didn't. We now check to make sure the data is there before we use it. Mark fixed the related problem in NDS so that it gives us the data that it should have.

Self-Extracting File Name:  nsync1.exe

Files Included       Size   Date         Time    Version   Checksum

\
  NETSYNC3.NLM     102467   06-15-1995   03:31PM
  NETSYNC4.NLM      53556   06-15-1995   03:33PM
    NSYNC1.TXT       4201   07-30-1997   04:03PM
   REMAPID.NLM       9941   03-03-1995   04:56PM