samba - Jun 2000 - Odd WINS Problem

I've been having an odd problem with nmbd and WINS.  We have two WINS
servers running on NT4.0, and eight solaris machines running samba (2.0.7).
Every so often, it appears that WINS loses its db entry for the samba
machines.  If I stop and restart nmbd, the samba machine reregisters with
WINS and all is good.  The problem is very sporadic, and doesn't seem to
affect all of the machines.  

We've seen this problem since around the 2.0.4 days.  We upgrade with each
release hoping to fix the problem.

Any ideas?

Thanks,

--Brian

On Fri, 23 Jun 2000, Vogle, Brian wrote:
> I've been having an odd problem with nmbd and WINS.  We have two WINS
> servers running on NT4.0, and eight solaris machines running samba (2.0.7).
> Every so often, it appears that WINS loses its db entry for the samba
> machines.  If I stop and restart nmbd, the samba machine reregisters with
> WINS and all is good.  The problem is very sporadic, and doesn't seem
to
> affect all of the machines.  
> 
> We've seen this problem since around the 2.0.4 days.  We upgrade with
each
> release hoping to fix the problem.
I'd like to second this report.  We had exactly this problem happen with a
linux server running 2.0.6.  We couldn't see anything unusual in the logs
on either the samba machine or the WINS server.  This has only happened to
us once.

	Andy

Hello,

I am afraid this is not a solution to this problem. We are having the same
problem on our Solaris boxes. It doesn't seem to happen on Linux. Is this a
bug?

Regards

Dave

-----Original Message-----
From: Vogle, Brian [mailto:Brian.Vogle@Williams.com]
Sent: 23 June 2000 14:36
To: Multiple recipients of list SAMBA
Subject: Odd WINS Problem


I've been having an odd problem with nmbd and WINS.  We have two WINS
servers running on NT4.0, and eight solaris machines running samba (2.0.7).
Every so often, it appears that WINS loses its db entry for the samba
machines.  If I stop and restart nmbd, the samba machine reregisters with
WINS and all is good.  The problem is very sporadic, and doesn't seem to
affect all of the machines.  

We've seen this problem since around the 2.0.4 days.  We upgrade with each
release hoping to fix the problem.

Any ideas?

Thanks,

--Brian



CONFIDENTIALITY NOTICE 
The information contained in this e-mail is intended only for the
confidential use of the above named recipient. If you are not the intended
recipient or person responsible for delivering it to the intended recipient,
you have received this communication in error and must not distribute or
copy it.  Please accept the sender's apologies, notify the sender
immediately by return e-mail and delete this communication.  Thank you.