similar to: Samba 3.x Windows 8

Displaying 20 results from an estimated 8000 matches similar to: "Samba 3.x Windows 8"

2012 Jul 31
0
CEBA-2012:1126 CentOS 5 samba3x Update
CentOS Errata and Bugfix Advisory 2012:1126 Upstream details at : https://rhn.redhat.com/errata/RHBA-2012-1126.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 9a6fa2d1334aa8bafc93794a16be2c8c9b834e1aa6ebc3c44f4b5aa5c12ad5f6 samba3x-3.5.10-0.110.el5_8.i386.rpm
2012 Aug 01
1
CentOS-announce Digest, Vol 90, Issue 1
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2012 Aug 18
0
winbindd: socket dir
Hi List, Hunting around Google I've found a couple of references to using "winbindd: socket dir" in smb.conf to allow multiple winbindd instances to run but can't seem to find any doco on this feature. I have tried adding this to my smb.conf file but when I try to use ntlm_auth with this configuration any authentication fails and it returns: ntlm_auth --username=testusr
2012 Aug 18
2
Unable to use more than 1000 concurrent ntlm_auth processes
Hi List, I'm running a heavily loaded squid server that uses ntlm_auth to provide NTLM authentication. As load has increased over time, I've found the need to increase the number of ntlm_auth processes available to squid as well as the "winbind max clients" value in the smb.conf file. This has worked well up until now but seems I've hit some sort of limit. If I keep the
2011 Nov 29
0
CentOS-announce Digest, Vol 81, Issue 13
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2011 Sep 26
1
nss_winbind problem
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Well, I think this is not the only time you guys ever seen that kind of mails. First of all, I did checked all that is to be checked before writing to list. wbinfo -u and wbinfo -g work flawless. Also wbinfo -a, so I can authenticate without problems. The setup is a normal trust setup where domain X (my domain) trusts domain Y (another company).
2011 Sep 22
0
CESA-2011:1220 Moderate CentOS 5 x86_64 samba3x Update
CentOS Errata and Security Advisory 2011:1220 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1220.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) x86_64: d1af26928e5b3437ed117f2ffbef2cb3 samba3x-3.5.4-0.83.el5_7.2.x86_64.rpm 0277d8f285c5006f57ae9f3a50ceb8fc samba3x-client-3.5.4-0.83.el5_7.2.x86_64.rpm
2011 Sep 22
0
CESA-2011:1220 Moderate CentOS 5 i386 samba3x Update
CentOS Errata and Security Advisory 2011:1220 Moderate Upstream details at : https://rhn.redhat.com/errata/RHSA-2011-1220.html The following updated files have been uploaded and are currently syncing to the mirrors: ( md5sum Filename ) i386: 155e4c1fd8f4165e83e602cee07f3e68 samba3x-3.5.4-0.83.el5_7.2.i386.rpm cdaf234215185ad93ae0c773edb625e2 samba3x-client-3.5.4-0.83.el5_7.2.i386.rpm
2012 Apr 10
0
CESA-2012:0466 Critical CentOS 5 samba3x Update
CentOS Errata and Security Advisory 2012:0466 Critical Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0466.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: bd761bf38e7466f89f612824f8ac73fe2558ca218a1fca167285f525c2fd58da samba3x-3.5.10-0.108.el5_8.i386.rpm
2012 Apr 30
0
CESA-2012:0533 Important CentOS 5 samba3x Update
CentOS Errata and Security Advisory 2012:0533 Important Upstream details at : https://rhn.redhat.com/errata/RHSA-2012-0533.html The following updated files have been uploaded and are currently syncing to the mirrors: ( sha256sum Filename ) i386: 471f54ba5397283d3f5251590236e720589c28103b36630455e431e461d17961 samba3x-3.5.10-0.109.el5_8.i386.rpm
2012 Apr 11
0
CentOS-announce Digest, Vol 86, Issue 6
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2012 May 01
0
CentOS-announce Digest, Vol 87, Issue 1
Send CentOS-announce mailing list submissions to centos-announce at centos.org To subscribe or unsubscribe via the World Wide Web, visit http://lists.centos.org/mailman/listinfo/centos-announce or, via email, send a message with subject or body 'help' to centos-announce-request at centos.org You can reach the person managing the list at centos-announce-owner at centos.org When
2015 May 22
5
Samba4 Disable USB ports
Hello Gabriel, I recommend you use gpupdate /force on the windows command line after login. The results of above command can be checked afterwards with the "gpresults" command. Can be you have an permission problem on your samba server. Only skimmed ofver the thread but did you try samba-tools ntacl sysvolreset on your samba server? achim~ Am 22.05.2015 um 12:08 schrieb Gabriel
2015 May 22
5
Samba4 Disable USB ports
2015-05-22 13:32 GMT+02:00 Gabriel Franca <gabriel.franca at gmail.com>: > > I found it strange more and something I have already noticed a while. > > No GPO is applied when the User is the "Domain Users", so I wonder if I'm > doing something wrong or I have to change something. > > I believe the "Domain Users" are not allowed to change the
2015 May 22
1
Samba4 Disable USB ports
Hello Gabriel, Am 22.05.2015 um 15:23 schrieb Gabriel Franca: > Good morning people, > > I make the case that Achim Gottinger passed. > > samba-tool ntacl sysvolreset and received the following information: > Segmentation fault (core of the recorded image) > > then sent a samba-tool ntacl sysvolcheck and received the following: > ERROR (<type
2015 Apr 20
4
smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
Second request ... Thank you in advance ... - Mike Sent: Friday, April 10, 2015 2:16 PM To: samba at lists.samba.org Subject: smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1 We are having issues with smbclient 4.0.7 not working to clusters, because it's resolving the host name ( 'default service = dev3k1.my.domain.com' in smb.conf file ) to an IP address
2015 Apr 21
2
smbclient 4.0.7 resolves host name to IP address for SMB2 but not NT1
The problem is that I don't want it to use the IP address, but to use the hostname. Regards, - Mike ? ? -----Original Message----- From: samba-bounces at lists.samba.org [mailto:samba-bounces at lists.samba.org] On Behalf Of Rowland Penny Sent: Monday, April 20, 2015 10:38 AM To: samba at lists.samba.org Subject: Re: [Samba] smbclient 4.0.7 resolves host name to IP
2017 Jun 21
2
samba 4.4.14 breaks classic domain
Good catch. I had set server max protocol to NT1 after upgrading from samba 3.x to 4.x . Some windows clients had problems with SMB2 and file shares (tho this should not really be an issue with the domain controllers.) I have now set the dc's to server max protocol = SMB2 server min protocol = NT1 and the client machine to be client max protocol = SMB2
2015 May 22
2
Samba4 Disable USB ports
Good morning everyone, Gabriel: I haven't had a chance to test this yet, but I'm also needing the same IE: Domain Users to have the GPO applied. Did you come right with this? Andrey: Thank you for letting me know about the SysVol replication across DC's, I haven't enabled this yet and will be doing so, is there anything I should watch out for? I'll just be using the "
2015 Mar 04
4
server max protocol appropriate values
Hello, My DC smb.conf currently has the following set server max protocol = NT1 server min protocol = CORE client max protocol = NT1 client min protocol = CORE Is it safe to change both the client and server max to = SMB3? What about on member servers? Should I be concerned with anything breaking? I'm using Windows 7 clients to authenticate against Ubuntu