samba - Oct 2000 - Password must be entered multiple times / nmbd has to be restarted

I searched the archives, but I couldn't find solutions to these two
problems:

1. Sometimes, users will enter their correct password during login from
Windows 95 and receive the following error "Domain password is not
correct or access to your login has been denied".  After the error, they
return to the login dialog and press enter again (without changing the
password).  This time it lets them in.  It's not fatal but its very
annoying.  It seems like some kind of timeout problem but I can't see
anything in the configuration.

2. We have a central WINS server and five other Samba servers that get
their WINS info from the central one.  Periodically, the central WINS
server will lose information about the IP of one of the other servers. 
Eventually, it would lose it for all of them.  I then have to go to that
other server and restart nmbd.  At that point, the central server
relearns the IP address.  During the time the IP is not know by the main
WINS server, users from other subnets can't browse that Samba server. 
I'm still confused by WINS, so I'm not sure what kind of circumstances
could cause this to happen.  Do WINS entries expire?

Any help on these would be greating appreciated.
--
Dave Brodin
Lead Systems Engineer
Information and Technology Services
City of Bloomington

I searched the archives, but I couldn't find solutions to these two
problems:

1. Sometimes, users will enter their correct password during login from
Windows 95 and receive the following error "Domain password is not
correct or access to your login has been denied".  After the error, they
return to the login dialog and press enter again (without changing the
password).  This time it lets them in.  It's not fatal but its very
annoying.  It seems like some kind of timeout problem but I can't see
anything in the configuration.

I had this problem and traced it back to a reverse DNS lookup timeout. After
I put entries for our subnets in /etc/hosts, everything worked fine. Sorry,
no idea with the wins problems...

Dave,
I reported issues about Samba names dropping out of WINS about a year
ago to the mailing list (I was then using 2.0.4b). Other than a few "Me,
too!" responses, there didn't seem to be a solution. I couldn't
decide
if the issue was due to crummy networking, our whacko NT setup here, or
something in samba. I have taken to restarting my samba processes every
night both to avoid this issue and to keep my smbd processes from
growing to large due to an apparent memory leak in the printing
subsystem in 2.0.7.

So I guess this makes me one of the "Me, too!" responses now. ;-)
Sorry
I don't have anything more helpful to contribute.
-- 
			Bill Knox
			Senior Operating Systems Programmer/Analyst
			The MITRE Corporation

Dave Brodin wrote:
> 
> I searched the archives, but I couldn't find solutions to these two
> problems:
> 
[first problem skipped]
> 
> 2. We have a central WINS server and five other Samba servers that get
> their WINS info from the central one.  Periodically, the central WINS
> server will lose information about the IP of one of the other servers.
> Eventually, it would lose it for all of them.  I then have to go to that
> other server and restart nmbd.  At that point, the central server
> relearns the IP address.  During the time the IP is not know by the main
> WINS server, users from other subnets can't browse that Samba server.
> I'm still confused by WINS, so I'm not sure what kind of
circumstances
> could cause this to happen.  Do WINS entries expire?
> 
> Any help on these would be greating appreciated.
> --
> Dave Brodin
> Lead Systems Engineer
> Information and Technology Services
> City of Bloomington