similar to: nmbd keeping old data

> Hello Thomas, > > Am 29.01.2015 um 18:12 schrieb Thomas Schulz: > > We have a build system that runs on our Solaris machines where the final > > files are copied into a distribution directory after being built. Note > > that copying a new file on top of an old one does not change the file ID. > > > > PC users sometimes will see the file as having the date

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 =

>> 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

> 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$'

This may not be a Samba problem, but perhaps people here know the answer. We are installing some Windows 8.1 Pro computers. The servers running Samba 4.2.19 and 4.3.0 are not showing up in the Network display. Our domain controller is also not showing up. The Windows 7 computers are showing up. The domain controller is a Windows 2000 machine. I can manually map network drives to the servers

> 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 >>>

> 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: schulz at adi.com (Thomas Schulz) >> To: durwin at mgtsciences.com, h.reindl at thelounge.net, > samba at lists.samba.org >> Date: 02/25/2015 06:39 PM >> Subject: Re: [Samba] Workgroup name too long >> Sent by: samba-bounces at lists.samba.org >> >>>> From: Reindl Harald <h.reindl at thelounge.net> >>>> To: samba at

> > 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.

I joined a Fedora Linux box running Samba 4.1.5 to a Windows Server 2000 domain controller as an additional domain controller with the command: samba-tool domain join adi.com DC -Uadministrator --realm=adi.com --dns-backend=BIND9_DLZ The messages indicated that this was mostly sucessfull with the exception of the message: NO DNS zone information found in source domain, not replicating DNS

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

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$' has wide links and unix extensions enabled. These parameters are incompatible. Wide links will be disabled for this share. I assume that Share 'IPC$' is some sort of

When Samba goes up a more major version (such as from 4.4.* to 4.5.*), they sometimes rearrange what files go in what directories. The best way to avoid trouble is to clean out the old version before installing the new one. If you build Samba to be installed in something like /usr/local then it is easy to remove the old files before installing the new ones. If you build Samba to go into the system

>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

For anyone wanting to build and install Samba on a Solaris machine: I have successfully built and installed Samba 4.1.4 on a Solaris 10 i386 machine. You will have to build and install a newer version of Python before you can configure Samba. You must configure Python with --enable-shared. See bug 10261 at bugzilla.samba.org for the details of why that is. If you are going to build Samba with the

> 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 > didn't go smoothly; customer is upgrading to Windows Server 2012 AD in a > couple of

There must be something that I am missing here. We have been running Samba 3.6.18 and I decided that it was time to check out Samba 4.1.4. Now that I have it, what do I do with it? I have found the man pages, but I was expecting that there would be some overview available somewhere. The first question that I could not find an answer for was what directory do I put the smb.conf file in. I found the

Adding a section of a debug level 5 log at the end that looks like it might have some usefull information. > 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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 The packages are online :-) Am 21.04.15 um 16:53 schrieb L.P.H. van Belle: > thats still the case with the packages but.. 4.2.1 wil build on > jessie fine. ( from source ) Did that today. > > > Gr, > > Louis > > >> -----Oorspronkelijk bericht----- Van: rowlandpenny at googlemail.com >>

> 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: