Christopher R. Hertel
crh at umn.edu
Tue Apr 16 09:35:01 GMT 2002
If that is the problem, then it's still important to know which box is
causing the NAME RELEASE REQUEST DEMAND message to be sent, and why.
There should not be any unique <DOMAIN>#1C unique names on your
network. If there are, then there is a misconfiguration somewhere.
Note that it would only be a unique name that would cause the conflict
(and it would be a third-party node that would send the RELEASE
I wonder if the receipt of the RELEASE message is listed in any logs
(does Windows have logs?).
NBT is a bowl full of jelly beans...Jalapeño and Kerosene flavor.
> "Esh, Andrew" wrote:
> Thanks Volker! The Google search worked. Here's what I found after
> some tunneling:
> -----Original Message-----
> From: Volker Lendecke [mailto:Volker.Lendecke at SerNet.DE]
> Sent: Tuesday, April 16, 2002 8:28 AM
> To: Christopher R. Hertel
> Cc: Esh, Andrew; samba-technical at lists.samba.org
> Subject: Re: nmblookup conflict
> On Mon, Apr 15, 2002 at 02:09:58PM -0500, Christopher R. Hertel
> > IIRC, NT will go into the Conflict state if it gets a "NAME RELEASE
> > REQUEST DEMAND". See my docs:
> > Look for the string "NAME RELEASE REQUEST DEMAND". It is really
> > easy to
> > code this up and send it as a unicast. I think that NT is immune
> > to the "NAME CONFLICT DEMAND", but you might want to check.
> There's a NT Patch against this problem. You can patch NT to ignore
> Look for 'netbios conflict' or so in google/msdn etc. I found it
> quite quickly once.
Christopher R. Hertel -)----- University of Minnesota
crh at nts.umn.edu Networking and Telecommunications Services
More information about the samba-technical