[Samba] Workgroup name too long

[durwin at mgtsciences.com]

> From: schulz at adi.com (Thomas Schulz)
> To: durwin at mgtsciences.com, h.reindl at thelounge.net, 
samba at lists.samba.org
> Date: 02/26/2015 11:38 AM
> Subject: Re: [Samba] Workgroup name too long
> 
> >> From: schulz at adi.com (Thomas Schulz)
> >> To: durwin at mgtsciences.com, h.reindl at thelounge.net, 
> > samba at lists.samba.org
> >> Date: 02/25/2015 06:39 PM
> >> Subject: Re: [Samba] Workgroup name too long
> >> Sent by: samba-bounces at lists.samba.org
> >> 
> >>>> From: Reindl Harald <h.reindl at thelounge.net>
> >>>> To: samba at lists.samba.org
> >>>> Date: 02/25/2015 02:52 PM
> >>>> Subject: Re: [Samba] Workgroup name too long
> >>>> Sent by: samba-bounces at lists.samba.org
> >>>> 
> >>>> 
> >>>> 
> >>>> Am 25.02.2015 um 22:48 schrieb Miguel Medalha:
> >>>>>> I have searched for this and the solutions I found were for 
> > instances
> >>>>>> where the workgroup name *was* too long.  However, my workgroup 
> > name 
> >>> is
> >>>>>> *not* too long.  The spaces between PEGASUS and ^[ are part of 
the
> >>>>>> message, I did not add them.  If you count them there are 16 
total
> >>>>>> including ending ^[.  I can't figure out where the spaces are 
> > coming
> >>>>> from.
> >>>>>>   This is the same for every Samba server.  Each machine will 
show 
> >>> this
> >>>>>> message for the other servers but not itself.  MachineA will show 

> >>> message
> >>>>>> for B and C, but not A.  MachineB will show message for A and C 
but 
> > 
> >>> not B.
> >>>>>
> >>>>> I can count 17 characters...
> >>>> 
> >>>> here you go:
> >>>> https://bugzilla.redhat.com/show_bug.cgi?id=1175710#c10
> >>> 
> >>> I understand the limit is 15.  However, in the case I included, the 
> > count 
> >>> is only 7.
> >>> I did *not* add the spaces nor the ending character (I assume it is 
> > some 
> >>> control
> >>> character).  The line below is straight from smb.conf
> >>> 
> >>> workgroup = pegasus
> >> 
> >> 
> >> I wonder if perhaps there is a control character at the end of that 
line
> >> that does not show up if you print it out. Try deleting that line and 

> > then
> >> typing it back in.
> > 
> > Just a note.  Using 'tail' on the log shows the name ending with an 
's'.
> > Using 'vi -b' on log file shows name ending with '^['.
> 
> 
> Generally when you see something like '^[' that means the control 
character
> you get when you hold down the control key and hit '['.  Now '^[' is the
> escape key. That sounds very suspisious. Someone might accidentally get
> that into a file if they were used to using vi and were editing with
> a different editor. Perhaps use 'vi -b' on the config file and look
> everywhere for a '^['.
> 
> Did the version of Samba you are using come with the operating system or
> did you build it yourself from source?

Thank you.  I did look at smb.conf for any control characters (with vi 
-b).
There were none.  I also deleted 'to-end-of-line' and reentered name. 
Still
no effect.  This issue is with all four Linux machines.  Three are Fedora 
21,
one is Fedora 20.  The version of Samba is what came with the 
distribution.


> 
> 
> > 
> >> 
> >>> All the machines I am referring to are Fedora.
> >>> 
> >>> Thank you.
> >>> 
> >>>> 
> >>>>> According to Microsoft:
> >>>>>
> >>>>> "The NetBIOS naming convention allows for 16 characters in a 
NetBIOS 
> > 
> >>> name.
> >>>>> Microsoft, however, limits NetBIOS names to 15 characters and uses 

> > the
> >>>>> 16th character as a NetBIOS suffix. "
> >>>>>
> >>>>> and
> >>>>>
> >>>>> "All NetBIOS names are 16 characters in length. A NetBIOS suffix 
is 
> >>> the
> >>>>> 16th character of the 16-character NetBIOS name. The NetBIOS 
suffix 
> > is
> >>>>> used by Microsoft Networking software to identify functionality 
> >>> installed
> >>>>> on the registered device. "
> >>>>>
> >>>>> http://support.microsoft.com/kb/163409
> >>>>>
> >>>>> Names are padded with spaces to 15 bytes, plus the NetBIOS suffix 
in 
> > 
> >>> the
> >>>>> 16th byte
> 
> Tom Schulz
> Applied Dynamics Intl.
> schulz at adi.com



This email message and any attachments are for the sole use of the 
intended recipient(s) and may contain proprietary and/or confidential 
information which may be privileged or otherwise protected from 
disclosure. Any unauthorized review, use, disclosure or distribution is 
prohibited. If you are not the intended recipient(s), please contact the 
sender by reply email and destroy the original message and any copies of 
the message as well as any attachments to the original message.