Event ID 8199 — Windows to UNIX Password Synchronization -- Configuration Issues
Applies To: Windows Server 2008
Windows to UNIX Password Synchronization -- Configuration Issues indicates the completeness or usability of settings that are configured for Windows to UNIX password synchronization.
When Password Synchronization is properly configured for Windows-to-UNIX synchronization, and a password is changed on a Windows-based computer running Password Synchronization, the Password Synchronization service determines whether the user's password is to be synchronized on UNIX computers. When the Password Synchronization service is operating normally, and encryption keys in both the UNIX and Windows environments match, it encrypts the password and sends it to the Password Synchronization daemon on each computer with which the Windows-based computer is configured to be synchronized. The daemon then decrypts the password and changes the password on the UNIX host.
|Product:||Windows Identity Management for UNIX|
|Message:||Error in receiving from socket. Check if SSOD is running on the UNIX host. %rhost = %1 %rWindows Sockets error is in the message data.|
Verify that the UNIX host computer is operational, and that the UNIX host is running the single sign-on daemon (SSOD) on the specified port. A Windows Sockets error is logged in the Event Viewer message data providing the exact failure error code.
For more information, see the topic "Install the Password Synchronization daemon on UNIX-based computers" in the Password Synchronization Help.
Retry Windows to UNIX password synchronization for any failed user password change attempts to verify that Password Synchronization is operating normally. Password Synchronization is operating normally when password synchronization succeeds and is operating under warning conditions if synchronization fails for some passwords but succeeds for others.
If password synchronization succeeds for some passwords but fails for others, Windows to UNIX Password Synchronization Configuration is likely fully operational, but there might be account- or computer-specific configuration problems preventing password changes from being synchronized on UNIX-based hosts.