Displaying 20 results from an estimated 800 matches similar to: "smbd log meesages"
2004 Feb 24
3
PDU & schannel errors
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,
2004 Jan 12
1
Another problem with Win2k logins...
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
2004 Jul 28
1
failed to decode PDU - failed to do schannel processing
I am running Slackware 10
samba-3.0.5-i486-2
I get the following errors in my syslog, over and over and over...
Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0]
rpc_server/srv_pipe.c:api_pipe_netsec_process(1397)
Jul 27 17:05:51 Olympus smbd[11471]: failed to decode PDU
Jul 27 17:05:51 Olympus smbd[11471]: [2004/07/27 17:05:51, 0]
2004 Feb 09
1
error messages -- what does it mean?
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
2004 Jul 11
1
Cannot login to PDC after upgrade
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
2003 Oct 17
1
Updating 2.2.8a to 3.0.0 (LDAP)
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
2004 Feb 09
2
primary gid of user [desires] is not a Domain group !
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]
2005 Feb 22
1
Failed logon with 3.0.11
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
2004 Jul 14
2
Slow Access *oopps*
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,
2004 Mar 30
1
Log Message
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
2004 May 26
2
Samba 3 and LDAP - Error loading profiles
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
2004 Aug 09
1
Verbose Logs?
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)
2004 Apr 27
2
Problems with Samba 3 and XP Roaming Profiles
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
2003 Jul 23
1
Profiles not working with W2K SP4, Samba 3.0.0beta2 (already posted but got no answer)
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):
=====>
2004 Jul 14
1
Slow Access
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
2004 Jun 10
1
Samba 3.0.5 pre1 cannot ad windows xp machine to domain
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
2010 Aug 18
1
Error: You do not have permission to change your password
I'm using Samba v3.5.4-62 on Fedora 13 PDC Using LDAP passdb backend
and do the following...
1. Login as user on Windows system using domain user name and password
- Login successful
2. Press Ctrl-Alt-Del
3. Press Change Password
4. Enter old and new password as prompted
5. Receive response "You do not have permission to change your password."
I receive the following
2004 May 04
1
Samba PDC
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
2004 Apr 16
1
Problems with NT passwords using Samba3 and LDAP
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
2003 Jun 26
1
Urgent : Connection problem to a Samba PDC
Hi,
We have a Samba3.0Beta1-LDAP acting as PDC for about 170 computers, since 2
weeks everything works perfectly but since yesterday every computers are unable
to connect to the PDC.
The following message appears on client side :
The session setup from the computer CJEREV01 failed to authenticate. The
name(s) of the account(s) referenced in the security database is
CJEREV01$. The following