Microsoft recently released a patch to its Windows NT 4.0 RPC service to address a vulnerability to Denial-of-Service attacks. Although the CIFS Import Users functionality does not cause or participate in any denial of service attacks, the patch does change the Window NT 4.0 RPC interface which, in turn, affects the CIFS Import Users functionality.
The interface changes are in the process of being tested, and we will release a patch to correct this problem soon after NetWare 6 ships.
If the Primary Domain Controller (PDC) is a Windows 2000 server, Windows workstations might not be able to access the CIFS server. To fix this, complete the following steps:
Specify the following parameter in SYS:\ETC\CIFS.CFG:
-PDC PDC_name IP_address
For example:
PDC ONENET 130.57.66.134
Enter CIFSSTOP and then CIFSSTRT.
If the PDC and CIFS servers are on different subnets, the -PDCNAME option (which uses DNS resolution) might not work. Use the -PDC option instead.
Trying to change a password from a Windows 9x or NT4 client workstation might fail if the default network username and password in the client's cache is not a valid combination on the CIFS server where the password change was attempted.
To avoid this problem, validate the username and password combination in the client's cache on the CIFS server before attempting the password change. You can validate by attempting to access the file system on the CIFS server by browsing to Network Neighborhood.
When the CIFS password (simple password) on NetWare server is changed using the NET PASSWORD command on a Windows 9x client, the client always sends the old and new passwords in upper case. As a result, the regular NDS password update will not be successful if the old regular NDS password contains lowercase letters. Also, the new password will be stored in upper case.
For Windows NT/2000, the user should provide a case-sensitive password; if not, the regular NDS password update will not be successful.
If the CIFS server on NetWare is the only member of a workgroup, then the workgroup will not appear under Network Neighborhood. However, it might be possible to locate the server using the Find Computer feature.
The -ASYNC, -OPLOCKS, and -UNICODE options are not supported with this release. Make sure these options are set to Off.
You might occasionally find that your CIFS server is not visible using Network Neighborhood. This can happen if you have a domain that contains only Windows 95/98 and no NT/2000/XP servers or clients. To correct this problem, enter the server name or IP address in Find Computer.
CIFS users might occasionally see an Out of Memory error when using MS Paint on a Windows NT workstation. This error message is incorrect and no processes are out of memory. The error message will disappear if the data file is first saved to local storage and then copied to the remote storage directory.