samba - Mar 2002 - occassionally : no domain controller available

I'm using samba 2.2.3a as fileserver and domaincontroller for 12
NT4-clients (sp6a) and occassionally - when a user tries to logon -
there comes the following messages on the nt-client:
-
No Windows NT Domain Controller is available for domain XXXX. There are
currently no logonservers available to service the logonrequest.
-
and
-
server-side profile not available. The OS tries to log you on with
your local profile.
-

There is no visible pattern when this error occures. Sometime no
machine has this error at all in the morning, sometimes 3 or 4 and
sometimes only 1 machine. The error is also not related to the
peaktime in the morning.

I run several very similar samba-installations and I never ran into
such a problem. After the user is logged on (with its local profile)
he can access the server as fileserver without any problems.

I currently work with debug-level 3 and cant find the problem. (There
are some errors in the log of course, but the very same errors occures
on different machines with no such problems this day).  The client
just seems not to access the roaming profile. There is no access to
NTUSER.DAT for example, so the problem seems to happen before.  I
compared logfiles which a successful logon and a "failed" logon and
just cant figure out the problem ..

there are almost certainly no networktroubles and I reapplied sp6a to
all clients and I also removed and readded affected clients from and
to the domain again without any help ...

I put the logfiles of one client where this problems happend today at
9:30 together with the serverlog and my smb.conf in a tgz-file at
http://www.goldfisch.at/temp/smb.tgz

The problem happened at 9:30 when user "elisabeth" tried to logon and
client and server are in sync for their systemtime.

maybe anyone can help me here. feel kinda doomed ...

thnx,
peter

I had some really weird problems just like this for a while, and finally figured
out by accident (our acocuntant was late coming in) that everything worked fine
until a few seconds after she turned her computer on.  It was apparently a bad
NIC, although it worked fine with a Win2K server - go figure...

Don't know if this is your problem, but...

Charles
> -----Original Message-----
> From: samba-admin@lists.samba.org 
> [mailto:samba-admin@lists.samba.org]On
> Behalf Of pilsl@goldfisch.at
> Sent: Thursday, March 14, 2002 5:03 AM
> To: samba@lists.samba.org
> Subject: [Samba] occassionally : no domain controller available
> 
> 
> I'm using samba 2.2.3a as fileserver and domaincontroller for 12
> NT4-clients (sp6a) and occassionally - when a user tries to logon -
> there comes the following messages on the nt-client:
> -
> No Windows NT Domain Controller is available for domain XXXX. 
> There are
> currently no logonservers available to service the logonrequest.
> -
> and
> -
> server-side profile not available. The OS tries to log you on with
> your local profile.
> -
> 
> There is no visible pattern when this error occures. Sometime no
> machine has this error at all in the morning, sometimes 3 or 4 and
> sometimes only 1 machine. The error is also not related to the
> peaktime in the morning.
> 
> I run several very similar samba-installations and I never ran into
> such a problem. After the user is logged on (with its local profile)
> he can access the server as fileserver without any problems.
> 
> I currently work with debug-level 3 and cant find the problem. (There
> are some errors in the log of course, but the very same errors occures
> on different machines with no such problems this day).  The client
> just seems not to access the roaming profile. There is no access to
> NTUSER.DAT for example, so the problem seems to happen before.  I
> compared logfiles which a successful logon and a "failed" logon
and
> just cant figure out the problem ..
> 
> there are almost certainly no networktroubles and I reapplied sp6a to
> all clients and I also removed and readded affected clients from and
> to the domain again without any help ...
> 
> I put the logfiles of one client where this problems happend today at
> 9:30 together with the serverlog and my smb.conf in a tgz-file at
> http://www.goldfisch.at/temp/smb.tgz
> 
> The problem happened at 9:30 when user "elisabeth" tried to logon
and
> client and server are in sync for their systemtime.
> 
> maybe anyone can help me here. feel kinda doomed ...
> 
> thnx,
> peter
> 
> 
> 
> -- 
> To unsubscribe from this list go to the following URL and read the
> instructions:  http://lists.samba.org/mailman/listinfo/samba

Hi Peter,

I am also using Samba 2.2.3a as a domain controller, but for a larger 
network. I have two such installations and have noticed similar things on 
both installations. There is nothing obvious in the log files and the 
error is only with domain logons, ie file access is not a problem.

Restarting the samba service seems to clear it all up and it works 
perfectly for a few days. I have only seen this since I have upgraded from 
2.2.2

Regards,

Joshua Marshall





pilsl@goldfisch.at
Sent by: samba-admin@lists.samba.org
14/03/2002 08:03 PM

 
        To:     samba@lists.samba.org
        cc: 
        Subject:        [Samba] occassionally : no domain controller available


I'm using samba 2.2.3a as fileserver and domaincontroller for 12
NT4-clients (sp6a) and occassionally - when a user tries to logon -
there comes the following messages on the nt-client:
-
No Windows NT Domain Controller is available for domain XXXX. There are
currently no logonservers available to service the logonrequest.
-
and
-
server-side profile not available. The OS tries to log you on with
your local profile.
-

There is no visible pattern when this error occures. Sometime no
machine has this error at all in the morning, sometimes 3 or 4 and
sometimes only 1 machine. The error is also not related to the
peaktime in the morning.

I run several very similar samba-installations and I never ran into
such a problem. After the user is logged on (with its local profile)
he can access the server as fileserver without any problems.

I currently work with debug-level 3 and cant find the problem. (There
are some errors in the log of course, but the very same errors occures
on different machines with no such problems this day).  The client
just seems not to access the roaming profile. There is no access to
NTUSER.DAT for example, so the problem seems to happen before.  I
compared logfiles which a successful logon and a "failed" logon and
just cant figure out the problem ..

there are almost certainly no networktroubles and I reapplied sp6a to
all clients and I also removed and readded affected clients from and
to the domain again without any help ...

I put the logfiles of one client where this problems happend today at
9:30 together with the serverlog and my smb.conf in a tgz-file at
http://www.goldfisch.at/temp/smb.tgz

The problem happened at 9:30 when user "elisabeth" tried to logon and
client and server are in sync for their systemtime.

maybe anyone can help me here. feel kinda doomed ...

thnx,
peter



-- 
To unsubscribe from this list go to the following URL and read the
instructions:  http://lists.samba.org/mailman/listinfo/samba