Centrify

Tips for finding Knowledge Articles

  • - Enter just a few key words related to your question or problem
  • - Add Key words to refine your search as necessary
  • - Do not use punctuation
  • - Search is not case sensitive
  • - Avoid non-descriptive filler words like "how", "the", "what", etc.
  • - If you do not find what you are looking for the first time,reduce the number of key words you enter and try searching again.
  • - Minimum supported Internet Explorer version is IE9
Home  >
article

KB-2796: Some users are unable to access Centrify Samba shares

12 April,16 at 11:08 AM

Applies to:

All versions of Centrify DirectControl Samba

Question:

It is noticed that many Windows users are unable to access Centrify Samba shares. 
When \\servername\sharename is run, the following error message is shown: 

 The specified network name is not available

Centrify's adbindproxy.pl was run multiple times and all Centrify Samba daemons are running. 
smbclient -k -L localhost is also failing on the Unix server. 

Is there any reason for this?

Snippet from Samba level 10 debug logs:

  Cache entry with key = IDMAP/SID2GID/S-1-5-32-545 couldn't be found
  Cache entry with key = IDMAP/SID2GID/S-1-5-32-544 couldn't be 
  Cache entry with key = IDMAP/SID2GID/S-1-5-32-544 couldn't be found
  smbd/error.c:error_packet_set(61)  error packet at smbd/reply.c(729) cmd=117 (SMBtconX)  NT_STATUS_BAD_NETWORK_NAME
 smbd/service.c:make_connection_snum(1081)
  '/data/oy/data/Windows_Share' does not exist or permission denied when connecting to [Odyssey3_Admin] Error was Permission denied

Answer:

There is a possibility that Centrify Samba has a stale cache of the user uid/gid.

Please try flushing the Samba cache by using the command:

# net cache flush

This removes all the current items from the cache.

Afterwards, lock and unlock (using Control, Alt, Del) the windows machine and try to access the Centrify Samba shares again.

For more details, please see the man pages of Samba

http://www.samba.org/samba/docs/man/manpages-3/net.8.html

Note: When installing a new version of Centrify-enabled samba and Centrify's adbindproxy, we recommend customers to run adbindproxy.pl again to let new version take effect.

In adbindproxy.pl running process, it will run `net cache flush`(if answer is "yes" to "Reset the Samba User/Group ID Cache (Centrify Samba may create conflicting mappings) [Y] :" ) and  samba server. 

Related Articles

 articleKB-2375: Unable to access samba share with Unix group permissions articleKB-1589: Unable to access Samba shares after tdb limit is reached articleKB-6041: How to show current license type in use by adclient articleKB-6040: How to change the license type in use after adclient successful joined to the AD? articleKB-20210: Common Questions Regarding Centrify DirectControl and CoreOS articleKB-1771: Unable to read/write to a NFS/Samba share when user is more than 16 groups articleKB-10577: Get NT_STATUS_ACCESS_DENIED error when try to list files after connecting to samba share articleKB-6073: How to join the Linux/Unix Centrify Server to Active Directory with specific Computer Role? articleKB-7555: Unable to login as root after upgrade to Centrify Suite 2016 (CDC 5.3.0)