similar to: widelinks_warning - but unix extensions *are* off

> 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

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

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

> On 02.11.2015, at 20:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: > > On 02/11/15 17:08, Thomas Werschlein wrote: >>> On 02.11.2015, at 16:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: >>> >>> Well he didn't write what I asked for, can you please post your entire smb.conf, please do not use testparm, please post as

Sure, but did you even try my advice.. ?? So again.. from smb.conf unix extensions (G) allow insecure wide links (G) wide links (S) follow symlinks (S) G = Global S = Share So here you are lazy ... ( fill the dots..) ;-) Read below .... from : man smb.conf In normal operation the option wide links which allows the server to follow symlinks outside of a share path is automatically

Again... Global ONLY smb.conf options: unix extensions = No allow insecure wide links = Yes Per share ONLY smb.conf options: ## and share options niet global used. wide links = yes follow symlinks = yes unix extensions are enabled =>> wide links are disabled automaticly. Set : allow insecure wide links = Yes I dont see it in you smb.conf.. wide links = yes

Good afternoon. Today, after a printer is, all machines on the network accused "spooler is not running." With the printer removed, all other work once again. Now, some users are complaining that some files are not opening. I have checked the log of samba, and is continuing with this message: "9/27/2011 14:43:12, 0] param / loadparm.c: widelinks_warning (4722) Share 'IPC

> On 02.11.2015, at 16:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: > > Well he didn't write what I asked for, can you please post your entire smb.conf, please do not use testparm, please post as is (although you can sanitise any sensitive info) Sorry, missed that part. Here we go. Regards, Thomas [global] available = yes smb2 leases = yes

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

On 02/11/15 17:08, Thomas Werschlein wrote: >> On 02.11.2015, at 16:25, Rowland Penny <rowlandpenny241155 at gmail.com> wrote: >> >> Well he didn't write what I asked for, can you please post your entire smb.conf, please do not use testparm, please post as is (although you can sanitise any sensitive info) > Sorry, missed that part. Here we go. > Regards, Thomas

Hi all, We are trying to print the log messages pertaining to each share in a different log file for auditing purposes. We are using Samba v3.0.20b. We are trying to modify the file smbd/service.c::make_connection_snum() function by changing the log file full path. The code changes that is done are as follows: char logfilefullpath[70]; char sharename[256]; safe_strcpy_fn

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

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi, i recently upgraded some of my servers from 3.0.2a to 3.0.4 after the upgrade my browselist shows duplicate entries for the domains. one domains is managed by a samba PDC(providing WINS too) and two samba BDC's. the other domains are managed by one samba PDC. 'smbclient -N -L <WINS_SERVER>' shows: - --- Workgroup

I've been working for hours with Samba on Ubuntu Server 9.10 (Samba version 3.4.0), trying to get it setup simply as a fileserver that performs authentication to an NT 4 server (yes, I know, old and out of date). After much struggling, I finally realized that my configuration *was* working when the clients connecting (from XP, and Win2k clients, mostly) were actually joined to the domain

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

HI I have been working with NT, Samba and win 9x for a couple of years. Any time an NT server is set to Domain security, or a Samba server is set to anything but share level security I have problems. My problem is this. I want to allow a diverse groupe of machines to connect to the samba server using user level access, but it always askes me for a password to connect to \\SERVER\IPC$, but no

T.D.Lee@durham.ac.uk wrote: > > > But we'd like to go one step further and have the return code from preexec > be used to continue or abort the connection being established. The script > above would be modified to generate this return code. > > Looking through the source code (smbd/service.c), it doesn't seem to check > the return code (calling smbrun to do the

> 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