similar to: smbclient (Samba 4.9.4) "Unable to initialize messaging context"?

> On 21 Dec 2018, at 09:54, David C. Rankin via samba <samba at lists.samba.org> wrote: > > Sambadevs, > > I don't know if this is a bug or just a spurious error message when using > smbclient (on a standalone config), but checking smbclient, I get: > > 02:47 2pi:~> smbclient -U% -Llocalhost > Unable to initialize messaging context > >

Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: >> What is "Unable to initialize messaging context"? >> >> I see a patch back in July, related to "Fix bug 13465", >> https://lists.samba.org/archive/samba-technical/2018-July/129186.html but it >> is unclear why the message is still being issued? > > Because that patch for bug 13465

On Wed, 2 Jan 2019 09:32:55 +0100 "Stefan G. Weichinger via samba" <samba at lists.samba.org> wrote: > Am 21.12.18 um 16:47 schrieb Peter Eriksson via samba: > > >> What is "Unable to initialize messaging context"? > >> > >> I see a patch back in July, related to "Fix bug 13465", > >>

Current Version: samba 4.18.1 All, I have several **standalone** servers on a subnet, and for quite some time, I have received log messages in other standalone machines about multiple responses from the WINS server. There is only a single WINS server on the network (as it has been since samba 2.02 or earlier). The WINS server is 192.168.6.14. The log message that is received for example

Hello, I am running slackware 9 and I have also updated samba to version 2.2.8a from the slackware security update. I can access my xp box with no problems from my linux box but I cannot access my linux box from my xp box. I have been on several forums and IRC channels and no one seems to have much insight into my problem, someone recommended trying to post my problem here. I have gotten

Guys, I have probably missed an announcement or overlooked something in a changelog, but I just want to confirm what I'm seeing is expected behavior. I run samba in standalone mode and I have always checked operation with smbclient -U% -Llocalhost Now the faithful command returns an error: Connection to localhost failed (Error NT_STATUS_BAD_NETWORK_NAME) Simply using the hostname

On Thu, Nov 08, 2018 at 06:12:40AM +1300, Andrew Bartlett wrote: > On Wed, 2018-11-07 at 15:19 +0300, Albert Berger via samba wrote: > >  > > I tried in sequence to start Samba in following conditions: > > > > 1. With all clients disconnected from Samba server; > > 2. As above + all shares disabled; > > 3. As above + minimal smb.conf > > 4. With

Hello ! I decided to upgrade my fileservers from stretch/samba 4.9 to buster/samba 4.11 I just realized that smbd is not working anymore :-/ If someone has an idea It would be amazing... as an idiot, I upgraded my 20 servers.... without snapshot.... Thank you so much Here's some logs : root at ef113:~# tail /var/log/samba/log.smbd #1

I'm having lots of trouble getting connected to samba on my little 2 computer network at home. One is a RedHat machine and the other is Windows 2000. Trying to access my just the IP of the RedHat machine from my Windows machines gives me the "Cannot find the file or item '\\192.168.20.2'" error. I've got 2 NICs in my RedHat machine so I did use the "interface

Hello, Actually I am having a strange error where I hope you can help me: As far as I know I think at least Samba is configured right but I don't reach to connect from a Windows machine to the samba (on RedHat) machine: I tried to do following things to see where the error is: * Testparm runs without a problem. * When typing "$ smbclient -L yourhostname" it asks for a Password,

I'd like to share the results of a little experiment I did yesterday. On an Arch Linux box on which in December I tried, and failed, to upgrade from 4.7.4. to 4.9.4 and then had to revert back to 4.7.4, yesterday I did the upgrade to the new 4.10 release. This time, everything worked, I had no errors whatsoever. So, I then made a backup of the new installation, in 3 different ways: Online

On Wed, 2 Jan 2019 09:54:24 +0000 Rowland Penny via samba <samba at lists.samba.org> wrote: > On Wed, 2 Jan 2019 09:45:56 +0000 > Kristján Valur Jónsson <kristjan at rvx.is> wrote: > > > Any thoughts? Have code, will debug. The error itself is > > meaningless to me and I am deeply and utterly unfamiliar with samba > > code, but if you have any thought or

Hai, I've updated the repo with the Debian Stretch 4.9.4 packages. No changes on my side, so check the samba changelogs for whats fixed. Info : https://apt.van-belle.nl Buildlogs : https://downloads.van-belle.nl/samba4/Buildlogs/stretch/ The repo setup. 1) Choose http or https for you apt, both work, for https you need to : apt-get install apt-transport-https 2) Import my public key

Hi, We upgraded a legacy (NT4) domain from 3.6 series to 4.8 and then 4.9.4 samba version (using sernet subscription packages / debian stable) The setup is composed of 4 DCs with each 2 CPU/16GB RAM. We currently have ~700 user accounts / ~600 computers / ~150 groups Our mail setup, SSO, ... query the 4 DCs constantly. Every 5 to 10 days the RAM consumption and CPU usage (due to kswapd)

Hi there. I'm trying to upgrad from 4.7.7 to 4.9.4. I built from source, running on centos 7.6 on a Raspberry Pi. When testing on a secondary DC, my "samba-tool drs showrepl" errors out with: ERROR(<class 'samba.drs_utils.drsException'>): DRS connection to dc02.rvx.is > failed - drsException: DRS connection to dc02.rvx.is failed: (8, >

Hai Viktor,   Yes, i did keep that in mind that it was an upgrade, that exact why im responding. ;-)   If in the base  /etc/hostname, /etc/nsswitch.conf and /etc/resolv.conf or systemd  cointains wrong settings, you might inherit these. So it might be that a previous samba was accepting these settings, but a latest samba not. Or a previous systemd version accepted these and a newer not..  

so the DC with FSMO is not done first?     Van: Kristján Valur Jónsson [mailto:kristjan at rvx.is] Verzonden: vrijdag 28 december 2018 17:08 Aan: L.P.H. van Belle Onderwerp: Re: [Samba] replication failing for 4.9.4 dc01 is still running 4.7.7.  No need to restart it.  There is also still a DC03 running 4.7.7.  the only one I've upgraded is DC02.  resolv.conf on DC02 is configured with

We just noticed an interesting bug/misfeature on our Samba 4.9.4 servers (FreeBSD 11.2). The same effect is also visible on Samba 4.8.3 on CentOS 7. Start with a directory that looks like this: root at filur00:/tmp/test # ls -la total 50 drwxrwx--- 2 peter86 uf-iti-all 3 Feb 27 11:27 . drwxrwxrwt 10 root wheel 56 Feb 27 16:41 .. -rw-rw---- 1 mikha02 uf-iti-all 6 Feb 27 11:27

On Thu, 27 Dec 2018 11:07:08 +0100 "L.P.H. van Belle via samba" <samba at lists.samba.org> wrote: > Gooood morning Rowland, :-) > > Your late ;-).. > What i also did see, so its more clear for others also. > > > Dez 22 21:08:31 dc1 systemd[1]: Starting Samba AD Daemon... > > Dez 22 21:08:31 dc1 kernel: audit: type=1131 > >

I just noticed that smbclient from Samba 4.9.4 /built by myself) on FreeBSD 11.2 coredumps when called like this: smbclient -L <hostname> > % /liu/pkg/samba/4.9.4-liu/bin/smbclient -L filur00 > Enter username at AD.LIU.SE's password: > Abort (core dumped) … if it is linked against /usr/local/lib/libmd5.so (which is part of “libwww”). If I remove libmd5.so and recompile