Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

[Samba] Workgroup name too long

488 views
Skip to first unread message

dur...@mgtsciences.com

unread,
Feb 25, 2015, 4:40:06 PM2/25/15
to
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.

Servers are Fedora release 20 and 21, Samba versions are 4.1.12 and 15.

46856 Feb 25 13:22:19 zaphod nmbd[32208]: [2015/02/25 13:22:19.194541, 0]
../source3/nmbd/nmbd_workgroupdb.c:57(name_to_unstring)
46857 Feb 25 13:22:19 zaphod nmbd[32208]: name_to_nstring: workgroup name
PEGASUS ^[ is too long. Truncating to


Thank you,

Durwin F. De La Rue



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.
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba

Miguel Medalha

unread,
Feb 25, 2015, 4:50:04 PM2/25/15
to
> 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...

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.

Reindl Harald

unread,
Feb 25, 2015, 5:00:05 PM2/25/15
to


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
signature.asc

dur...@mgtsciences.com

unread,
Feb 25, 2015, 5:10:02 PM2/25/15
to
samba-...@lists.samba.org wrote on 02/25/2015 02:51:28 PM:

> From: Reindl Harald <h.re...@thelounge.net>
> To: sa...@lists.samba.org
> Date: 02/25/2015 02:52 PM
> Subject: Re: [Samba] Workgroup name too long
> Sent by: samba-...@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

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
>
>
> [attachment "signature.asc" deleted by Durwin De La Rue/Mgtsciences/US]
--
> To unsubscribe from this list go to the following URL and read the
> instructions: https://lists.samba.org/mailman/options/samba


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.

Miguel Medalha

unread,
Feb 25, 2015, 5:50:04 PM2/25/15
to

I suppose that the correct answer has been already given to you by Reindl
Harald.

https://bugzilla.redhat.com/show_bug.cgi?id=1175710#c10
0 new messages