Displaying 6 results from an estimated 6 matches for "firstgrade".
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".
...teway smbd[24378]: [ID 702911 daemon.error] [2014/02/12
19:44:11.498634, 0]
../source3/auth/auth_domain.c:302(domain_client_validate)
Feb 12 19:44:11 Gateway smbd[24378]: [ID 702911 daemon.error]
domain_client_validate: unable to validate password for user in domain to
Domain controller GEDIMAN.FIRSTGRADE.CO.UK. Error was
NT_STATUS_INVALID_PARAMETER.
Feb 12 19:44:12 Gateway smbd[24381]: [ID 702911 daemon.error] [2014/02/12
19:44:12.718457, 0]
../source3/auth/auth_domain.c:302(domain_client_validate)
Feb 12 19:44:12 Gateway smbd[24381]: [ID 702911 daemon.error]
domain_client_validate: unable to va...
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 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).
Hello,
We're having a problem with "Samba 4" joined to a "Server 2008 R2" domain
(at "Server 2008" functional level across the forest).
The interesting thing is that this only affects a single user - all other
accounts work without problems.
When accessing our main server using that account, "smbd" always reports
"can't parse the PAC:
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
2014 Feb 12
0
Odd "force user =" behaviour in 4.2.0pre1-GIT-0ce4631 on "Solaris".
Good day everyone,
So here's a strange thing .
Thought I'd update my Samba (client code only) installation
in case some of the things I've been involved in discussing have had their
fixes make their way into the code base yet (not logging the million-and-one
"accept()" errors which crop up on Solaris at debug 0, and correctly
interpreting