similar to: Workgroup name too long

>> From: Reindl Harald <h.reindl at thelounge.net> >> To: samba at lists.samba.org >> Date: 02/25/2015 02:52 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >> >> >> Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >>>> I have searched for this and the solutions I found were

Am 25.02.2015 um 22:48 schrieb Miguel Medalha: >> I have searched for this and the solutions I found were for instances >> where the workgroup name *was* too long. However, my workgroup name is >> *not* too long. The spaces between PEGASUS and ^[ are part of the >> message, I did not add them. If you count them there are 16 total >> including ending ^[. I

samba-bounces at lists.samba.org wrote on 02/25/2015 02:51:28 PM: > From: Reindl Harald <h.reindl at thelounge.net> > To: samba at lists.samba.org > Date: 02/25/2015 02:52 PM > Subject: Re: [Samba] Workgroup name too long > Sent by: samba-bounces at lists.samba.org > > > > Am 25.02.2015 um 22:48 schrieb Miguel Medalha: > >> I have searched for this and

I have searched for this and the solutions I found were for instances where the workgroup name *was* too long. However, my workgroup name is *not* too long. The spaces between PEGASUS and ^[ are part of the message, I did not add them. If you count them there are 16 total including ending ^[. I can't figure out where the spaces are coming from. This is the same for every Samba

> On Fri, 19 Apr 2019 10:26:09 -0600 > durwin at mgtsciences.com wrote: > > > > > > > > > > > Centos is RHEL recompiled and as such, it will suffer from the same > > > problems as Fedora (some people call Fedora, RHEL testing) from the > > > Samba point of view. Basically, if you are going to change distro, > > > you need to find

Ever since installing Fedora 7, samba stopped showing the machine on the network. I can connect to it by entering the machine name (\\lazarus), but it will not show itself from a Windows machine. I tried a command suggested to test if it was listening and this is what I got; $ smbclient -L localhost -U% Domain=[LAZARUS] OS=[Unix] Server=[Samba 3.0.25b-2.fc7] Sharename Type

> > > > > > There are two opensource kerberos servers, one is MIT, which is the > > > default on red-hat distros, the other is Heimdal, which is the > > > default for Samba. After a lot of work, Fedora is now using MIT > > > with Samba, but there is still a lot more to do, so it is > > > recommended to only use the Fedora packages for testing

I have hollowed these instructions. https://github.com/thctlo/samba4/blob/master/full-howto-Ubuntu18.04-samba-AD_DC.txt My normal domain is company.com. For the Samba domain it is msi.company.com. DNS is working. I ran these commands. host -t SRV _ldap._tcp.msi.company.com. _ldap._tcp.msi.company.com has SRV record 0 100 389 dc0.msi.company.com. host -t SRV _kerberos._udp.msi.company.com.

I have read the shutdown.txt in the docs directory. It says that after upsmon calls the shutdown command init takes over. This I understand clearly. However, step 8. 8. init then runs your shutdown script. This checks for the POWERDOWNFLAG, finds it, and tells the UPS driver(s) to power off the load. Since init is shuting down the system, why is the POWERDOWNFLAG needed? Why do I

I have all working and the test shutdown using 'upsmon -c fsd' worked. Also I get appropriate messages on console when I pull power and restore. But I want to *see* it work by removing power, but I don't want to wait. How can I tell UPS to issue needed message after a minute on battery? Durwin F. De La Rue Management Sciences, Inc. 6022 Constitution Ave. NE Albuquerque, NM 87110

> From: Rowland Penny via samba <samba at lists.samba.org> > To: samba at lists.samba.org > Date: 04/19/2019 08:29 AM > Subject: Re: [Samba] GPO Filtering Denied > Sent by: "samba" <samba-bounces at lists.samba.org> > > On Fri, 19 Apr 2019 08:00:32 -0600 > Durwin via samba <samba at lists.samba.org> wrote: > > > I followed Part 1, Part

> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) > Thomas Schulz via samba <samba at lists.samba.org> wrote: > > > We are running Samba 4.4.6 as a file server. > > In the logs for a few client machines I see entries such as: > > > > [2016/09/29 22:36:58.862575, 0] > > ../source3/param/loadparm.c:4402(widelinks_warning) > > Share 'IPC$'

> > > > > > Is this dns server also authoritative for the same dns domain as > > > the AD domain ? > > > > Yes, the Fedora29 server is authoritative. > > > > > > > > > > > Lets start with the smb.conf from the DC, your DC's FQDN and > > > ipaddress (sanitised if you have to) and the same for your Fedora

> On 2/16/2015 10:14 AM, Thomas Schulz wrote: >>> My apologies for being too new to this whole process... >>> >>> Server was AIX 5.3/Samba 2.2.7, authenticating only against the AD. No >>> single sign-on, kerberos, or LDAP to my knowledge; smbd processes never >>> load kerberos or LDAP libraries. Upgraded to AIX 7.1/Samba 3.3.12, which >>>

> > Good morning. > > I am looking to resolve the above vulnerability on our T-4 Solaris boxes. I have not worked or patch Samba before and not sure of the process. > > When I find and apply the patch will it resolve the issue on the version that we are running or do I need to bring our current version more up to date? > > Any assistance would be greatly appreciated.

> On 21/04/15 09:17, Peter Grotz - Obel und Partner GbR wrote: > > Hallo, > > > > > > > > samba 4.2 is released for some time now. Sernet usually doesn?t take a lot > > of time to release their new packages. > > > > But now we haven?t heard a peep from them. Are they gone or will there be > > another fine release? > > > >

>From a discussion on samba technical about the inability to have Samba work as a DC when the original DC is a Windows Server 2000 machine. > > as Andrew asked you previously, the main question is : do you have some > > specific requirements for keeping a DC on that computer (eg. Exchange or > > whatever)? > > > > If you don't need to keep the DC role on

This problem shows up on both Linux and Solaris. I am going to show the logs from a Fedora 2.6.25-14.fc9.i686 machine. We are using 'security = domain' with a Windows 2000 domain controller. We are setting 'password server = starfish2' dispite the fact that the documentation says that this in not necessary as we have found it to be necessary. We are setting 'workgroup =

> On Fri, Aug 26, 2016 at 12:19:30PM -0400, Thomas Schulz via samba wrote: > > I am testing Samba 4.5.0rc2 on a Solaris 10 i386 box. log.smbd contains > > a new message/error that does not show up on Samba 4.4.5. The error is: > > > > [2016/08/26 11:45:54.886237, 0] > > ../source3/rpc_server/rpc_service_setup.c:539(dcesrv_ep_setup) > > dcesrv_ep_setup:

Arter managing to build Samba 4.1.5 on Solaris 10 i386. I tried to join an existing Windows 2000 Server Active Directory domain as an additional domain controller. The join started to work and then died with the error: Error: Samba was compiled without the posix ACL support that s3fs requires. Try installing libacl1-dev or libacl-devel, then re-run configure and make. I downloaded acl-2.2.52 and