search for: datenverzeichnis

...comment = Benutzerprofile path = /d2/samba/profiles writable = yes browsable = no read only = no available = yes create mask = 0600 locking = no directory mode = 0700 read only = no [Daten] comment = Datenverzeichnis writeable = yes browsable = yes available = yes create mode = 0666 path = /d2/Daten directory mode = 0777 valid users = @users write list = @users hide unreadable = yes

...2.168.2.1 idmap_ldb:use rfc2307 = yes template shell = /bin/bash template homedir = /home/%U [netlogon] path = /var/lib/samba/sysvol/myworkgroup.local/scripts read only = No [sysvol] path = /var/lib/samba/sysvol read only = No [Daten] comment = Datenverzeichnis path = /d2/Daten read only = No hide unreadable = yes NOTE: you really shouldn't use '.local', if this really is your TLD, then stop Avahi from running on the DC. Next, go and read: https://wiki.samba.org/index.php/Setting_up_a_Share_Using_Windows_ACLs...

...late shell = /bin/bash > template homedir = /home/%U > >[netlogon] > path = /var/lib/samba/sysvol/myworkgroup.local/scripts > read only = No > >[sysvol] > path = /var/lib/samba/sysvol > read only = No > >[Daten] > comment = Datenverzeichnis > path = /d2/Daten > read only = No > hide unreadable = yes > >NOTE: you really shouldn't use '.local', if this really is your TLD, >then stop Avahi from running on the DC. > >Next, go and read: > >https://wiki.samba.org/in...

I have some identical windows 7 clients. All connected to Samba 3.5.4-1.1-2382-SUSE-SL11.0. If I'm the windows-owner of the file, swat shows me under "oplock" "exclusive+batch". Other users get: "none". What is the reason for this? ___________________________________________________________ Neu: WEB.DE De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt

...create mode = 0644 writable = yes comment = Eingangs-Fax-Queue path = /var/spool/fax/recvq [rootdir] create mode = 0644 writable = yes path = / [data] browsable = yes create mode = 0644 writable = yes comment = Datenverzeichnis path = /data public = yes [homepages] browsable = yes create mode = 0644 writable = yes comment = homepages path = /usr/local/apache/homepages public = yes ------------------------------------------------------------- There are no...

Hi, i upgrade to sles sp1 with sernet packages and get the following error after upgrade. Its looks like that port 135 will not reached. Anyone who have an information about that or a solution? Thanks Sven orion:~ # samba-tool drs showrepl Failed to connect host 192.168.24.2 on port 135 - NT_STATUS_CONNECTION_REFUSED Failed to connect host 192.168.24.2 (orion.domain.local) on port 135 -