Hello Juanjo,
I have a related problem I believe, and have similar errors showing up in my
error logs - specifically the bit about:
[2004/01/15 13:19:54, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371)
failed to decode PDU
[2004/01/15 13:19:54, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605)
process_request_pdu: failed to do schannel processing.
[2004/01/15 13:19:56, 1] smbd/service.c:make_connection_snum(705)
I compiled 3.0.2pre1 with the options:
./configure --with-ldap=no --with-winbind
In my case the users can login but never generate a profile, or the profile
never gets saved back to the PDC. Otherwise, they can also smbclient -L
PDCname -U username.
I hope someone finds the source of these errors.
Cheers
Jeff
On Monday 12 January 2004 17:44, Juanjo Lull ONO wrote:> Hi all,
> After recovering the former SID that I hadn't had in mind while
changing
> the Linux distro (thanks to Thomas for his help), now I still have some
> problems. I can't still get any user to login but the ones that must be
in
> cache in the clients (thanks again Thomas). So, I'll give you the logs
to
> see if anybody detects something strange... The users can perform a
> 'smbclient -L PDCname -U username' but they cannot still login in
their
> machines. As the network is not so big (4 computers x 20 users), I'd
have
> to change around 100 registry entries if I don't find a solution, but I
> still would like to know what's going on... ############### log.p3
(one
> of the clients) #########
> [2004/01/12 23:29:04, 1] smbd/service.c:close_cnum(880)
> p3 (192.168.0.183) closed connection to service jlull
> [2004/01/12 23:29:10, 0]
> rpc_server/srv_pipe.c:api_pipe_netsec_process(1357) failed to decode PDU
> [2004/01/12 23:29:10, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605)
> process_request_pdu: failed to do schannel processing.
> [2004/01/12 23:29:23, 1] smbd/service.c:make_connection_snum(698)
> p3 (192.168.0.183) connect to service jlull initially as user jlull
> (uid=1006, gid=408) (pid 16244)
> [2004/01/12 23:29:33, 1] smbd/service.c:make_connection_snum(698)
> p3 (192.168.0.183) connect to service jlull initially as user jlull
> (uid=1006, gid=408) (pid 16244)
> [2004/01/12 23:31:00, 1] smbd/service.c:close_cnum(880)
> p3 (192.168.0.183) closed connection to service jlull
>
> ########## log.nmbd ##########
> [2004/01/12 23:37:53, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95)
> process_logon_packet: Logon from 192.168.0.13: code = 0x12
> [2004/01/12 23:43:51, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95)
> process_logon_packet: Logon from 192.168.0.13: code = 0x12
> [2004/01/12 23:43:51, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95)
> process_logon_packet: Logon from 192.168.0.13: code = 0x12
> [2004/01/12 23:44:23, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95)
> process_logon_packet: Logon from 192.168.0.14: code = 0x12
> [2004/01/12 23:44:23, 1] nmbd/nmbd_processlogon.c:process_logon_packet(95)
> process_logon_packet: Logon from 192.168.0.14: code = 0x12
>
> Here 192.168.0.13 is the client from where I am logged (with a cached user)
> and 192.168.0.14 is another client that has generated that 0x12 code
> without anything more that being on (I mean, no user trying to log).
It's
> all the time generating that code = 0x12... Any idea?
--
Jeff Gardiner [ gardiner@imaging.robarts.ca ]
System Administrator - Imaging Research Laboratories
Robarts Research Institute - London ON, Canada
519.663.5777 x34089
~~~~~~~
Those who do not understand Unix are condemned to reinvent it, poorly.
-- Henry Spencer
~~~~~~