Server name being truncated in Winbindd

chuckg at lexmark.com chuckg at lexmark.com
Thu Sep 26 18:15:59 GMT 2002


Well it is the W2k DC that has the 15 character name, not the client.... I
am attempting to join a Samba 3.0 client to a
w2k DC with a 15 character name... True it's not probably winbindd per se,
it just happens that I am using the "net rpc join" and winbindd to validate
users...  Thanks,

Chuck



Richard Sharpe <rsharpe at ns.aus.com> on 09/26/2002 02:50:41 PM

To:    <chuckg at lexmark.com>
cc:    <samba-technical at lists.samba.org>
Subject:    Re: Server name being truncated in Winbindd


On Thu, 26 Sep 2002 chuckg at lexmark.com wrote:

> I am runing Samba-3.0-alpha18 winbindd and attempting to join a w2k
domain
> that has a
> 15 character server name.. as you can see from the log below the name
gets
> truncated to 14 characters which then results in the
NT_STATUS_INVALID_COMPUTER_NAME
> when attempting authentication....I am not at work to look at the code
but I did notice
> the message from  convert_string() about requiring 16 character and only
15 being available..
> This works fine if the domain name is less than 15 characters...

Hmmm, I am not sure that winbindd is the culprit here.

In any case, NetBIOS names are resricted to 15 characters. Always have
been. The 16th character has always been the type char, since 1984 when
IBM defined the protocol.

When joining a domain, the client joining needs an account on the server
with a $ on the end. This accounts for the 14-char restriction.

The question is, do Windows PDCs allow clients with 15-char names to join?

If they do, then Samba should re-examine the decision. If they don't, then
you will have to reduce the length of the name.

> Has anyone else seen this and have a fix?  Thanks in advance,
>
> Chuck Grieshaber
>
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   L0001-EXK0001-M#00: flags = 0x44
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   MAST_EXDC#00: flags = 0xc4
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   MAST_EXDC#1c: flags = 0xc4
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   L0001-EXK0001-M#20: flags = 0x44
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   MAST_EXDC#1b: flags = 0x44
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   MAST_EXDC#1e: flags = 0xc4
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)
>   L0001-EXK0001-M#03: flags = 0x44
> [2002/09/25 10:29:05, 10] libsmb/namequery.c:parse_node_status(67)

--
Regards
-----
Richard Sharpe, rsharpe at ns.aus.com, rsharpe at samba.org,
sharpe at ethereal.com









More information about the samba-technical mailing list