similar to: can "root" still connect clients to a domain?

Hallo, I wrote am 26.06.13: > Running "pxelinux": more problems than with 5.10. > 5.00-pre6: all worked fine > 5.10: the start menu (GUI) wasn't shown; "tab" showed the labels, and > the textual menus. Invoking the labels worked. > 6.00: no GUI start menu. "tab" showed the textual menus. Invoking > them seems to do nothing (after some

Hi, I have the same problem as Helmut with INCLUDE keyword and extlinux 5.10 an later. The following configuration has been tested and worked with extlinux 4.05, 4.06, 5.01 Contents of "boot_label" file DEFAULT 1 --------------------------------------- Contents of "extlinux.conf" file # Enable menu.c32 UI menu.c32 # Disable the boot: prompt PROMPT 0 # 5 sec TIMEOUT 50 #

Hallo, on a school server in the neighbourhood Samba 3.0.22 (only SMB server, "security = server") serves many Windows2000/XP clients in their classrooms. The last lesson on a friday ends at 13:35, then the pupils shut down the clients and leave the room. In /var/log/warn follows -------------------------------------- Sep 7 13:39:37 Arktur smbd[31514]: read_data: read

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

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

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

Hallo, I've just tried to compile Samba 4.0.0alpha14 under Slackware 13-current - it failed. 206 warnings, 257 errors, and last famous words ---------------- cite on --------------- [2152/2374] Linking default/source4/heimdal_build/libroken-samba4.so [2153/2374] Linking default/source4/heimdal_build/libasn1-samba4.so /lib/libcom_err.a(error_message.o): In function `et_list_unlock':

Hallo, for a school server I'd like the option write list = "/path/to/class-8a-list" for the share [class-8a] Ok - I can work with [class-8a] ... include "/path/to/writelistdefinition.txt" ... but that's more ugly. Viele Gruesse! Helmut

On 04/19/2016 1:44 PM, Helmut Hullen wrote: > Hallo, Dale, > > Du meintest am 19.04.16: > >>> Found some more info: >>> >>> mount.cifs to mount shares from my DCs (samba 4.2.11) works >>> mount.cifs to mount shares from smbserver (also 4.2.11) does NOT >>> work. > [...] > >>> As for smb.conf options: similar on the DCs and the

> Hallo, Matt, > > Du meintest am 25.06.13: > > >> Not really... let's just document "make bios". > > > There's preliminary documentation in doc/building.txt. > > (sent to you and to the mailing list; some robot blocks the list ...) > > Additionally: > > Compiling (with "make bios") worked. > > Running

Hallo, can I use pxelinux for booting a notebook via WLAN? Viele Gruesse! Helmut

On 05/19/2016 11:09 AM, Helmut Hullen wrote: > Hallo, ToddAndMargo, > > Du meintest am 19.05.16: > >>>>>> Is there anything in Samba that will help protect >>>>>> against ransomware? > > [...] > >>> months ago there where ransomware which discovered shares without a >>> drive letter assigend > >> yes, I just read

Hallo, I'm using Samba 3.0.36, 3.2.13 and older. My "smb.conf" (stripped): [global] server string = c't/ODS-Schulserver %h mit Samba %v workgroup = WORKGROUP # ... domain logons = yes logon script = logon.bat logon home = \\%L\%U # nur f?r Windows 9x logon path = \\%L\Profile\%U\%a logon drive = U: hosts allow = 127., 192.168., 172.16.0.0/12, 10. lanman auth =

Hallo, I'm trying to convert smbpasswd to passdb.tdb. cd /etc/samba/private # (where smbpasswd lies) pdbedit -i smbpasswd -e tdbsam:/etc/samba/private/passdb.tdb converts all human users, but it converts (or transfers) no machine account. In "smbpasswd" are many entries beginning with (p.e.) mac001$ for these accounts, pdbedit -L -v | grep -i mac shows

Hallo, syslinux, I've just tried to compile syslinux 4.04 for slackware - it stopped when it tried to execute Entering directory `/path/to/diag/geodsp' ./mk-lba-img lba.img "strace" shows execve("./mk-lba-img", ["./mk-lba-img", "lba.img"], [/* 49 vars */]) = - 1 ENOEXEC (Exec format error) dup(2) = 3

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

Hallo, one of my colleagues has problems with Samba (V 3.0.32). Samba runs on a Linux server (Slackware 2.6.29.6), some clients are attached via a Windows Terminalserver. Wiederum war auf dem Windows-TS 1(!) User in die Arktur3.6 -Dom?ne f?r ca 20 Minuten angemeldet und hat dabei ca 4400 Meldungen in die /var/log/messages geschrieben. Diese beginnen mit: (my bad translation: 1 client was

Hallo, Matt, Du meintest am 25.06.13: >> Not really... let's just document "make bios". > There's preliminary documentation in doc/building.txt. (sent to you and to the mailing list; some robot blocks the list ...) Additionally: Compiling (with "make bios") worked. Running "pxelinux": more problems than with 5.10. 5.00-pre6: all worked fine

Hallo, I wrote am 26.06.13: >> Running "pxelinux": more problems than with 5.10. >> 5.00-pre6: all worked fine >> 5.10: the start menu (GUI) wasn't shown; "tab" showed the labels, >> and the textual menus. Invoking the labels worked. >> 6.00: no GUI start menu. "tab" showed the textual menus. Invoking >> them seems to do