Displaying 6 results from an estimated 6 matches for "mabbs".
2013 Feb 25
7
"Samba 4" - "smbd"; "can't parse the PAC: NT_STATUS_BUFFER_TOO_SMALL" error but only for a single domain user ("Server 2008 R2" domain, "Server 2008" functional level forest).
...mation.
So can anyone suggest any way forward to resolve this please? It would
appear that something is incorrectly being decoded somewhere, so it's
probably to everyone's advantage to get this sorted out - I know it would
certainly be to mine :-)
Many thanks, and regards,
Tris Mabbs.
2013 Mar 02
5
Making Linux and domain users the same
I have a set of Linux boxes with (nearly) working Samba configurations. Windows users can get in and work with shares. My one problem is that the local user "joe" is not the same as the domain user that logs into Samba. And that means that users cannot access their own home directories, unless I relax the Linux permissions.
This is not surprising, given the way Samba was configured
2013 Aug 12
2
Odd Samba 4 ("4.2.0pre1-GIT-b505111"; actually only using client) behaviour #2 - "accept: Software caused connection abort".
Good day oh technical ones .
I was running Samba 4 (client only, not using it as a DC so
effectively running Samba 3 code from the Samba 4 tree) and, other than a
little "Gotcha!" regarding decoding Kerberos PACs, it was all working
perfectly.
Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111"
(I had to upgrade the OS on the server
2013 Sep 05
1
primary GID based access for user in 16 supplementary groups
We observe a difference between a Windows 7 client and Windows 2003/XP client when accessing directories that should be accessible via the UNIX accounts primary group GID. Windows client refuses access.
Ignoring for now why the two different client behaviours (either some subtle difference in the requests or the way the Samba reply is dealt with) the question is what should be the correct
2013 Aug 12
1
Odd Samba 4 ("4.2.0pre1-GIT-b505111"; actually only using client) behaviour #1 - "Could not fetch trust account password for domain ...".
Good day oh technical ones .
I was running Samba 4 (client only, not using it as a DC so
effectively running Samba 3 code from the Samba 4 tree) and, other than a
little "Gotcha!" regarding decoding Kerberos PACs, it was all working
perfectly.
Then recently I had to upgrade, to "4.2.0pre1-GIT-b505111"
(I had to upgrade the OS on the server
2014 Feb 12
0
Another odd problem - missing user and domain - with 4.2.0pre1-GIT-0ce4631 on "Solaris".
Good day all,
Another odd little problem; this has persisted through a lot
of recent versions, but posting earlier reminded me I need to mention this
as well .
Built a new version.
Cleared out all ".tdb" etc. files beneath "/var/samba/"
(which is where "locks", "lock", "log", . all sit on