Lamar.Saxon@americredit.com
2006-Feb-23 18:11 UTC
[Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems...
Wondering if any one has seen the following issues with Samba 3.0.21b with Windows XP and 2003 clients: [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) Failed to parse NTLMSSP packet, could not extract NTLMSSP command [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) Failed to parse NTLMSSP packet, could not extract NTLMSSP command Client logs are full of these messages. Seems to only affect 2003 and XP clients since I upgraded to 3.0.21b since my Windows 2000 clients are connecting with no issues. I could connect with the same smb.conf file with no issues on 3.0.20b; but was having a problem with 2003 servers connecting to Samba. I have seen other messages; but mainly with winbindd which I am not using... Before I post debug information, I wanted to make sure it was not a simple fix I was missing. Searched BugZilla; but now posting to the group... Thanks ! Lamar Saxon Lamar.Saxon@americredit.com Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
Jeremy Allison
2006-Feb-23 21:16 UTC
[Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems...
On Thu, Feb 23, 2006 at 11:55:44AM -0600, Lamar.Saxon@americredit.com wrote:> > Wondering if any one has seen the following issues with Samba 3.0.21b > with Windows XP and 2003 clients: > > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > > Client logs are full of these messages. Seems to only affect 2003 and > XP clients since I upgraded to 3.0.21b since my Windows 2000 clients are > connecting with no issues. I could connect with the same smb.conf file > with no issues on 3.0.20b; but was having a problem with 2003 servers > connecting to Samba.Can you get a sniffer trace to illustrate this ? Jeremy.
Lamar.Saxon@americredit.com
2006-Feb-23 21:19 UTC
[Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems...
I think I might be able to arrange that via our network monitoring group. They ( security ) frown on us running our own ! Will get it coordinated. Do you need any other information like a testparms and/or running smbd in debug 10 mode ? I will try to provide as much information as I can... Lamar -----Original Message----- From: Jeremy Allison [mailto:jra@samba.org] Sent: Thursday, February 23, 2006 3:16 PM To: Saxon, Lamar Cc: samba@lists.samba.org Subject: Re: [Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems... On Thu, Feb 23, 2006 at 11:55:44AM -0600, Lamar.Saxon@americredit.com wrote:> > Wondering if any one has seen the following issues with Samba 3.0.21b > with Windows XP and 2003 clients: > > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > > Client logs are full of these messages. Seems to only affect 2003 and > XP clients since I upgraded to 3.0.21b since my Windows 2000 clientsare> connecting with no issues. I could connect with the same smb.conffile> with no issues on 3.0.20b; but was having a problem with 2003 servers > connecting to Samba.Can you get a sniffer trace to illustrate this ? Jeremy. Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.
Lamar.Saxon@americredit.com
2006-Mar-13 17:03 UTC
[Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems...
3.0.21c seems to fix the problems I was encountering with XP. Working on testing it with Windows 2003 now. Lamar -----Original Message----- From: Jeremy Allison [mailto:jra@samba.org] Sent: Thursday, February 23, 2006 3:16 PM To: Saxon, Lamar Cc: samba@lists.samba.org Subject: Re: [Samba] Samba 3.0.21b / Security = Server / Windows 2003 or XP clients / AIX 5.3 = Problems... On Thu, Feb 23, 2006 at 11:55:44AM -0600, Lamar.Saxon@americredit.com wrote:> > Wondering if any one has seen the following issues with Samba 3.0.21b > with Windows XP and 2003 clients: > > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > [2006/02/23 11:47:58, 1] libsmb/ntlmssp.c:ntlmssp_update(252) > Failed to parse NTLMSSP packet, could not extract NTLMSSP command > > Client logs are full of these messages. Seems to only affect 2003 and > XP clients since I upgraded to 3.0.21b since my Windows 2000 clientsare> connecting with no issues. I could connect with the same smb.conffile> with no issues on 3.0.20b; but was having a problem with 2003 servers > connecting to Samba.Can you get a sniffer trace to illustrate this ? Jeremy. Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.