similar to: Share 'IPC$' has wide links and unix extensions enabled

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

> On Fri, 30 Sep 2016 12:14:44 -0400 (EDT) > schulz at adi.com (Thomas Schulz) wrote: > > > > 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: >

>> On Fri, 30 Sep 2016 12:14:44 -0400 (EDT) >> schulz at adi.com (Thomas Schulz) wrote: >> >>>> On Fri, 30 Sep 2016 10:14:32 -0400 (EDT) >>>> Thomas Schulz via samba &lt;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

Hi all Since we changed our installation from Samba 3.x to 4.x (currently 4.2.5 on Solaris 11.1), we repeatedly encounter the following 'widelinks_warning', originating from Windows Server 2012 R2 RDS clients: [2015/10/29 15:50:38.837702, 0] ../source3/param/loadparm.c:4306(widelinks_warning) Share 'data' has wide links and unix extensions enabled. These parameters are

> On 29 Oct 2015, at 23:22, Jeremy Allison <jra at samba.org> wrote: > > On Thu, Oct 29, 2015 at 05:27:49PM +0100, Thomas Werschlein wrote: >> Hi all >> >> Since we changed our installation from Samba 3.x to 4.x (currently 4.2.5 on Solaris 11.1), we repeatedly encounter the following 'widelinks_warning', originating from Windows Server 2012 R2 RDS

After an upgrade, I got re-bitten by the 'unix-extensions and wide links' incompat. (They used to be compat but were made incompat in the 3.4.x timeframe due to security concerns). At the time it was suggested I write a patch complete with documentation to describe the fix. The below seems to fit the bill. I was wondering what people thought about it's inclusion in future

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

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

> 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 Thu, Oct 29, 2015 at 05:27:49PM +0100, Thomas Werschlein wrote: > Hi all > > Since we changed our installation from Samba 3.x to 4.x (currently 4.2.5 on Solaris 11.1), we repeatedly encounter the following 'widelinks_warning', originating from Windows Server 2012 R2 RDS clients: > > [2015/10/29 15:50:38.837702, 0] ../source3/param/loadparm.c:4306(widelinks_warning)

I suggest you try something like. Global smb.conf options: unix extensions = No allow insecure wide links = Yes Per share smb.conf options: ## and share options niet global used. wide links = yes follow symlinks = yes > -----Oorspronkelijk bericht----- > Van: samba [mailto:samba-bounces at lists.samba.org] Namens Rowland Penny > Verzonden: vrijdag 30 oktober

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

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

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

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

Sorry for the delay and thanks for your pointers. "allow insecure wide links" does not change the behaviour, tried that before. Which is strange, if you look at the code. On the other hand it is clearly not a static misconfiguration, otherwise I would be able to reproduce it. About half of the time, we get a PANIC about 5 to 10 minutes after these strange widelinks_warnings appear in

We are having a problem that I suspect is due to nmbd giving out obsolete information. Unfortunately the problem can not be reproduced consistently. 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

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

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

>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