Adding a little bit more detail:
It still happens with a just upgraded 3.0.9 install
The period of time appears to be 15 minutes (tested twice, connecting
every 30 seconds, 15 minutes both times) - until then, connections work
fine. After that, see below.
Here is the output from a debug level 3 smbclient connection:
$ smbclient -d 3 -L \\\\server_name -U user%pass
lp_load: refreshing parameters
Initialising global parameters
params.c:pm_process() - Processing configuration file
"/path/to/smb.conf"
Processing section "[global]"
added interface ip=XXX.XXX.XXX.XXX bcast=XXX.XXX.XXX.XXX nmask=255.255.255.0
Client started (version 3.0.9).
resolve_lmhosts: Attempting lmhosts lookup for name server_name<0x20>
resolve_wins: Attempting wins lookup for name server_name<0x20>
resolve_wins: using WINS server XXX.XXX.XXX.XXX and tag '*'
Got a positive name query response from XXX.XXX.XXX.XXX ( XXX.XXX.XXX.XXX )
Connecting to XXX.XXX.XXX.XXX at port 445
Doing spnego session setup (blob length=58)
got OID=1 3 6 1 4 1 311 2 2 10
got principal=NONE
Got challenge flags:
Got NTLMSSP neg_flags=0x60890215
NTLMSSP: Set final flags:
Got NTLMSSP neg_flags=0x60080215
NTLMSSP Sign/Seal - Initialising with flags:
Got NTLMSSP neg_flags=0x60080215
SPNEGO login failed: No logon servers
session setup failed: NT_STATUS_NO_LOGON_SERVERS
Bill Knox
Lead Operating Systems Programmer/Analyst
The MITRE Corporation
On Thu, 18 Nov 2004, William R. Knox wrote:
> Date: Thu, 18 Nov 2004 14:36:53 -0500 (EST)
> From: William R. Knox <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Subject: [Samba] Domain authentication failing after a period of time
>
> I am having an unusual bit of behavior with a recently upgraded 3.0.8
> installation (from 3.0.2a). I upgraded the server and retained the
> secrets.tdb file. The server itself is using security = domain, and it had
> been joined to the domain prior to the upgrade. Now, once I started the
> new version, I couldn't log on, and would get the error "There are no
> logon servers available to service the logon request". If I "rejoin" the
> domain (using the net join command), I can access the shares, but only for
> a period of time. After a few minutes (there doesn't seem to be a specific
> interval), that same message is returned. Running a smbclient -L against
> the system yields "session setup failed: NT_STATUS_NO_LOGON_SERVERS".
>
> I haven't tried failing back to 3.0.2a yet, but I will if that will help
> in any diagnoses.
>
> Thanks in advance for any help anyone may be able to give.
>
> Bill Knox
> Lead Operating Systems Programmer/Analyst
> The MITRE Corporation
> --
> To unsubscribe from this list go to the following URL and read the
> instructions: http://lists.samba.org/mailman/listinfo/samba
>
--
To unsubscribe from this list go to the following URL and read the
instructions: http://lists.samba.org/mailman/listinfo/samba
