new password not available on nis client for up to 10 minutes after yppush passwd

Hi,

We are currently in the process to move the user authentication for our AIX clients to a Windows 2003 server to authenticate them against the active directory entries.

What we have so far:

  • NIS master server on Windows 2003 Server with the unix-subsystem installed -> This is managing the users and passwords

  • NIS slave server on a AIX workstation -> This is managing the auto-mounts

  • several AIX workstations defined as NIS clients -> These are configured to use the AIX slave server as the NIS server

When I now change the password of a user on the NIS master and issue a yppush, the passwd.byuid and passwd.byname in /var/yp/<domain> on the AIX NIS slave are updated and it is possible to telnet into that machine with the new password.
However, it takes an awfull long time (10 minutes and more) until it is pushed further to the NIS clients.
The command ypwhich on the client shows the AIX NIS slave, so it definitely sees it but can not get the maps in a reasonable amount of time...

Can anyone help?

Thanks in advance.

Tom.

To answer my own question for those interested:

The entries for passwd.* in the mapcache-directory (C:\WINDOWS\idmu\nis\MapCache\<domain>) on the Windows 2003 Master NIS server have to be deleted before issuing the yppush command.

It looks as the NIS client is checking there for his passwd files, despite ypwhich showing the slave server...