All, I came into work to find a strange problem today: The shares on a Samba server were no longer accessible. After working on it for a while, I finally turned up logging and found the following in the client connection logs: [2019/01/14 14:59:21.384622, 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step) gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER [2019/01/14 14:59:21.396728, 2] ../auth/ntlmssp/ntlmssp.c:119(gensec_ntlmssp_update_find) Failed to parse NTLMSSP packet: zero length [2019/01/14 14:59:21.396777, 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step) gensec_spnego_server_negTokenInit_step: ntlmssp: parsing NEG_TOKEN_INIT content failed (next[(null)]): NT_STATUS_INVALID_PARAMETER Windows clients claim they can’t find a path to the server/share, and Mac clients just don’t work. The server has been running since mid-December with no updates, no reboots and no issues. SSSD (ssh authorization to AD) logins are working fine, and interestingly enough, smbclient seems to be able to connect without difficulty. So why can’t my Windows and Mac clients connect? Thank you for the help, -- Jason Lewis Senior Systems Engineer @ Micro Electronics, Inc. E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>
On Mon, 14 Jan 2019 20:11:15 +0000 "Jason W. Lewis via samba" <samba at lists.samba.org> wrote:> All, > I came into work to find a strange problem today: The shares on a > Samba server were no longer accessible. After working on it for a > while, I finally turned up logging and found the following in the > client connection logs: > > [2019/01/14 14:59:21.384622, > 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step) > gensec_spnego_server_negTokenInit_step: ntlmssp: parsing > NEG_TOKEN_INIT content failed (next[(null)]): > NT_STATUS_INVALID_PARAMETER [2019/01/14 14:59:21.396728, > 2] ../auth/ntlmssp/ntlmssp.c:119(gensec_ntlmssp_update_find) Failed > to parse NTLMSSP packet: zero length [2019/01/14 14:59:21.396777, > 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step) > gensec_spnego_server_negTokenInit_step: ntlmssp: parsing > NEG_TOKEN_INIT content failed (next[(null)]): > NT_STATUS_INVALID_PARAMETER > > Windows clients claim they can’t find a path to the server/share, and > Mac clients just don’t work. The server has been running since > mid-December with no updates, no reboots and no issues. SSSD (ssh > authorization to AD) logins are working fine, and interestingly > enough, smbclient seems to be able to connect without difficulty. So > why can’t my Windows and Mac clients connect? > > Thank you for the help, > -- > Jason Lewis > Senior Systems Engineer @ Micro Electronics, Inc. > E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com> >Have you tried restarting Samba ? What OS ? How are you running Samba ? I know you say nothing has changed on the Samba server, but has anything changed externally ? New router or windows updates etc ? Rowland
Rowland,
Thanks for getting back with me. Fortunately, I was able to fix the problem. I
started noticing bits in some of the messages coming off Samba that it
wasn't in a domain, or at least I didn't think so. It looks like
another admin may have removed domain info from smb.conf. Putting that in got
the server working again.
--
Jason Lewis
Senior Systems Engineer @ Micro Electronics, Inc.
E: jwlewis at microcenter.com
On 1/14/19, 3:36 PM, "samba on behalf of Rowland Penny via samba"
<samba-bounces at lists.samba.org on behalf of samba at lists.samba.org>
wrote:
External email – Please make sure you trust the source before clicking links
or opening attachments.
On Mon, 14 Jan 2019 20:11:15 +0000
"Jason W. Lewis via samba" <samba at lists.samba.org> wrote:
> All,
> I came into work to find a strange problem today: The shares on a
> Samba server were no longer accessible. After working on it for a
> while, I finally turned up logging and found the following in the
> client connection logs:
>
> [2019/01/14 14:59:21.384622,
> 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
> gensec_spnego_server_negTokenInit_step: ntlmssp: parsing
> NEG_TOKEN_INIT content failed (next[(null)]):
> NT_STATUS_INVALID_PARAMETER [2019/01/14 14:59:21.396728,
> 2] ../auth/ntlmssp/ntlmssp.c:119(gensec_ntlmssp_update_find) Failed
> to parse NTLMSSP packet: zero length [2019/01/14 14:59:21.396777,
> 1] ../auth/gensec/spnego.c:1218(gensec_spnego_server_negTokenInit_step)
> gensec_spnego_server_negTokenInit_step: ntlmssp: parsing
> NEG_TOKEN_INIT content failed (next[(null)]):
> NT_STATUS_INVALID_PARAMETER
>
> Windows clients claim they can’t find a path to the server/share, and
> Mac clients just don’t work. The server has been running since
> mid-December with no updates, no reboots and no issues. SSSD (ssh
> authorization to AD) logins are working fine, and interestingly
> enough, smbclient seems to be able to connect without difficulty. So
> why can’t my Windows and Mac clients connect?
>
> Thank you for the help,
> --
> Jason Lewis
> Senior Systems Engineer @ Micro Electronics, Inc.
> E: jwlewis at microcenter.com<mailto:jwlewis at microcenter.com>
>
Have you tried restarting Samba ?
What OS ?
How are you running Samba ?
I know you say nothing has changed on the Samba server, but has
anything changed externally ?
New router or windows updates etc ?
Rowland
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/options/samba