similar to: Samba4 and Ubuntu 12.10 : problem to get it working...

Hello, I am using Samba 4.0.5 and got this kind of error messages in samba.log (loglevel 2). While this happens getent passwd shows no domain users, but everyone could reach all of the shares. Any idea what could cause this kind of error messages? [2013/11/21 15:53:15.736390, 1] ../source3/smbd/sesssetup.c:276(reply_sesssetup_and_X_spnego) Failed to generate session_info (user and group

Hi all, Here's my problem : after installing and setting up samba 4 on a Ubuntu server 13.04, everything is ok : samba is working, I can connect ; kerberos is ok also. BUT !!! I have a problem with dns forwarding. Here's my settings : in samba domain provision, i select 10.10.70.10 (i.e. my samba server) as dns forwarder (we have a firewall, but it's not set as DNS forwarder) I change

hi: I setup a small samba 4.0.5 AD DC server. my client is windows 7 and linux. and I use windows 7 with remote managment tools to manage rfc2307 account seetings of samba4 DC. I hope my users can use the same account to use windows and linux. samba4 DC provsion command as below: samba-tool domain provision --use-rfc2307 --function-level=2008_R2 --interactive and smb.conf global

I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is showing the following: root at dtdc03:~# tail -f /usr/local/samba/var/log.samba [2016/12/01 10:14:39.167794, 0] ../source4/librpc/rpc/dcerpc_sock.c:245(continue_ip_open_socket) Failed to connect host 192.168.16.50 (aa03011a-94c2-4c52-bc60-6fd2f75d35e5._msdcs.dtshrm.dt) on port 135 - NT_STATUS_CONNECTION_REFUSED.

Hi List I've update updated from samba-4.10 to samba-4.11. After the update I can not manga the dns entries by samba-tool and can not connect with net rpc. I get the error message: NT_STATUS_CONNECTION_REFUSED. I use the bind9 backend. samba-tool dns zonelist localhost Failed to connect host 127.0.0.1 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 127.0.0.1 (127.0.0.1)

My DC's need to be upgraded to support audit logging a la  Setting up Audit Logging - SambaWiki | | | | Setting up Audit Logging - SambaWiki | | | Are there any big red flags/pitfalls not in the release notes when going straight to 4.8?

On 2016-12-04 09:11, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > >> I have two DC's running Samba 4.5.0 and the "dtdc03" log.samba is >> showing the following: >> >> root at dtdc03:~# tail -f /usr/local/samba/var/log.samba >> [2016/12/01

On 2016-12-04 10:25, Rowland Penny via samba wrote: > On Sun, 04 Dec 2016 09:43:25 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > On 2016-12-04 09:11, Rowland Penny via samba wrote: > > On Sun, 04 Dec 2016 08:01:09 -0600 > Bob of Donelson Trophy via samba <samba at lists.samba.org> wrote: > > I have two DC's running

> when i dont use localhost its not working: > > > phoenix /mnt/backupsamba # samba-tool domain backup online > --server=$(hostname -s) --targetdir=/mnt/backupsamba/ -U Administrator > Failed to connect to ldap URL 'ldap://phoenix' - LDAP client internal > error: NT_STATUS_CONNECTION_REFUSED > Failed to connect to 'ldap://phoenix' with backend

Dear All, Recently I notice that sometime the AD DC will die sometime. Any one have see this issue before? And yesterday case lead me to believes that this error message was the issue... They are repetitive and thus I only show 2... [2015/07/29 00:00:04.620033, 0] ../source4/librpc/rpc/dcerpc_util.c:681(dcerpc_pipe_auth_recv) Failed to bind to uuid e3514235-4b06-11d1-ab04-00c04fc2dcd2 for

Hello Samba team ! On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) : -> One PDC : pdc01 -> Two "slave" DC : sdc02, sdc03 I don't know why, but sometimes Samba receive the SIGTERM signal and restart even if I remove it from the logrotate configuration. On "pdc01" I see : ---------- pdc01 (log.samba) ---------- SIGTERM: killing children

New to linux and new to Samba so any direction in troubleshooting would be helpful. Here is what I have so far. Within a half an hour of a reboot of the server my cpu reaches high numbers and becomes slow to respond on all actions. With my limited understanding I have used vmstat to observe the system. I noticed is that the numbers of forks grows from 1-2k to 43k within 30 minutes after reboot. I

What Samba version are you using? I have seen a similar problem triggered by connectivity issues between the DCs. What's the output from samba-tool drs showrepl? Still, I haven't found a solution... On Sat, Aug 1, 2015 at 5:30 AM, Min Wai Chan <dcmwai at gmail.com> wrote: > Just to ask. > Anyone can shard some light on that wrong is that? > > Thank you. > > Min

I've been looking at the Sambawiki for notes on upgrading (https://wiki.samba.org/index.php/Upgrading_a_Samba_AD_DC) The way I read it it is suggested to uninstall samba completely and then essentially re-installing. That seems like a Murphy's Law disaster (with my luck) waiting to happen. Is "upgrading "in-place" a realistic option?

>> >> Hello Samba team ! >> >> On my network I have three Samba-4.1.17 domain controllers (Debian Jessie) >> : >> -> One PDC : pdc01 >> -> Two "slave" DC : sdc02, sdc03 >> >> I don't know why, but sometimes Samba receive the SIGTERM signal and >> restart even if I remove it from the logrotate configuration. On >>

On 26/02/15 08:15, L.P.H. van Belle wrote: > aha ... > > ;-) > > netstat --numeric-hosts --numeric-ports --programs -u -t -l > i didnt see samba running.. ;-) > > >> I removed the "service bind9 stop &&" from line 449 (as bind9 was >> already stopped, why stop it again) and ran the script on my >> VM. All the

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -

Greetings, The process to join a new samba 4.6 DC to an existing samba 4.1 DC repeatedly caused: samba_dnsupdate --verbose --all-names to fail on the new DC with: Failed to connect host x.x.x.x on port 49152 - NT_STATUS_CONNECTION_REFUSED Noted: both samba versions are obsolete and will be updated post haste. Regardless, samba_dnsupdate was accidentally invoked on the new DC while the

Hi I've had success building & using my own Samba4 Debian package using the instructions on the SambaWiki, specifically: https://wiki.samba.org/index.php/OS_Requirements Distribution Specific Package Installation Debian / Ubuntu # apt-get install build-essential libacl1-dev libattr1-dev \ libblkid-dev libgnutls-dev libreadline-dev python-dev libpam0g-dev \ python-dnspython gdb

I am setting up W7 profiles following the "Samba & Windows Profiles" on the Sambawiki. If it matters, I have two functional DC's and one member server. When I run '# chmod 1770 /srv/samba/profiles' (on the member server) the permissions changed to: root at mbr01:~# ls -alh /srv/samba/profiles total 12K drwxrwx--T+ 2 root root 4.0K Mar 1 10:21 . drwxr-xr-t 5 root