similar to: Samba 3.6 security fixes

Thank you for the responses! Hi Helmut, I actually prefer moving into a newer version that has all the great new features, but due to policies inside our firm it will be a long process. I find the idea of modifying the new version Samba to start up like the old version. Very crafty! :) Hi Volker, yes we do have a support contract with Red Hat and Oracle. The version we are currently using is

So any Samba server version will work with Windows 10? What versions have been tested with Windows 10? We have a server at a site in Israel running 3.5.14, and Windows 10 systems are not able to access it. They get an error message when trying to connect to a share: "The specified network name is no longer available." Regards, Steve -----Original Message----- From: samba

Dear all, I wanna create a GNU/Linux that it boots from USB. I don't any idea on that. Can you introduce me a doc that i can use it & i can solve my problem? Cheers, -- ------------------------- Mohsen Pahlevanzadeh email address : mohsen at pahlevanzadeh.org web site : http://pahlevanzadeh.org IRC IM : m_pahlevanzadeh yahoo IM : linuxorbsd ----------------------------

Currently the resize command is under filesystem, and takes a path to the mounted filesystem. This seems wrong to me. Shouldn''t it be under device, and take a path to a device to resize? Otherwise, how can a resize operation when you have multiple devices make any sense? -- To unsubscribe from this list: send the line "unsubscribe linux-btrfs" in the body of a message to

Hallo, linux-btrfs, please delete the option "-L" (for labelling) in "mkfs.btrfs", in some configurations it doesn''t work as expected. My usual way: mkfs.btrfs -d raid0 -m raid1 /dev/sdb /dev/sdc /dev/sdd ... One call for some devices. Wenn I add the option "-L mylabel" then each device gets the same label, and therefore some other programs

Hallo, Luke, Du meintest am 02.04.16: > Also, when I run testparm -svv | less I can find these four lines on > both the working and non-working servers: > server max protocol = SMB3 > server min protocol = LANMAN1 > client max protocol = NT1 > client min protocol = CORE Perhaps a max protocol = NT1 in the global section helps. And

Is that with an active directory domain controller? On Apr 3, 2016 11:21 PM, "barış tombul" <bbtombul at gmail.com> wrote: > my conf win10 no problem: > client NTLMv2 auth = Yes > client lanman auth = No > server max protocol = SMB3_11 > server min protocol = LANMAN1 > client max protocol = SMB3_11 > client min protocol = CORE > >

Hallo, I use "isohybrid <myimage>.iso" for creating an *.iso which can boot from CD or from USB stick. Booting from CD works fine (since years). Booting from USB stick leads to ISOLINUX 4.04 ... EDD: Error 0400 reading sector ... No DEFAULT or UI configuration directive found! What goes wrong? Searching with google showed many such messages but (at least at the

Hi Helmut, Thank you for your mail. The distribution is Debian linux 7.9. I am talking of a fresh installation, and of course of it's update after. Thank you for helping. Regards Le 19 avr. 2016 06:08, "Helmut Hullen" <Hullen at t-online.de> a écrit : > Hallo, Jules, > > Du meintest am 18.04.16: > > > Is it recommended to install the tarball or archive

Hallo, Simon (and Andrew), Du meintest am 08.02.11: >> in the samba mailinglist there was a remark that samba 4 is designed >> only for the BIND nameserver; look escpecially at >> >> http://lists.samba.org/archive/samba/2011-February/160848.html >> >> I know that most programmers work in their "free" time (me too). But >> I don't like

Hallo, "never change a running system" ... For some months I run btrfs unter kernel 3.2.5 and 3.2.9, without problems. Yesterday I compiled kernel 3.3.4, and this morning I started the machine with this kernel. There may be some ugly problems. Copying something into the btrfs "directory" worked well for some files, and then I got error messages (I''ve not

Hallo, H. Peter, Du meintest am 25.06.13: >> We could probably fabricate a script of some sort to check for the >> required version of gnu-efi, and skip it if not found, unless the >> user explicitly requested that the EFI files be built, in which case >> we'd error out. >> >> Thoughts? > Not really... let's just document "make bios". By

Dear samba list, Is it recommended to install the tarball or archive version of samba4 in production ? Or what will be please the best pratices ? Thank you for your advices Best Regards -- Jules HOUANTONON *Phone* : (00229) 97578914 *Email *: juleshoueto at gmail.com *Skype* : houantonon *linkedin* : www.linkedin.com/in/jhouantonon/en

Hi all, I was wondering if anyone could help me, I have searched for some reason but cannot find any. After migrating from a previous samba-3.0.10 (I think) PDC server to a newer samba-3.0.23c server on Centos5, I have the strange problem that my XP clients no longer map all the drives listed in the logon.bat during logon, however if I run logon.bat manually after I'm logged in, all

On Mon, 24 Jun, at 06:27:00PM, Helmut Hullen wrote: > In file included from /tmp/syslinux-6.00/efi/mem.c:3:0: > /tmp/syslinux-6.00/efi/efi.h:33:5: error: unknown type name 'EFI_SERVICE_BINDING' [...] > Where is the problem: on the syslinux side or on the slackware side? Or > somewhere else? You need a newer version of gnu-efi, gnu-efi 3.0u, which is the release

On Tue, 25 Jun, at 01:09:47PM, H. Peter Anvin wrote: > Not really... let's just document "make bios". There's preliminary documentation in doc/building.txt. -- Matt Fleming, Intel Open Source Technology Center

Hi Everyone, Do we have an EOL date for version 3.6? I was looking into the Release Planning wiki and EOL is not yet defined. Thank you, Lester

Il 05/02/16 14:41, Helmut Hullen ha scritto: >> is: if a client is upgraded to Windows 10, will it still work with >> that old Samba version? > > May be - Samba 3.6 does the job. Hi, you mean that 3.2 will not talk to Windows 10, no way? Unfortunately the latest Samba version for Debian Lenny is 3.2.15 AFAIK. -- 01

SYSLINUX 4.00 2010-06-28 EDD Load error - Boot error Booting from USB on old IBM T43 or newer Esprimo E5731E. No problems with version 3.86 and same usb-stick.

I am trying to migrate samba from a box with Mandrake 10.1 with Samba 3.0.10 to a new box running CentOS 5.2 with Samba 3.0.28. The two versions of samba are too differnet to simply copy the config and tdb files over to the new box and the Mandrake box won't upgrade past 3.0.10. I could really use some suggestions. Thanks Greg