samba - Feb 2004 - Samba 3.0.1 -> 3.0.2 upgrade problem

Hello!

This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final on our 3
servers and users were not able to login. All servers run RedHat 7.3, we
use LDAP as backend. Two servers work as PDC (each in different VLAN), one
server is BDC. I had only few minutes to test it from Windows XP clients 
(we use Windows 98, 2000 and XP clients in our company) because we have 
hundreds of users connected and I had to go back to 3.0.1 immediately 
before the get angry:-) I found strange errors in client's machine log, 
desciption follows:

[2004/02/11 07:30:07, 0] lib/util_sock.c:send_smb(604)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2004/02/11 07:30:07, 2] smbd/server.c:exit_server(558)
  Closing connections
[2004/02/11 07:30:07, 2] rpc_parse/parse_prs.c:netsec_decode(1575)
  netsec_decode: FAILED: packet sequence number:
[2004/02/11 07:30:07, 2] lib/util.c:dump_data(1830)
  [000] B9 41 2A EF DD 51 EA 02                           ?A*??Q?.
[2004/02/11 07:30:07, 2] rpc_parse/parse_prs.c:netsec_decode(1577)
  should be:
[2004/02/11 07:30:07, 2] lib/util.c:dump_data(1830)
  [000] 00 00 00 00 80 00 00 00                           ........
[2004/02/11 07:30:07, 0] 
rpc_server/srv_pipe.c:api_pipe_netsec_process(1371)
  failed to decode PDU
[2004/02/11 07:30:07, 0] 
rpc_server/srv_pipe_hnd.c:process_request_pdu(605)
  process_request_pdu: failed to do schannel processing.
[2004/02/11 07:30:07, 2] passdb/pdb_ldap.c:init_sam_from_ldap(462)
  init_sam_from_ldap: Entry found for user: ogulas-nb$
[2004/02/11 07:30:07, 2] passdb/pdb_ldap.c:init_sam_from_ldap(462)
  init_sam_from_ldap: Entry found for user: ogulas
[2004/02/11 07:30:07, 2] auth/auth.c:check_ntlm_password(310)
  check_ntlm_password:  Authentication for user [OGulas] -> [OGulas] 
FAILED with error NT_STATUS_WRONG_PASSWORD

I allways compile installation package from SRPMS, but it went without 
errors. Does anybody have the same experience? Do you have any ideas?

Best regards

Michal Sladek

Michal Sladek wrote:
 > This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final
 > I had only few minutes to test it from Windows XP clients
 > (we use Windows 98 and XP clients in our company) because we have
 > hundreds of users connected and I had to go back to 3.0.1 immediately
 > before the get angry:-)

Exactly the same happend with me.

After compiling 3.0.2 (which worked absolutely fine) and installing it,
the telephone started to ring, and I had to revert immediately.

Basic effect:
when attaching a network drive, the system asked for a password and
afterwards rejected the service with a message like
'invalid user or password'

I haven't got time to install 3.0.2 on a spare server to check what
went wrong without the threat of being thrown out of the window,
but if in between someone got some hints what might have gone wrong
and (even more interesting) how to fix it, I would greatly appreciate
to get the info, too.

Thanks
Regards
john

> org] On Behalf Of Barry Smoke
> Sent: Thursday, 12 February 2004 02:47
> Cc: samba@lists.samba.org
> Subject: Re: [Samba] Samba 3.0.1 -> 3.0.2 upgrade problem
> 
> same thing here...
I had a similar experience, where NT4, 9X & DOS clients dropped off. 

This was caused by a hung process  or locked file in my case, where smbd
failed shutdown cleanly. 
Rather than attempting to trace the rogue file/process, I simply
restarted the machine and all came up roses.
> 
> amrito wrote:
> 
> > Michal Sladek wrote:
> > > This morning I tried to upgrade Samba from 3.0.1 to 3.0.2 final I
> > > had only few minutes to test it from Windows XP clients (we use 
> > > Windows 98 and XP clients in our company) because we have 
> hundreds 
> > > of users connected and I had to go back to 3.0.1 
> immediately before 
> > > the get angry:-)
> >
> > Exactly the same happend with me.
> >
> > After compiling 3.0.2 (which worked absolutely fine) and installing 
> > it, the telephone started to ring, and I had to revert immediately.
> >
> > Basic effect:
> > when attaching a network drive, the system asked for a password and 
> > afterwards rejected the service with a message like 
> 'invalid user or 
> > password'
> >
> > I haven't got time to install 3.0.2 on a spare server to check
what
> > went wrong without the threat of being thrown out of the 
> window, but 
> > if in between someone got some hints what might have gone wrong and 
> > (even more interesting) how to fix it, I would greatly 
> appreciate to 
> > get the info, too.
> >
> > Thanks
> > Regards
> > john
Might be better to set-up a test machine & test your upgrades before
rolling them out eh!

Cheers,

Lewis