similar to: Log: param/loadparm.c:widelinks_warning(4722)

Hi all. Need your help... I can join the domain normally. After restarting indicates that duplicate name exists on the network. When I try to log in, indicates that the domain is unavailable. I made two machines and get the message in both. I'm using Ubuntu 9.04 and configured using this tutorial:

Hi all. I'm having a serious problem with my samba/ldap server. It was working well till the last week and today stops definitly. Nothing has changed. Now my network is down and nobody can log in. When I restart samba: invoke-rc.d samba restart * Stopping Samba daemons... start-stop-daemon: warning: failed to kill 4436: No such process

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

I am with a problem to enter the server samba+ldap that I configured. When I go in Rwindow$ XP and I try to enter the domain, I type login and the password of root. If I type the password certain the error is ?was not possible to locate the uru?rio name?. If I type the password wrong the error is ?imperfection of logon: name of unknown user or incorrect password?. I looked for regarding the

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

Hi all. The user did not log in samba. Now, log in samba, how I make to keep the old profile? I don't want that a new profile is created. The username is the same. Thanks in advance. Sincerely Walmiro Muzzi _______________________________________________________ Yahoo! Mail - Sempre a melhor op??o para voc?! Experimente j? e veja as novidades.

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

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

Hi all. Please. Can somebody explain to me what's goin on with samba??? Thanks in advance! Aug 1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] lib/substitute.c:alloc_sub_basic(521) Aug 1 10:37:03 cronos smbd[28462]: alloc_sub_basic: NULL source string! This should not happen Aug 1 10:37:03 cronos smbd[28462]: [2007/08/01 10:37:03, 0] lib/fault.c:fault_report(36) Aug 1

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

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

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

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

On 10/08/2023 17.52, Philippe LeCavalier via samba wrote: > The solution is to update Samba to (security update to 4.17) so that 166 > (and possible 244) work from the client side. If you rely on a client side > solution you will likely continuously revisit this issue. I know I have to update Samba, but it's a hard job on a lot of small installations, and it requires quite a lot of

Here's a second set of diffs for sanity-checking smb.conf files. This one implements a basic set of checks on netbios names. No, it won't recognize someone using an ip address, but it will realize the dots don't belong: $ testparm Load smb config files from /usr/local/samba/lib/smb.conf WARNING: netbios name "127.0.0.1" contained a dot, which is only legal in DNS domain

> 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