similar to: failed to decode PDU - failed to do schannel processing

I extracted the following weird error from the sys-log regarding pdu and schannel (have the same PID): Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0, pid=31833, effective(65534, 65533), real(65534, 0)] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 24 10:40:37 s-svr01 smbd[31833]: failed to decode PDU Feb 24 10:40:37 s-svr01 smbd[31833]: [2004/02/24 10:40:37, 0,

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

Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 9 07:08:10 fileserver smbd[2025]: failed to decode PDU Feb 9 07:08:10 fileserver smbd[2025]: [2004/02/09 07:08:10, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) Feb 9 07:08:10 fileserver smbd[2025]: process_request_pdu: failed to do schannel processing. I

We recently converted our Redhat9 Samba server to Debian Sarge/testing. We are running (3.0.2a-Debian). After installing Debian, I itegrated the old configuration files (smb.conf, smbpasswd, smbusers, secrets.tdb) making changes where I thought it was necessary. When I tried to login to our Windows 2000 server using rdesktopl, windows tells me that I've specified the incorrect username or

Hi, we have Samba 2.2.8a+LDAP 2.0.27 domain controllers running on our Debian servers and I'm preparing the update to Samba 3.0.0. Everything seems to work fine so far, except that I get some error messages that I don't understand. Could someone please explain them to me? Should I wait for the next Samba release before switching to 3.x? The error messages: When a user logs into the

Can someone please explain what these messages mean. I am running 3.0.2a with no issues at all. I just happened to be looking through the logs and notice the messages. [2004/05/10 03:53:23, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) failed to decode PDU [2004/05/10 03:53:23, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) process_request_pdu: failed to do schannel

Greetings ... I hope somebody can explain this to me, or give me a help to fix this problem ... On my Samba server ( 3.0.2rc2 ) I am getting ... Feb 9 17:31:21 eastrand smbd[2113]: [2004/02/09 17:31:21, 0] rpc_server/srv_pipe.c:api_pipe_netsec_process(1371) Feb 9 17:31:21 eastrand smbd[2113]: failed to decode PDU Feb 9 17:31:21 eastrand smbd[2113]: [2004/02/09 17:31:21, 0]

Hi All, come acrross a curious issue with 3.0.1-2 from Debian unstable. Looks like a bug of sorts to me... Have a PDC configured and basically working well, apart from single recurrent issue that keeps popping up in the logs below, related to failure or breaking of remote procedure calls. The pipes more often break when using the UNC path as opposed to IP. couldn't find service netlogon

Hi, I just tried an upgrade from Samba 3.0.2a to 3.0.11 to fix a known bug (1147), but now I get a different problem. Users cannot login. Here's what the log looks like in 3.0.2a ............. [2005/02/22 16:57:49, 2] param/loadparm.c:do_section(3339) Processing section "[shares]" [2005/02/22 16:57:49, 2] lib/interface.c:add_interface(79) added interface ip=192.168.4.10

Don't know how that last email took off, but that wasn't suppose to happen. Any the root 3 59.6 0.0 0 0 ? R< 10:16 11:04 [events/0] is a kernel thread that handles weird irq stuff. I just disabled onboard sound and USB and it went away. I'm still left with my other problems though, here they are 2.) I'm having LMB and DMB problems on the server,

Hi, I'm setting up Samba with ldap backend and everythin appears to be working correctly except for profiles. Using: samba-3.0.2 openldap-2.1.26 smbldap-tools-0.8.4 When a user 'testa' tries to logon from a Win2K system that has joined the domain he gets the following error message: "Windows did not load your roaming profile and is attempting to log you on with your local

Hello. I'm not quite sure what the problem with my samba is. Im running red hat 9 and samba 3.0 and my log has far too much information. this is my samba log: --------------------- samba Begin ------------------------ **Unmatched Entries** lib/util_sock.c:get_peer_addr(978) getpeername failed. Error was Socket operati on on non-socket : 2 Time(s)

Can someone tell me what this means; [2004/03/30 12:09:56, 0] rpc_server/srv_pipe_hnd.c:process_request_pdu(605) process_request_pdu: failed to do schannel processing. Martin Stacey IT Support Manager Safcol Australia Pty Ltd

logins Reply-To: I've sourced the groups, but haven't had any success with solving this problem. Here are the details: I have a debian/testing system running samba 3.0.0beta2-1. It was working fine with the 2.x series, until I upgraded to 3.0. The debian server (al) is a PDC for a small NT domain (isabela) with three workstations, all running win2k pro. All but one work fine

I've got some annoying Problems with roaming profiles. Perhaps someone is able to help me... I would like to use Samba as a PDC and for storing NT roaming profiles. When I first installed Samba 3.02 and XP SP1 (Before that I used Samba 2.2.8a and XP without SP1), XP downloaded the old profiles it found. But upon shutdown or logoff, changes to the profiles were not written to the server. I

Hello, I still have a problem with my Samba installation. Userprofiles don't work under W2K SP4. They work fine with Windows NT 4. When loggin on for the first time the user profile directory is created. After loggin off however no data is written to the profile directory on the Samba PDC. When logging on there ist the following activity in the logs (debug level = 1; log.pc1): =====>

Before yesterday I had a perfectly (as far as I could tell) functioning PDC with samba, roaming profiles and all. Yesterday I made some changes to the server 1.) install dhcp3 server 2.) changed IPs from 192.168.1.50 to 192.168.1.1 3.) changed netbios name from garnet-base to garnetmain 4.) started two more interfaces eth1 (172.17.0.0/16) and eth2 (cable internet) eth0 is still 192.168.0.0/16

Hi all, I can add my W2K machines to the Samba 3.0.5pre1 with no problems, but I can not add my XP machines. Existing XP machines work fine, but when I try to add new XP machine it does not work. Here is my smb.conf and pc from the log.smbd Thanks -Glenn [global] netbios name = HSFNP01 workgroup = MTHCS security = user os level = 64 domain master = yes local master = yes preferred master = yes

Does Samba3 require windows machine accounts? I need to have users authenticate to a Samba PDC and be able to run logon scripts when authenticated, BUT NOT have to have machine accounts for every user be setup. In other words, can the user authenticate without his/her machine being part of the Domain? Thanks, Rich

I'm at my wits end here so hopefully someone can help me. Currently I have a Redhat 9.0 box running Samba 2.2.7 with openldap 2.0.27 as a PDC Domain logins work great with this setup. I can add, remove, modify computers and users all day long without a glitch. I do not store usernames in the local smbpasswd or passwd files. User information is stored in ou=Users,dc=mydomain,dc=com Group