No subject
Tue Dec 2 04:10:01 GMT 2003
the DC is a Windows box. Is that correct?
Here's the odd thing... The 1C name is a group name. It should not be
in conflict at all. The only way I know of (assuming that this is a
Windows/NT box) to cause the Conflict stat is for some other node to
send a directed "NAME CONFLICT DEMAND" or "NAME RELEASE REQUEST DEMAND"
to the node.
Can you scan your networks and look for the same name as a unique name?
That shouldn't be the problem but... If some other node is registering
DOMAIN<1C> as a unique name it could cause trouble.
Perhaps something else is going on. The handling of #1C names is very
strange. The WINS server is supposed to list all of the IP addresses
(up to 25 of them) of the DOMAIN<1C> name, but it is also supposed to
force the IP address of the DOMAIN<1B> name to the top of the #1C IP
list. [Goofy as all getout, but that's how you identify the PDC from
the list of IPs in the #1C entry. Yes, really. Geez.]
Anyway, if anything is messed up in the WINS database, or if some node
is sending out bogus "NAME CONFLICT DEMAND" or "NAME RELEASE REQUEST
DEMAND" messages, or if there is a conflicting #1C unique name... then
you would get the conflict status.
Chris -)-----
Andrew Esh wrote:
>
> What causes this conflict condition in the PDC #1c nmblookup info?
> This causes Samba not to be able to authenticate with the given
> domain controller. Of course, if the smb.conf "password server"
> parameter has another (good) DC listed, we get past this, but it
> kills Samba in single-DC environments. I've seen this twice in the
> last three weeks, in two unrelated domains. If the DC is rebooted,
> the conflict goes away, and Samba can authenticate again.
>
> (NetBIOS Names and IPs changed to protect the innocent, but the
> output is real.)
>
> # nmblookup -A 2.4.6.8
>
> Local Area Connection:
> Node IpAddress: [2.4.6.8] Scope Id: []
>
> NetBIOS Remote Machine Name Table
>
> Name Type Status
> ---------------------------------------------
> DC <00> UNIQUE Registered
> DC <20> UNIQUE Registered
> DOMAIN <00> GROUP Registered
> DOMAIN <1C> GROUP Conflict
> DOMAIN <1B> UNIQUE Registered
> DOMAIN <1E> GROUP Registered
> DC <03> UNIQUE Registered
> DOMAIN <1D> UNIQUE Registered
> ..__MSBROWSE__.<01> GROUP Registered
>
> MAC Address = 00-01-02-03-04-05
>
> --
> Andrew C. Esh mail:Andrew.Esh at tricord.com
> Tricord Systems, Inc.
> 2905 Northwest Blvd., Suite 20 763-557-9005 (main)
> Plymouth, MN 55441-2644 USA 763-551-6418 (direct)
> http://www.tricord.com - Tricord Home Page
--
Christopher R. Hertel -)----- University of Minnesota
crh at nts.umn.edu Networking and Telecommunications Services
------_=_NextPart_001_01C1E4AF.EC81B120
Content-Type: text/html;
charset="iso-8859-1"
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
<META NAME="Generator" CONTENT="MS Exchange Server version 5.5.2650.12">
<TITLE>RE: nmblookup conflict</TITLE>
</HEAD>
<BODY>
<P><FONT SIZE=2>Yes, the DC is Windows. NT in one case. Not sure about the one that produced this (sanitized) output.</FONT>
</P>
<P><FONT SIZE=2>-----Original Message-----</FONT>
<BR><FONT SIZE=2>From: Christopher R. Hertel [<A HREF="mailto:crh at umn.edu">mailto:crh at umn.edu</A>]</FONT>
<BR><FONT SIZE=2>Sent: Monday, April 15, 2002 1:49 PM</FONT>
<BR><FONT SIZE=2>To: aesh at tricord.com</FONT>
<BR><FONT SIZE=2>Cc: samba-technical at lists.samba.org</FONT>
<BR><FONT SIZE=2>Subject: Re: nmblookup conflict</FONT>
</P>
<BR>
<P><FONT SIZE=2>From the output (because the MAC address is given) it looks as though</FONT>
<BR><FONT SIZE=2>the DC is a Windows box. Is that correct?</FONT>
</P>
<P><FONT SIZE=2>Here's the odd thing... The 1C name is a group name. It should not be</FONT>
<BR><FONT SIZE=2>in conflict at all. The only way I know of (assuming that this is a</FONT>
<BR><FONT SIZE=2>Windows/NT box) to cause the Conflict stat is for some other node to</FONT>
<BR><FONT SIZE=2>send a directed "NAME CONFLICT DEMAND" or "NAME RELEASE REQUEST DEMAND"</FONT>
<BR><FONT SIZE=2>to the node.</FONT>
</P>
<P><FONT SIZE=2>Can you scan your networks and look for the same name as a unique name?</FONT>
<BR><FONT SIZE=2>That shouldn't be the problem but... If some other node is registering</FONT>
<BR><FONT SIZE=2>DOMAIN<1C> as a unique name it could cause trouble.</FONT>
</P>
<P><FONT SIZE=2>Perhaps something else is going on. The handling of #1C names is very</FONT>
<BR><FONT SIZE=2>strange. The WINS server is supposed to list all of the IP addresses</FONT>
<BR><FONT SIZE=2>(up to 25 of them) of the DOMAIN<1C> name, but it is also supposed to</FONT>
<BR><FONT SIZE=2>force the IP address of the DOMAIN<1B> name to the top of the #1C IP</FONT>
<BR><FONT SIZE=2>list. [Goofy as all getout, but that's how you identify the PDC from</FONT>
<BR><FONT SIZE=2>the list of IPs in the #1C entry. Yes, really. Geez.]</FONT>
</P>
<P><FONT SIZE=2>Anyway, if anything is messed up in the WINS database, or if some node</FONT>
<BR><FONT SIZE=2>is sending out bogus "NAME CONFLICT DEMAND" or "NAME RELEASE REQUEST</FONT>
<BR><FONT SIZE=2>DEMAND" messages, or if there is a conflicting #1C unique name... then</FONT>
<BR><FONT SIZE=2>you would get the conflict status.</FONT>
</P>
<P><FONT SIZE=2>Chris -)-----</FONT>
</P>
<P><FONT SIZE=2>Andrew Esh wrote:</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> What causes this conflict condition in the PDC #1c nmblookup info?</FONT>
<BR><FONT SIZE=2>> This causes Samba not to be able to authenticate with the given</FONT>
<BR><FONT SIZE=2>> domain controller. Of course, if the smb.conf "password server"</FONT>
<BR><FONT SIZE=2>> parameter has another (good) DC listed, we get past this, but it</FONT>
<BR><FONT SIZE=2>> kills Samba in single-DC environments. I've seen this twice in the</FONT>
<BR><FONT SIZE=2>> last three weeks, in two unrelated domains. If the DC is rebooted,</FONT>
<BR><FONT SIZE=2>> the conflict goes away, and Samba can authenticate again.</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> (NetBIOS Names and IPs changed to protect the innocent, but the</FONT>
<BR><FONT SIZE=2>> output is real.)</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> # nmblookup -A 2.4.6.8</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Local Area Connection:</FONT>
<BR><FONT SIZE=2>> Node IpAddress: [2.4.6.8] Scope Id: []</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> NetBIOS Remote Machine Name Table</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> Name Type Status</FONT>
<BR><FONT SIZE=2>> ---------------------------------------------</FONT>
<BR><FONT SIZE=2>> DC <00> UNIQUE Registered</FONT>
<BR><FONT SIZE=2>> DC <20> UNIQUE Registered</FONT>
<BR><FONT SIZE=2>> DOMAIN <00> GROUP Registered</FONT>
<BR><FONT SIZE=2>> DOMAIN <1C> GROUP Conflict</FONT>
<BR><FONT SIZE=2>> DOMAIN <1B> UNIQUE Registered</FONT>
<BR><FONT SIZE=2>> DOMAIN <1E> GROUP Registered</FONT>
<BR><FONT SIZE=2>> DC <03> UNIQUE Registered</FONT>
<BR><FONT SIZE=2>> DOMAIN <1D> UNIQUE Registered</FONT>
<BR><FONT SIZE=2>> ..__MSBROWSE__.<01> GROUP Registered</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> MAC Address = 00-01-02-03-04-05</FONT>
<BR><FONT SIZE=2>> </FONT>
<BR><FONT SIZE=2>> --</FONT>
<BR><FONT SIZE=2>> Andrew C. Esh mail:Andrew.Esh at tricord.com</FONT>
<BR><FONT SIZE=2>> Tricord Systems, Inc.</FONT>
<BR><FONT SIZE=2>> 2905 Northwest Blvd., Suite 20 763-557-9005 (main)</FONT>
<BR><FONT SIZE=2>> Plymouth, MN 55441-2644 USA 763-551-6418 (direct)</FONT>
<BR><FONT SIZE=2>> <A HREF="http://www.tricord.com" TARGET="_blank">http://www.tricord.com</A> - Tricord Home Page</FONT>
</P>
<P><FONT SIZE=2>-- </FONT>
<BR><FONT SIZE=2>Christopher R. Hertel -)----- University of Minnesota</FONT>
<BR><FONT SIZE=2>crh at nts.umn.edu Networking and Telecommunications Services</FONT>
</P>
</BODY>
</HTML>
------_=_NextPart_001_01C1E4AF.EC81B120--
More information about the samba-technical
mailing list