search for: gjcarter2

On Fri, 10 Jan 2025 15:07:34 -0700 Gregory Carter <gjcarter2 at gmail.com> wrote: > Well, if I eliminate the ipv6.disable-1 from the kernel command line > everything works fine. So I don't think it is a samba config issue > per se, unless of course I need something specific for kpasswd5 port > 464, but in any case. > > This AD ser...

...ing more closely at the syntax, maybe I need a subnet after the second IP address to make that work. I will be looking at that tonight. On Sat, Jan 11, 2025 at 1:38?AM Rowland Penny via samba < samba at lists.samba.org> wrote: > On Fri, 10 Jan 2025 15:07:34 -0700 > Gregory Carter <gjcarter2 at gmail.com> wrote: > > > Well, if I eliminate the ipv6.disable-1 from the kernel command line > > everything works fine. So I don't think it is a samba config issue > > per se, unless of course I need something specific for kpasswd5 port > > 464, but in any case...

...e I need a subnet after the second >IP address to make that work. > >I will be looking at that tonight. > >On Sat, Jan 11, 2025 at 1:38?AM Rowland Penny via samba < >samba at lists.samba.org> wrote: > >> On Fri, 10 Jan 2025 15:07:34 -0700 >> Gregory Carter <gjcarter2 at gmail.com> wrote: >> >> > Well, if I eliminate the ipv6.disable-1 from the kernel command line >> > everything works fine. So I don't think it is a samba config issue >> > per se, unless of course I need something specific for kpasswd5 port >> >...

Well, if I eliminate the ipv6.disable-1 from the kernel command line everything works fine. So I don't think it is a samba config issue per se, unless of course I need something specific for kpasswd5 port 464, but in any case. This AD server is a Fedora 41 box running root at ad:~# uname -ra Linux ad.example.com 6.11.10-300.fc41.x86_64 #1 SMP PREEMPT_DYNAMIC Sat Nov 23 00:51:20 UTC 2024

I noticed that kpasswd5 (port 464) isn't showing up on subnets where IPv6 is not allowed. So I cannot do any joins for these Linux boxes. Is there a Global switch I can use for samba to just startup and listen on IPV4 only? It seems inconsistent as all the other services don't seem to be affected by this switch and appropriately bind to the interface. How do I get kpasswd5 up on IPV4

I believe RC4 is the default Samba side. I had to create a policy on the workstation to enable cipher RC4 to correct the issue. The latest update to Windows 11 doesn't accept RC4 anymore. Another option I tried was backing out of the updates which also worked. My laptop SSD died however and I lost my diagnostic tools. Perhaps you could try changing the cipher Samba side for these new