similar to: session request to PDSLNX failed

Hi, I have some problems running Samba and Winbind 3.0.22 in a AD, kerberos environment. I have seen previous posts on several forums about this problem but haven't found any solution for it yet. I have no problem with the default Samba package that comes with Ubuntu, 3.0.14a. But I do wan't to upgrade and the only option in that case seems to be to compile it. I compiled it with

Hello, I don't know if this is a bug of some sort, but I am running out of ideas. O/S: FreeBSD 2.2.5-stable Samba: Version 1.9.17p4 Clients: Win95 only I am trying to get Samba to accpet Win95 clients logging on my FreeBSD Samba domain logon server. If I empty (null) my password I can login, if I have an encrypted password (/etc/passwd) it will not work. I will get: "You have

All, I've just upgraded from 2.0.4 to 2.0.5a on my Sparc 20 (Solaris 2.5.1). I've kept the same configurations but I can no longer map drives from my Windows machines (NT, Win95). smbd exits on error: [1999/07/26 15:48:16, 2] smbd/server.c:main(716) Changed root to / [1999/07/26 15:48:16, 3] smbd/oplock.c:open_oplock_ipc(85) open_oplock_ipc: opening loopback UDP socket. [1999/07/26

I am fairly new to the world of SAMBA and am having problems getting SAMBA to work on OS/390 OMVS 2.6. I have installed SAMBA on OS/390 OMVS 2.4 system and file sharing is working great. Here is the problem. >From OMVS I issue: smbclient -L '\\myserver' -U username -d 11 I get the following results: SAMBA Client log lp_file_list_changed() file /usr/local/samba/lib/smb.conf

Here's my setup: Caldera Open Linux Lite (kernel 2.0.29) Samba 2.0.4a Windows Domain (Two Windows NT 4.0 Servers -- one PDC, one BDC -- and numerous Windows NT 4.0 Workstations) I can see my Linux box in Network Neighborhood on my Windows NT boxes. I can open the Linux box and see the top level shares available. When I try to open a share I see one or two anonymous folders. Anyone

Here is some log output that occurs on the production during the process of issuing a net use command from the win95 box to the samba server. The connection reset by peer message appears immediately after the error 54 network is busy message appears on the windows 95 machine. (This is debug level = 10) [1999/05/18 18:21:00, 2] smbd/server.c:main(709) Changed root to / [1999/05/18 18:21:00,

Am 30.12.2016 um 19:10 schrieb Rowland Penny via samba: >> -d10 please :-) >> >> Volker >> > > I would have worked up to that ;-) > > But the OP has since posted that he just changed the smb.conf on his > old PDC and didn't empty /var/lib/samba emptying /var/lib/samba caused issues with joining: no secrets.tdb -> main ~ # winbindd -i -d10 INFO:

On Sat, 31 Dec 2016 01:14:46 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 30.12.2016 um 19:10 schrieb Rowland Penny via samba: > > >> -d10 please :-) > >> > >> Volker > >> > > > > I would have worked up to that ;-) > > > > But the OP has since posted that he just changed the

Hi, I'm running a samba CTDB setup using default Centos 7.2 repos, fully up-to-date. This is in pre-production so this is quite a nasty problem. Everything was running fine, including after a package update 1-2 days ago. However, this morning I can't get winbind started, CTDB times it out. I've taken the clustering=yes line out of smb.conf, and run winbind at dedug level from the

On 2017-11-13 13:31, Rowland Penny wrote: > On Mon, 13 Nov 2017 13:18:20 +0100 > Sven Schwedas via samba <samba at lists.samba.org> wrote: > >> Could we please not waste a week poking at random unrelated stuff this >> time? These "I try the same stuff no matter what the problem is" >> boilerplate emails become really grating after the first few times. :/

I've been searching this lists archives and using the Googles for two days now, and keep coming across the same messages from before 2012 with the errors I'm getting, so either I'm seeing something new, or I've missed something stupid. I've been following the HOWTOs here from Samba.org. In each case below, I uninstalled the provided Samba packages and built from source.

Hello, Getting during configure the infamous error: No locking available. Running Samba would be unsafe solaris I went into tests folder and tried summary.c. It fails with the above error. I tried to make the fcntl_lock manually like it tries and got the following: root@raven:/usr/local/samba/source/tests #gcc -m32 -o fcntl_lock fcntl_lock.c fcntl_lock.c: In function `main':

I'm trying to solve a roaming profile problem which manifests as a locking error during Win2K logout with roaming profiles enabled. Level 3 debug tells me: [2002/05/30 11:59:58, 2] smbd/open.c:open_file(213) markk opened file markk/ntuser.ini read=Yes write=Yes (numopen=1) [2002/05/30 11:59:58, 3] smbd/process.c:process_smb(860) Transaction 1449 of length 75 [2002/05/30 11:59:58, 3]

There seems to be a few people having this problem, but not much response. I've dug into the logs, and while I don't know exactly what I am looking at, I think I may have found something that may make sense to someone. A short recap. Samba was working fine, until I did a Debian security update, which upgraded my Samba to 2.2.8a. Now, I can create files on a mounted Samba share in a

Debian Woody with security updates Linux kernel 2.2.25 Samba 3.0.0 libc6 2.2.5 The problem I have is with a windows application that uses samba. This application is crucial for the organization, so if this is not fixed, and soon, we will have to ditch Samba and move to a windows server. I *really* don't want to do this, as Samba has been working so well for years now and billg is rich enough

Any and all attempts to connect to our samba server, packaged in the redhat RPM found on samba.org, have failed. The allow statement is set to localhost, x.y.z. where x.y.z is our class C(ended with a period, as per the online help in SWAT.) Local connections via smbclient work beautifully, but connections from any other machine fails. I've followed the troubleshooting procedure to the

Samba 3.0.26a, two different RHEL4 boxes and a Fedora 2 box. I'm seeing this message whenever I do anything to nmbd with smbcontrol, for example smbcontrol reload-config or smbcontrol debug. [root@fleetwood samba]# smbcontrol nmbd reload-config params.c:pm_process() - Processing configuration file "/etc/samba/smb_all.conf" Processing section "[homes]" Processing section

Greetings, Here is what I have built samba on: Solaris 9 GCC 3.2.2 samba-3.0.20pre1 openldap-2.2.24 MIT Kerberos 1.4 Samba built with: ./configure --prefix=/opt/local/samba --with-automount --with-profile --with-acl-support --with-utmp --with-winbind --with-ads --with-ldap --with-krb5=/opt/local/kerberos5 --with-pam Within a minute of starting samba + winbind I get a core dump in the samba

Hi all, I've got kind of strange setup, wherein all of my data is on a big NFS server (RH linux 8.0 running the 2.4.18 kernel and nfs-utils 1.0.1-2.80) and my Samba 3.0.0 PDC server (RH linux 7.3 w/ 2.4.18 kernel, nfs-utils 0.3.3-6.73) mounts the NFS export with the following options: rw,vers=3,wsize=8192,rsize=8192,hard,intr This mounted partition is then re-exported to the windows users

Hello dear list! I'm about to setup a winbind to authenticate my proxy users through Active Directory. Unfortunately the daemon winbindd crash while requesting some wbinfo, Here is a transcript of the problem: IDCSRV922:~ # cat /etc/krb5.conf [libdefaults] default_realm = MY.DOMAIN.COM [realms] [logging] kdc = FILE:/var/log/krb5/krb5kdc.log