Disruption to Domain Controller by Samba

[Herb Lewis]

Marc Cosgrove wrote:
> 
> 
> Before:
> 
> 33             <20>  UNIQUE      192.168.102.33      480
> SCADIS         <03>  UNIQUE      192.168.102.48      -1
> SCADIS         <00>  UNIQUE      192.168.102.48      -1
> SCADIS         <20>  UNIQUE      192.168.102.48      -1
> workgroup      <1C>  UNIQUE      192.168.102.48      -1
> workgroup      <1B>  UNIQUE      192.168.102.48      -1
> 
> During:
> 
> SCADIS#19388   <20>  UNIQUE      192.168.102.48      120
> 33             <20>  UNIQUE      192.168.102.33      480
> SCADIS         <03>  UNIQUE      192.168.102.48      -1
> SCADIS         <00>  UNIQUE      192.168.102.48      -1
> SCADIS         <20>  UNIQUE      192.168.102.48      -1
> WORKGROUP      <1C>  GROUP       192.168.102.48      660
> workgroup      <1C>  UNIQUE      192.168.102.48      -1
> workgroup      <1B>  UNIQUE      192.168.102.48      -1
> 

This looks like a SCO problem not a samba problem. The <1c> name
is supposed to be a group name not a unique name. All the NT systems
I looked at here also register this as a group name just like samba.

-- 
======================================================================
Herb Lewis                                   Silicon Graphics 
Networking Engineer                          2011 N Shoreline Blvd
Strategic Software Organization              Mountain View, CA  94043  
herb at sgi.com                                 Tel: 650-933-2177
http://www.sgi.com                           Fax: 650-932-2177          
======================================================================