Login problems - correct mail

Wed Dec 13 14:38:00 GMT 2000

Jorge -

Just thought I'd let you know you're not alone with this type of problem.
I have experienced this once on my network, and I am aware of seven other
users that have experienced it, ranging from "occasionally" to "all the
time".  Follow the thread "Login Troubles" first posted by Greg Ryle on
11/2/00.  Below is the original posting:

Greg Ryle wrote:
> I am running RedHat 6.2 with Samba 2.0.6 setup as a PDC doing domain
> logins. Users are experiencing difficulties logging in first thing in
> the morning after their machine has been shut down for the night.  If
> I change the Win98 machines so that they don't log into a NT domain,
> then they go in normally and can access the samba shares.  After they
> start accessing the shares, I can change the properties back to logging
> into an NT domain and it will log in.
>
> When the machines can't log in, the error I receive is that the password
> is not correct or access has been denied to the server.
>
> I tried redoing the passwords but that didn't work.
>
> Any suggestions,
>
> Greg

Global summary of the problem:
  Users report sporadic "Domain password not correct or access to domain
  server has been denied" messages at logon.  This problem may or may not
  go away after xx minutes.  This problem may go away after repeated
  attempts at logging on.  This problem happens for both Win9x and WinNTWS
  users.  For some sites, this problem always goes away immediately after
  changing any user password in smbpasswd.  Other services on the server
  (such as file access and printing for users already logged on) are
  functional during the time the problem is occurring.

Both Richard Sharpe and Gerald Carter had graciously responded to my
postings regarding this problem.  They wanted a network trace, verbose debug
logs and the output of smbstatus while the problem was occurring, but we
could not get the problem to repeat.  I referred them back to the other
users that were experiencing it regularly, and suggested that they may wish
to solicit the users on this list server for info from anybody/everybody
experiencing this problem, but have not seen anything else posted on this
issue since.

My current "guess" is that domain logons on Samba are exceptionally
sensitive to network communication problems, which can hang up the process
that authenticates users against smbpasswd.  I found that simply editing the
smbpasswd file made the problem go away immediately.  I had at least one
other user confirm that this also worked for him.  The users experiencing
this problem frequently admitted to having possible network communication
problems.

Hope this history helps.  I would expect that those responding to your
posting will be looking for detailed debug/error logs, a network trace and
output from "smbstatus" from when the problem was occurring, so you might
want to get started collecting info.

> -----Original Message-----
> From: samba-ntdom-admin at lists.samba.org
> [mailto:samba-ntdom-admin at lists.samba.org]On Behalf Of Ilender Linux
> Sent: Wednesday, December 13, 2000 8:45 AM
> To: samba-ntdom at lists.samba.org
> Subject: Login problems - correct mail
>
>
> Sorry people, I made a mistake copy - pasting my ifconfig last
> time... here is the correct IFCONFIG
> ______________
>
> Hello everybody.
>
> I use SAMBA 2.0.7 on Red Hat Linux 7.0 (with ALL the patches
> already installed) and clients in Windows 98 and Windows 98
> Second Edition.
>
> The problem I am having is that everyday, at the time the users
> come to work and turn on their machines, its almost impossible
> for them to login the domain. They receive "Bad Password" error
> about 14 to 20 times (I have counted them) until they can log in.
> After that, during the day, if someone restarts its computer, it
> logs at the first try. But if someone turns off his computer for
> a regular time or if the IP address is changed, the errors come back.
>
> I have read and tried different configuration and options, but
> none has worked.
>
> I will appreciate a lot if you help me, cause I don´t want
> Windows NT to work again as the PDC.
>
> Here I include my GLOBAL PARAMETERS and my IFCONFIG status.
>
> Thanks a lot for your help!
>
> Greetings
>
> Jorge Sarmiento
> Network Administrator
> Ilender Peru S.A.
> www.ilender.com.pe
>
>
> The [global] part of my smb.conf file I use is:
>
> [global]
>         workgroup = ILENDER_LINUX
>         netbios name = LINUX
>         server string = Samba Server
>         interfaces = eth2
>         encrypt passwords = Yes
>         log file = /var/log/samba/%m.log
>         max log size = 0
>         name resolve order = wins bcast lmhosts host
>         socket options = TCP_NODELAY SO_SNDBUF=16384 SO_RCVBUF=16384
>         logon script = login.bat
>         domain logons = Yes
>         os level = 65
>         preferred master = Yes
>         domain master = Yes
>         dns proxy = No
>         wins support = Yes
>         hosts allow = 172.16.4.
>
> my IFCONFIG status is:
>
> eth0      Link encap:Ethernet  HWaddr 00:10:5A:5D:63:C8
>           inet addr:216.244.146.194  Bcast:216.244.146.223
> Mask:255.255.255.224
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:419715 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:258698 errors:0 dropped:0 overruns:0 carrier:5
>           collisions:174 txqueuelen:100
>           Interrupt:10 Base address:0xcc00
>
> eth1      Link encap:Ethernet  HWaddr 00:10:5A:A0:BA:19
>           inet addr:192.168.1.10  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:30909 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:11248 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:4 txqueuelen:100
>           Interrupt:11 Base address:0xc800
>
> eth2      Link encap:Ethernet  HWaddr 00:D0:09:41:15:9B
>           inet addr:172.16.4.90  Bcast:172.16.4.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:810044 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:881412 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:100
>           Interrupt:11 Base address:0xc400
>
> lo        Link encap:Local Loopback
>           inet addr:127.0.0.1  Mask:255.0.0.0
>           UP LOOPBACK RUNNING  MTU:3924  Metric:1
>           RX packets:57544 errors:0 dropped:0 overruns:0 frame:0
>           TX packets:57544 errors:0 dropped:0 overruns:0 carrier:0
>           collisions:0 txqueuelen:0
>
>
>
>