I have a samba PDC (3.0.21c with ldap backend). and another linux server used as
file server(samba 3.0.21c). . the users access the file shares using logon script
which redirects to respective shares in file server.
but when the logon script runs it gives the followin error
System error 121 has occurred.
The semaphore timeout period has expired.
I have a samba 3.0.21c with ldap backend acting as a PDC , i have about 100 users connectingto my domain.i have another linux system which acts as a file server (prjsrv01) where i have declared 2 shares.projects and datalib. The users get drives mapped with the help of logon
script. so i map projects share as P: drive
net use p: //prjsrv01/projects.
but whent the logon script runs the command. it says semaphore error.
The Domain Member Server uses lib_nss, to get user information from ldaps server
The following is the log level 10 output when the semaphore error occured. ie
the log starts when the user logs in and logon script runs.
when the semaphore error returns at windows client, at log it shows
Created attachment 1854 [details]
Debug Level 10 Output
Log Level 10 ouput when the user logs on the the domain
and logon script runs.
The log is taken from the domain member server ie my file server
the log file is generally username.machine.log.
The ouput is attached
It looks as if the logfile has prematurely ended. Do you have other logfiles for the guest user? Can you 'su -' to the user you set in 'guest account'?
Created attachment 1855 [details]
Debug Level 10 Output
This is another log, the log is of user dcadmin
logged in the machine name printsrv001.
it's not guest user.
Is it possible that you have winbind running and that winbind is haning for some reason? Could you try to issue 'wbinfo -t' on the command line and report the output? Could you also try to issue 'wbinfo -a domain\\user%password' on the command line and report the output? If that gives any problems, could you please also upload the winbind log files?
Created attachment 1862 [details]
Debug 10 Output
The NT_STATUS_IO_TIMEOUT comes from the communication with winbind. Could you please upload winbind logfiles from the operations that I mentioned?
severity should be determined by the developers and not the reporter.