Congratulations! I stand corrected. I said I thought upgrading wasn't
the route, but I guess you were right all along. Curious that I don't
see that behavior. Who knows what gremlins were biting you and not me
despite us having the same OS, Samba version and AD environment.
Hopefully Feisty Fawn will use newer Samba packages by default.
James A. Dinkel wrote:
Updating to 3.0.23c fixed it!! I didn't even change my config. I just
uninstalled the Ubuntu packages with "apt-get remove samba-common samba
winbind", added Samba.com's Debian Sarge repository and did "apt-get
update && apt-get install samba samba-common winbind" and it installed
the newer packages from the Sarge repo.
This fixed my nested domain groups problem, hopefully it didn't
introduce any new ones. I've only done this on my test server. After a
little more QA I'll do this on my semi-production server.
James Dinkel
--
To unsubscribe from this list go to the following URL and read the
instructions: https://lists.samba.org/mailman/listinfo/samba
