similar to: Certain systems can no longer access samba post upgrade to 4.3.9

On Mon, Aug 29, 2016 at 6:13 PM, Jeremy Allison <jra at samba.org> wrote: > On Mon, Aug 29, 2016 at 11:41:53AM -0400, Jeff Hodge via samba wrote: > > During an ubuntu 14.04 update samba was updated from 4.1.6 to 4.3.9. We > > had no problems with any windows system accessing the server prior to the > > upgrade to 4.3.9. It seems to affect access to the entire samba

On Mon, Aug 29, 2016 at 11:41:53AM -0400, Jeff Hodge via samba wrote: > During an ubuntu 14.04 update samba was updated from 4.1.6 to 4.3.9. We > had no problems with any windows system accessing the server prior to the > upgrade to 4.3.9. It seems to affect access to the entire samba server as > no shares are able to be seen or accessed when trying to view \\servername > or

On Tue, Aug 30, 2016 at 11:57 AM, Jeff Hodge <jeff.hodge55 at gmail.com> wrote: > On Mon, Aug 29, 2016 at 6:13 PM, Jeremy Allison <jra at samba.org> wrote: > >> On Mon, Aug 29, 2016 at 11:41:53AM -0400, Jeff Hodge via samba wrote: >> > During an ubuntu 14.04 update samba was updated from 4.1.6 to 4.3.9. We >> > had no problems with any windows system

Hai, The best info is missing. What are the windows event ID errors? What is the right set on the profiles folder? If you layout is : /home/samba/profiles and you shared the folder profiles, then show me getfacl /home/samba/profiles. I see your running, Samba 4.7, are you able to upgrade to 4.9.4? This: ~# cat default-rights-sysvol.acl # file: /var/lib/samba/sysvol # owner: root #

On 12/16/2013 08:01 PM, Charles Lepple wrote: > On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: > >> > Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >> > ai_socktype > [...] >> > The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't see what >> > could have changed. How do I attempt to further

On 12/16/2013 09:23 PM, Charles Lepple wrote: > Not sure - I didn't write the getaddrinfo() code in upsd, but it seemed to > follow all of the recommendations on how to use that function. So if there is > a way to fix it in the NUT code, I am not aware of it (and would appreciate > any updates if that turns out to be the case). > > The odd part is that it looks like you went

On Dec 16, 2013, at 10:11 PM, David C. Rankin wrote: > On 12/16/2013 08:01 PM, Charles Lepple wrote: >> On Dec 16, 2013, at 4:19 PM, David C. Rankin wrote: >> >>>> Dec 16 14:05:16 phoinix upsd[369]: getaddrinfo: Servname not supported for >>>> ai_socktype >> [...] >>>> The kernel update was from linux (3.12.1-3 -> 3.12.5-1), I don't

On 12/17/2013 10:43 AM, David C. Rankin wrote: > Huh? Why the : in Servname? So I just hardwired it passing the port "Servname" > as "3493" (could have just used "nut" from /etc/services): Sheepishly looking for a place to hide.... Yes there was a ':' there all right. Seems I was hit by a vi error: [12:04 phoinix:/etc/ups] # grep 3493 *.conf

Hello, I have a strange problem with Samba AD member: It is accessible via \\server or \\server.domain.local But when I try to access it with its IP address, ex. \\10.15.10.1 I get access denied error and prompt for user and pass. Entering username and password with or without DOMAIN\ has no effect. The server is FreeBSD 10.1. It behaves the same way with Samba 4.1.18 and now with Samba 4.2.2

Am 2017-07-10 um 12:08 schrieb Rowland Penny via samba: > I would change /etc/hosts to this: > > 127.0.0.1 localhost > 127.0.1.1 pre01svdeb01.my.tld pre01svdeb01 > > ::1 localhost ip6-localhost ip6-loopback > ff02::1 ip6-allnodes > ff02::2 ip6-allrouters > > But replace '127.0.0.1' with the real ipaddress of pre01svdeb01.my.tld > if

Hello. I'm in need of some help to shed some light on a strange problem. The box is running Samba 4.1.7 on FreeBSD 9.2/amd64 and I suspect (though I'm not sure) all troubles started after the upgrade from 4.1.6. The setup is quite simple: no AD, no LDAP, only one server. A command as simple as "smbclient -U user //SERVER/SHARE", if fired up several times in a row on the

I know more people posted about this , but i see no solution. smbstatus gives over 100 nobody users The windows 10 pc is doing nothing, just a reboot ( and logon ) , than this happens: Samba version 4.6.2 Centos 7. PID Username Group Machine Protocol Version Encryption Signing

> On 25 Jul 2016, at 19:49, Rowland penny <rpenny at samba.org> wrote: > > On 25/07/16 19:32, Kevin Davidson wrote: >>> On 25 Jul 2016, at 16:39, Rowland penny <rpenny at samba.org> wrote: >>> >>> On 25/07/16 16:02, Kevin Davidson wrote: >>>> Having problems with rfc2307 user ids. This was working briefly and now it’s not.

http://bugzilla.mindrot.org/show_bug.cgi?id=306 ------- Additional Comments From cmadams at hiwaay.net 2002-06-28 00:31 ------- I'm not seeing this on Tru64 4.0G or 5.1A with OpenSSH 3.4p1. What does "rsh [server]" say? Are you using IPv6? ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

Would someone please tell me where I can find some good troubleshooting documents to resolve AD authentication issues when using Samba? Is this mailing list the best place? I was able to setup a working WINBIND-Samba setup on CentOS 7.6, but I am required to use SSSD on a different CentOS 7.6 server. Using a test VM, I can get services running, but I can't authenticate from a Mac or

> On 25 Jul 2016, at 16:39, Rowland penny <rpenny at samba.org> wrote: > > On 25/07/16 16:02, Kevin Davidson wrote: >> Having problems with rfc2307 user ids. This was working briefly and now it’s not. >> >> samba and winbind v 2.4.2.10+dfs >> >> […] >> What have I done wrong? >> > > You haven't done anything wrong. > >

Hello openssh developers, I had built openssh-4.7p1 on arm-apple-darwin9 platform, but I get this error when I load sshd using launchd: root# launchctl load /Library/LaunchDaemons/com.openssh.sshd.plist errors on getaddrinfo(): nodename nor servname provided, or not known When I execute sshd directly, I don't get any warnings or error messages, but the sshd is not listening on the intended

--- .../smbdotconf/printing/spoolssbackchannel.xml | 16 ++++++++++++++++ source3/include/proto.h | 1 + source3/param/loadparm.c | 12 ++++++++++++ source3/rpc_server/srv_spoolss_nt.c | 6 ++++++ 4 files changed, 35 insertions(+), 0 deletions(-) create mode 100644

Hi... Out of sudden our samba file servers are no longer honoring secondary group membership. I appears that the fileservers are no longer seeing groups. When I do a 'net -U <domUser> rpc group list' on the PDC everything is fine. I can see all groups. When I do this on the fileservers I do not receive anything. We operate samba 4.3.9 both as classic PDC (for a couple of reason

Accepting only Unix sockets can be a bit limiting; let's be more flexible. Eric Blake (2): nbd: Refactor Unix socket connection nbd: Support TCP socket plugins/nbd/nbdkit-nbd-plugin.pod | 36 ++++-- plugins/nbd/nbd.c | 175 ++++++++++++++++++++++-------- TODO | 3 - 3 files changed, 161 insertions(+), 53 deletions(-) -- 2.20.1