This morning a lot of the machines on the network can't logon to the domain, it's Win2K clients, and it can be solved by removing the machine and joining it to the domain again, and this is a lot of work as it has to be done on the clients individually....why are the machines being removed from the domain ? I hope you have a solution that keeps me from walking around from machine to machine! It started on 3.0.7 - and I just upgraded to 3.0.10 and the problem persists.
There's not enough information here to even guess at what the issue is in your environment. Password expiration perhaps ?
(In reply to comment #1) > There's not enough information here to even guess at what > the issue is in your environment. Password expiration > perhaps ? The users are created on the Samba server - how do I see expiration dates?
pdbedit -v loginName
(In reply to comment #3) > pdbedit -v loginName maggie root # pdbedit -v pleslie Unix username: pleslie NT username: Account Flags: [U ] User SID: S-1-5-21-2545196088-1598065383-3250250138-3000 Primary Group SID: S-1-5-21-2545196088-1598065383-3250250138-1201 Full Name: Home Directory: \\maggie\pleslie HomeDir Drive: Logon Script: pleslie.bat Profile Path: \\maggie\profiles\pleslie Domain: MYGROUP Account desc: Workstations: Munged dial: Logon time: 0 Logoff time: Fri, 13 Dec 1901 21:45:51 GMT Kickoff time: Fri, 13 Dec 1901 21:45:51 GMT Password last set: Wed, 03 Nov 2004 15:34:10 GMT Password can change: Wed, 03 Nov 2004 15:34:10 GMT Password must change: Fri, 13 Dec 1901 21:45:51 GMT Last bad password : 0 Bad password count : 0 Logon hours : FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF maggie root # ....does it make sense?
severity should be determined by the developers and not the reporter.
Cleaning up . Please reopen if the problem still exists in a current Samba release.