Displaying 3 results from an estimated 3 matches for "weirdserver".
2018 Jul 25
3
Unable to contact active directory or verify claim types
...claim types." I do
NOT see this error message on when looking at folder properties on other
samba servers. It seems to be something unique to this one.
I tried querying group lists with "net" which pointed to the max server
protocol being a possible factor.
root at weirdserver:~# net groupmember list IT -U Administrator
Enter Administrator's password:
smb1cli_req_writev_submit: called for dialect[SMB3_11] server[127.0.0.1]
root at weirdserver:~# testparm -v
.
server max protocol = SMB3
.
root at okserver:~# net groupmem...
2018 Jul 25
0
Unable to contact active directory or verify claim types
...eric Vandal <gaiseric.vandal at gmail.com> wrote:
> My partial smb.conf and nsswitch.conf is as follows. FYI the user in
> question is able to access directories via ssh so the permissions and
> group membership seems correct - at least on the unix level.
>
>
> root at weirdserver:~# getent passwd | grep myname
> myname:x:123:999::/home/myname:/bin/bash
> MYDOMAIN\myname:*:123:999:My Name:/home/MYDOMAIN/myname:/bin/false
> root at weirdserver:~#
>
> Rebooting the Win 2012 R2 server did fix the network share access
> caused by changing the max protocol.
>...
2018 Jul 25
0
Unable to contact active directory or verify claim types
I set "server min protocol = SMB2" and "server max protocol = SMB2" .
Which then resulted in the Win 2012 R2 server being unable to access the
Samba server as \\weirdserver <file://weirdserver> . But I can access via
\\weirdserver.mydomain.com <file://weirdserver.mydomain.com> or \\ipaddres
<file://ipaddres> .
Logs on samba server for that client shows "bad SMB2 signing."
[2018/07/24 22:34:19.865792, 3]
../source3/smbd/smb2...