Help - Zoeken - Gebruikers - Kalender
Volledige versie: Twee mandriva's aan elkaar knopen
MandrivaClub.NL > Forum > Servers en netwerken
qpatrick
Het lukt me maar niet om twee mandriva's (2007) met elkaar te laten kletsen, de ene mandriva kletst wel met de oude windows installatie.

Wat is de handigste en stabielste mogelijkheid om twee mandriva elkaar te laten zien en data uit te wisselen. Die windows installatie gaat er toch af, dus het hoeft niet met Samba.
Heeft iemand ergens een tutorial die dit uit de doeken doet ?

Alvast bedankt !

Patrick
doelman
Het kan met Samba, NFS, Sftp, ftp en er zijn vast nog wel meer mogelijkheden smile.gif
qpatrick
Dan zal het voornamelijk tussen de twee eerste gaan denk ik dan zo...
FTP lijkt me niet zo heel funtioneel hiervoor....

Ben nu nog ff bezig met Samba proberen werkend te krijgen, want dat staat er toch al op, of zijn er wezenlijke voordelen voor nfs ?

SnorkelBoy
is het misschien een idee om via SSH een tunneltje te leggen?

Wellicht dat het fish-protocol iets voor je is?

Ik kan me herinneren (oud draadje) dat je al eerder via ssh en rsync de boel aan elkaar hebt kunnen hangen.

Kortom: Als je alleen bestanden wil delen is SSH met de juiste sleutel-paren misschien een idee. Als je nog meer wil kun je dat wellicht even specificeren... icon_idea.gif

Arno
rockingbilly
(qpatrick @ Mar 14 2007, 03:18 PM) [snapback]80842[/snapback]

Dan zal het voornamelijk tussen de twee eerste gaan denk ik dan zo...
FTP lijkt me niet zo heel funtioneel hiervoor....

Ben nu nog ff bezig met Samba proberen werkend te krijgen, want dat staat er toch al op, of zijn er wezenlijke voordelen voor nfs ?

Ik knoop alles aan elkaar via samba.
Vooral ook omdat ik soms nog een paar virtuele machines heb draaien met Windows XP erin, en die kun je toch via samba het best benaderen.
JClosed
Ik gebruik zowel Samba, NFS als FTP....

Vergeleken bij FTP is Samba relatief langzaam. Als je FTP op de max speed van je netwerk zet, zal het transport ook op volle snelheid gaan. Samba is naar mijn gevoel een stuk langzamer en het overzetten van een (flinke) file duurt het naar mijn gevoel allemaal een stuk langer. Daarnaast kent Samba nóg een hele grote beperking. De filesize is maximaal 2Gb!! Overzetten van een grotere file gaat gegarandeerd mis. Een goede snelheidsvergelijking met NFS heb ik nog niet gedaan, aangezien ik de laatste niet echt comfortabel in gebruik vindt...

Voor Samba gebruik ik Webmin voor de configuratie en Smb4k als (wederzijdse) client. Voor FTP gebruik ik GPROFTPD in combinatie met ProFTPD v. 1.3.0 voor configuratie en gFTP als client.

Voor beiden is het mounten en unmounten van een "share" eenvoudig. Bij NFS moet je een share mounten als netwerkdrive. Dat gaat wat lastiger aangezien je geen "client" hebt. Je moet dan mounten vanuit het MCC en dat vindt ik nogal omslachtig...

Qua veiligheid is alles relatief goed in de hand te houden. Voor Samba gebruik ik een aparte gebruiker, zodat de toegankelijkheid zeer beperkt blijft. Voor FTP gebruik ik een directory (bij diezelfde gebruiker) die redelijk goed afgeschermd is (is heel goed te doen met GPROFTPD). Daarnaast gebruik ik uiteraard een firewall-setting die dit lokale verkeer afschermt van de boze buitenwereld...

Tot zover mijn ervaring op dit gebied...
doelman
(JClosed @ Mar 14 2007, 08:04 PM) [snapback]80866[/snapback]

Daarnaast kent Samba nóg een hele grote beperking. De filesize is maximaal 2Gb!! Overzetten van een grotere file gaat gegarandeerd mis.

Dat is volgens mij niet waar, ik heb regelmatig bestanden groter dan 2GB gekopieerd via Samba, en nooit is er iets mis gegaan.
JClosed
Tja - bij mij gaat het altijd mis. Ik gebruik Samba voornamelijk als "hulpje" bij VMware server. Omdat die dan toch "draait" gebruik ik het ook voor transport tussen twee Mandriva "bakjes". Ik heb me niet echt verdiept in hoe en waarom het mis gaat bij mij. Ik dacht (simpel gedacht - ik geef het toe) dat het een beperking betrof van het op windows gebaseerde protocol dat (in deze vorm) nog stamt uit de tijd van FAT32 en de 2Gb beperking dat dit filesysteem kent. Mijn gedachte was dat aangezien FAT32 deze beperking kende, het transportprotocol geen noodzaak kende tot bestanden groter dan 2Gb. Achteraf natuurlijk verkeerd gedacht, want NTFS stamt natuurlijk ook uit die tijd...

Affijn - ik maak(te) me er ook niet verder druk over aangezien FTP voor mij sneller werkt en geen beperking van de bestandsgroottte geeft...

Maar misschien eens goed om uit te zoeken hoe dit nu zit.. Leuk uitzoekertje voor een verloren uurtje... icon_cheesygrin.gif
rockingbilly
(doelman @ Mar 14 2007, 08:06 PM) [snapback]80867[/snapback]

Dat is volgens mij niet waar, ik heb regelmatig bestanden groter dan 2GB gekopieerd via Samba, en nooit is er iets mis gegaan.

Ik kopieer ook regelmatig bestanden 2GB+ (images bijv. van 4GB of groter). Dat gaat prima met samba.
RvP
Het topic begint dat het niet lukt om 2 mandriva pc's met elkaar te verbinden met samba.
Ik heb ze hier allemaal (dualboot) met samba in een netwerk en het maakt niet uit hoe je inlogt, je kunt altijd de pc's op het netwerk zien en de printer bedienen. Wat lukt er niet? zet anders je smb.conf hier eens neer.
Zoeken op samba op dit forum levert ook veel informatie op.
JClosed
(RvP @ Mar 14 2007, 08:38 PM) [snapback]80873[/snapback]

Het topic begint dat het niet lukt om 2 mandriva pc's met elkaar te verbinden met samba.
Ik heb ze hier allemaal (dualboot) met samba in een netwerk en het maakt niet uit hoe je inlogt, je kunt altijd de pc's op het netwerk zien en de printer bedienen. Wat lukt er niet? zet anders je smb.conf hier eens neer.
Zoeken op samba op dit forum levert ook veel informatie op.


Hmm.. niet helemaal waar...

Er staat: "Die windows installatie gaat er toch af, dus het hoeft niet met Samba.". Dat is in mijn ogen een duidelijk statement dat Samba niet verplicht is. Vandaar dat er ook alternatieven voor Samba werden aangedragen...

RvP
(JClosed @ Mar 14 2007, 08:43 PM) [snapback]80875[/snapback]

Hmm.. niet helemaal waar...

Er staat: "Die windows installatie gaat er toch af, dus het hoeft niet met Samba.". Dat is in mijn ogen een duidelijk statement dat Samba niet verplicht is. Vandaar dat er ook alternatieven voor Samba werden aangedragen...

Alternatieven zijn altijd welkom (hopelijk leest Bill Gates dit ook icon_greedy.gif ).

Het topic begint met
Het lukt me maar niet om twee mandriva's (2007) met elkaar te laten kletsen

gevoegd bij
het hoeft niet met Samba
Doet mij ernstig vermoeden dat reeds geprobeerd is eea met Samba voorelkander te krijgen.

Poirot ;).gif

Zeker en vast kan de topicstarter hier iets zinnigs over bezigen. Speculeren doen we maar op de beurs. ;).gif
Tux Brothers
Hey Patrick smile.gif

Samba, is lekker snel en veilig, en dat met die 2GB limit is totale onzin, ik sleep bestanden van meer dan 9GB eroverheen en nooit problemen.

FTP kan ook maar is niet erg veilig en je moet aan beidde zijden een FTP server laten lopen.

Webdav over SSL, is denk ik 1 van de mooiste oplossingen, is snel veilig en kan ook van buitenaf als extra diskruimte benaderd worden, wel moeilijk te installeren.

NFS is supersnel maar totaal geen beveiliging.

SSH, super veilig niet zo snel, makkelijk op te zetten en met Konqueror heel makkelijk te benaderen.

USB sticky, makkelijk en heeeel veilig icon_cheesygrin.gif

Maar ff zonder dollen dit zijn wel een beetje de gangbare oplossingen en ik weet niet precies waarvandaan jij je bestanden wilt benadere (LAN maar wellicht in de toekomst ook WAN?)
qpatrick
Het gaat simpelweg over een Lan netwerk. En als ik de reacties hier zo lees is Samba wel het makkelijkst om in te regelen. En heeft het niet al teveel nadelen. En inderdaad handig om in de toekomst een virtueel windows te gebruiken.

De grootste nadeel zou zijn van die 2 GB limiet. Maar ditl ijkt me een oud probleem is ondertussen is verholpen. Dus nu staat me niets meer in de weg om Samba werkend te krijgen op mijn laptopje...

Ik heb hier alleen een oude tutorial uit de knowledge base gevonden. Hier owrdt nog gesproken over Mandrake en wordt het uitgelegd aan de hand een mandrake 10.x systeem

Het belangrijkste is natuurlijk de pakketjes:
ik heb het volgende erop staan:

Webmin
swat
samba server
samba client
samba common

Na het installeren van webmin eerst deze service gestart:
# service webmin start

en met de browser naar localhost:10000
Het eerst waar ik ff op vastloop ik de inlog van Webmin.....
Welke user moet ik hiervoor gebruiken...Wat ik ook probeer ik wordt niet ingelogd.... en dat is toch vervelend als de config file wilt aanpassen....

Ben ik nu al stappen vergeten ? of heb ik alles geïnstalleerd wat ik nodig heb ?
Alvast bedankt voor alle reacties icon_idea.gif
RvP
Zonder webmin en swat te hoeven gebruiken:
Stel in MCC in dat iedere gebruker mappen mag delen.
Ga naar systeem - configuratie - KDE -internet/netwerk - samba, en stel daar samba in, o.a. hoe je je computer in het netwerk gaat heten. Moet wel als root en dat heeft MDV met 2007 wat lastiger proberen te maken. Op dit forum vindt je wel hoe het moet, anders een PM sturen.
Ga met Konquerer naar de folders die je wilt delen en voila, de folders zijn zichtbaar op je netwerk.
2007 zet helaas wel iets te veel in de conf file, waardoor (ik o.a.) niet 123 het gewenste resultaat hadden. Je conf (zie de Forum rubriek netwerken voor topics) daarna kaal maken met alleen het hoogst nodige en je hebt een werkend syteem.

Volgens mij is er trouwens niet veel (geen) verschil tussen Mandrake 10.0 en latere versies.
qpatrick
aaaah ik word helemaal gek van webmin....

Ik probeer mijn netwerk uberhaupt zichtbaar te maken, maar dit lukt van geen kant. Ik kan de instellingen niet vinden die hiervoor zorgen. Ik heb mijn PC die het wel doet, naast mijn laptop en alle instellingen doorlopen.

Maar de laptop herkent zichzelf niet eens als server, dus volgens mij zit er een probleem in een service die niet start of firewall die blokkeert.

de smb service draait uiteraard en smb deling staat bij de firewall aangevinkt.
Heeft iemand punten waar ik naar kan gaan zoeken om het werkend te krijgen....?

Stel in MCC in dat iedere gebruker mappen mag delen.
Ga naar systeem - configuratie - KDE -internet/netwerk - samba, en stel daar samba in, o.a. hoe je je computer in het netwerk gaat heten.


Kan het niet vinden. Daarom ben ik toch maar verder gegaan met Samba via webmin, ook omdat het wel werkt op mijn PC.

Alvast bedankt voor de reacties....
Kareltje
(qpatrick @ Mar 22 2007, 10:05 PM) [snapback]81378[/snapback]

aaaah ik word helemaal gek van webmin....

Dat werd ik ook en heb het er toen afgegooid. Je doet echter veels te moeilijk. tongue.gif
Ga naar MCC - Koppelpunten. "Stel delen van uw schijf...." Geef gebruikers de mogelijkheid te delen. (Staat standaard 'uit'). Ga daarna naar Konqueror naar een directory, die je wilt delen. Rechtsklik erop en neem "eigenschappen" Selecteer de tab: gedeeld. Rootw8w, enz.
Doe hetzelfde op de andere computer.
Ga weer terug naar de eerste: MCC - Koppelpunten en neem nu: NFS-koppelpunten instellen. (Wil je ook naar windoos, neem dan sambakoppel...) Nu moet je de andere pc al kunnen zien. Vóór het icoontje staat een driehoekje. Klik erop. Bekijk de zaak en vul het nodige in. Als wordt gevraagd om op te slaan: kies ja. Sluit Mcc af
Ga naar Konqueror, veeg de adresbalk schoon en type: nfs://naam_van_de_dir en toets [enter].
Tadaaaa. icon_cheesygrin.gif
qpatrick
@Kareltje
Dat is wel heel duidelijk, maar toch willen ze elkaar niet zien. Niet via Samba en niet NFS. Uiteraad heb ik wel alle andere stappen gedaan. Ook het delen van een map gedaan, hierdoor veranderd het icoontje....

Maar als ik via nfs of samba naar servers zoek, nothing !
De firewall, staat wel open voor smb deling

Kareltje
(qpatrick @ Mar 26 2007, 01:18 PM) [snapback]81668[/snapback]

De firewall, staat wel open voor smb deling

Zet die dan maar eens helemaal uit en probeer het nog eens.
Kunnen de pc's elkaar wel pingen? Post anders het smb.conf (in code svp) hierzo.

Edit: Je moet wel na iedere wijziging de smb-service herstarten hè? Via Mcc-Systeem-Systeemdiensten... Klik op "start" achter "netfs".
qpatrick
mmmh pingen is niet succesvol, dus dan moet er een fout in de configuratie zitten:


SMB.CONF (vaste pc)
  
[global]
    
    # 1. Server Naming Options:
    # workgroup = NT-Domain-Name or Workgroup-Name
    workgroup = MDKGROUP
    
    # netbios name is the name you will see in "Network Neighbourhood",
    # but defaults to your hostname
    #  netbios name = <name_of_this_server>
    
    # server string is the equivalent of the NT Description field
    server string = Samba Server %v
    
    # Message command is run by samba when a "popup" message is sent to it.
    # The example below is for use with LinPopUp:
  ; message command = /usr/bin/linpopup "%f" "%m" %s; rm %s
    
    # 2. Printing Options:
    # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
    # (as cups is now used in linux-mandrake 7.2 by default)
    # if you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    printcap name = cups
    load printers = yes
    
    # printcap cache time, so samba will automatically load new cups printers
    printcap cache time = 60
    
    # It should not be necessary to spell out the print system type unless
    # yours is non-standard. Currently supported print systems include:
    # bsd, sysv, plp, lprng, aix, hpux, qnx, cups
    printing = cups
    
    # Samba 2.2 supports the Windows NT-style point-and-print feature. To
    # use this, you need to be able to upload print drivers to the samba
    # server. The printer admins (or root) may install drivers onto samba.
    # Note that this feature uses the print$ share, so you will need to
    # enable it below.
    # Printer admins are now defined by granting the SePrintOperatorPrivilege, ie:
    # run: net rpc rights grant 'DOMAIN\Printer Operators' SePrintOperatorPrivilege
    
    # 3. Logging Options:
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log
    
    # Put a capping on the size of the log files (in Kb).
    max log size = 50
    
    # Set the log (verbosity) level (0 <= log level <= 10)
    # log level = 3
    
    # 4. Security and Domain Membership Options:
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
    # not work for all the hosts in your network.
    #   hosts allow = 192.168.1. 192.168.2. 127.
    
    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    #  guest account = pcguest
    # Allow users to map to guest:
    map to guest = bad user
    
    # Security mode. Most people will want user level security. See
    # security_level.txt for details.
    security = user
    # Use password server option only with security = server or security = domain
    # When using security = domain, you should use password server = *
    #   password server = <NT-Server-Name>
    #   password server = *
    
    # Password Level allows matching of _n_ characters of the password for
    # all combinations of upper and lower case.
    #  password level = 8
    #  username level = 8
    
    # You may wish to use password encryption. Please read
    # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
    # Do not enable this option unless you have read those documents
    # Encrypted passwords are required for any use of samba in a Windows NT domain
    # The smbpasswd file is only required by a server doing authentication, thus
    # members of a domain do not need one.
    encrypt passwords = yes
    smb passwd file = /etc/samba/smbpasswd
    
    # The following are needed to allow password changing from Windows to
    # also update the Linux system password.
    # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
    # NOTE2: You do NOT need these to allow workstations to change only
    #        the encrypted SMB passwords. They allow the Unix password
    #        to be kept in sync with the SMB password.
  ;  unix password sync = Yes
    # You either need to setup a passwd program and passwd chat, or
    # enable pam password change
  ;  pam password change = yes
    #  passwd program = /usr/bin/passwd '%u'
  ;  passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n \
  ;*passwd:*all*authentication*tokens*updated*successfully*
    
    # Unix users can map to different SMB User names
  ;  username map = /etc/samba/smbusers
    
    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    #   include = /etc/samba/smb.conf.%m
    
    # Options for using winbind. Winbind allows you to do all account and
    # authentication from a Windows or samba domain controller, creating
    # accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
    # and gid's. winbind uid and winbind gid are the only required parameters.
    #
    # winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
    #  idmap uid = 10000-20000
    #
    # winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
    #  idmap gid = 10000-20000
    #
    # winbind separator is the character a user must use between their domain
    # name and username, defaults to "\"
    #  winbind separator = +
    #
    # winbind use default domain allows you to have winbind return usernames
    # in the form user instead of DOMAIN+user for the domain listed in the
    # workgroup parameter.
    #  winbind use default domain = yes
    #
    # template homedir determines the home directory for winbind users, with
    # %D expanding to their domain name and %U expanding to their username:
    #  template homedir = /home/%D/%U
    
    # When using winbind, you may want to have samba create home directories
    # on the fly for authenticated users. Ensure that /etc/pam.d/samba is
    # using 'service=system-auth-winbind' in pam_stack modules, and then
    # enable obedience of pam restrictions below:
    #  obey pam restrictions = yes
    
    #
    # template shell determines the shell users authenticated by winbind get
    #  template shell = /bin/bash
    
    # 5. Browser Control and Networking Options:
    # Most people will find that this option gives better performance.
    # See speed.txt and the manual pages for details
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    
    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    #   interfaces = 192.168.12.2/24 192.168.13.2/24
    
    # Configure remote browse list synchronisation here
    #  request announcement to, or browse list sync from:
    #       a specific host or from / to a whole subnet (see below)
    #   remote browse sync = 192.168.3.25 192.168.5.255
    # Cause this host to announce itself to local subnets here
    #   remote announce = 192.168.1.255 192.168.2.44
    
    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    #   local master = no
    
    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    #   os level = 33
    
    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    #   domain master = yes
    
    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    #   preferred master = yes
    
    # 6. Domain Control Options:
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations or Primary Domain Controller for WinNT and Win2k
    #   domain logons = yes
    
    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    #   logon script = %m.bat
    # run a specific logon batch file per username
    #   logon script = %u.bat
    
    # Where to store roaming profiles for WinNT and Win2k
    #        %L substitutes for this servers netbios name, %u is username
    #        You must uncomment the [Profiles] share below
    #   logon path = \\%L\Profiles\%u
    
    # Where to store roaming profiles for Win9x. Be careful with this as it also
    # impacts where Win2k finds it's /HOME share
    # logon home = \\%L\%u\.profile
    
    
    # The add user script is used by a domain member to add local user accounts
    # that have been authenticated by the domain controller, or when adding
    # users via the Windows NT Tools (ie User Manager for Domains).
    
    # Scripts for file (passwd, smbpasswd) backend:
    # add user script = /usr/sbin/useradd -s /bin/false '%u'
    # delete user script = /usr/sbin/userdel '%s'
    # add user to group script = /usr/bin/gpasswd -a '%u' '%g'
    # delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
    # set primary group script = /usr/sbin/usermod -g '%g' '%u'
    # add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
    # delete group script = /usr/sbin/groupdel '%g'
    
    # Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller,
    # and needs configuration in smbldap_conf.pm
    # add user script = /usr/sbin/smbldap-useradd -m '%u'
    # delete user script = /usr/sbin/smbldap-userdel '%u'
    # add user to group script = /usr/sbin/smbldap-groupmod -m '%u' '%g'
    # delete user from group script = /usr/sbin/smbldap-groupmod -x '%u' '%g'
    # set primary group script = /usr/sbin/smbldap-usermod -g '%g' '%u'
    # add group script = /usr/sbin/smbldap-groupadd '%g' && /usr/sbin/smbldap-groupshow %g|awk '/^gidNumber:/ {print $2}'
    # delete group script = /usr/sbin/smbldap-groupdel '%g'
    
    
    # The add machine script is use by a samba server configured as a domain
    # controller to add local machine accounts when adding machines to the domain.
    # The script must work from the command line when replacing the macros,
    # or the operation will fail. Check that groups exist if forcing a group.
    # Script for domain controller for adding machines:
    # add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M '%u'
    # Script for domain controller with LDAP backend for adding machines (please
    # configure in /etc/samba/smbldap_conf.pm first):
    # add machine script = /usr/sbin/smbldap-useradd -w -d /dev/null -c 'Machine Account' -s /bin/false '%u'
    
    # Domain groups:
    # Domain groups are now configured by using the 'net groupmap' tool
    
    # Enable priveleges, ie allowing members of Domain Admins to join machines
    # to the domain
    # enable privileges = yes
    
    # Samba Password Database configuration:
    # Samba now has runtime-configurable password database backends. Multiple
    # passdb backends may be used, but users will only be added to the first one
    # Default:
    # passdb backend = smbpasswd guest
    # TDB backen with fallback to smbpasswd and guest
    # passdb backend = tdbsam smbpasswd guest
    # LDAP with fallback to smbpasswd guest
    # Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
    # passdb backend = ldapsam:ldaps://ldap.mydomain.com smbpasswd guest
    # Use the samba2 LDAP schema:
    # passdb backend = ldapsam_compat:ldaps://ldap.mydomain.com smbpasswd guest
    
    # Idmap settings (set idmap uid and idmap gid above):
    # Idmap backend to use:
    # idmap backend = ldap:ldap://ldap.mydomain.com
    
    # LDAP configuration for Domain Controlling:
    # The account (dn) that samba uses to access the LDAP server
    # This account needs to have write access to the LDAP tree
    # You will need to give samba the password for this dn, by
    # running 'smbpasswd -w mypassword'
    # ldap admin dn = cn=root,dc=mydomain,dc=com
    # ldap ssl = start_tls
    # start_tls should run on 389, but samba defaults incorrectly to 636
    # ldap port = 389
    # ldap suffix = dc=mydomain,dc=com
    # Seperate suffixes are available for machines, users, groups, and idmap, if
    # ldap suffix appears first, it is appended to the specific suffix.
    # Example for a unix-ish directory layout:
    # ldap machine suffix = ou=Hosts
    # ldap user suffix = ou=People
    # ldap group suffix = ou=Group
    # ldap idmap suffix = ou=Idmap
    # Example for AD-ish layout:
    # ldap machine suffix = cn=Computers
    # ldap user suffix = cn=Users
    # ldap group suffix = cn=Groups
    # ldap idmap suffix = cn=Idmap
    
    
    # 7. Name Resolution Options:
    # All NetBIOS names must be resolved to IP Addresses
    # 'Name Resolve Order' allows the named resolution mechanism to be specified
    # the default order is "host lmhosts wins bcast". "host" means use the unix
    # system gethostbyname() function call that will use either /etc/hosts OR
    # DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
    # and the /etc/resolv.conf file. "host" therefore is system configuration
    # dependant. This parameter is most often of use to prevent DNS lookups
    # in order to resolve NetBIOS names to IP Addresses. Use with care!
    # The example below excludes use of name resolution for machines that are NOT
    # on the local network segment
    # - OR - are not deliberately to be known via lmhosts or via WINS.
    # name resolve order = wins lmhosts bcast
    
    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    #   wins support = yes
    
    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    #       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    #   wins server = w.x.y.z
    
    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one  WINS Server on the network. The default is NO.
    #   wins proxy = yes
    
    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The built-in default for versions 1.9.17 is yes,
    # this has been changed in version 1.9.18 to no.
    dns proxy = no

# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
#  preserve case = no
#  short preserve case = no
# Default case is normally upper case for all DOS files
#  default case = lower
# Be very careful with case sensitivity - it can break things!
#  case sensitive = no

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
#   dos charset = 850
#   unix charset = ISO8859-1


#============================ Share Definitions ==============================
[homes]
    comment = Home Directories
    browseable = no
    writable = yes
# You can enable VFS recycle bin and on-access virus-scanning on a per
# share basis:
# Uncomment the next 2 lines (make sure you create a .recycle folder in
# the base of the share and ensure all users will have write access to it.
# For virus scanning, install samba-vscan-clamav and ensure the clamd service
# is running
#   vfs objects = vscan-clamav recycle
#   vscan-clamav: config-file = /etc/samba/vscan-clamav.conf

# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
#   comment = Network Logon Service
#   path = /var/lib/samba/netlogon
#   guest ok = yes
#   writable = no

#Uncomment the following 2 lines if you would like your login scripts to
#be created dynamically by ntlogon (check that you have it in the correct
#location (the default of the ntlogon rpm available in contribs)
#root preexec = /usr/bin/ntlogon -u '%u' -g '%g' -o %a -d /var/lib/samba/netlogon/
#root postexec = rm -f '/var/lib/samba/netlogon/%u.bat'

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#[Profiles]
#    path = /var/lib/samba/profiles
#    browseable = no
#    guest ok = yes
#    writable = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
#root preexec = PROFILE='/var/lib/samba/profiles/%u'; if [ ! -e $PROFILE ]; \
#                then mkdir -pm700 $PROFILE; chown '%u':'%g' $PROFILE;fi
# If you want read-only profiles, fake permissions so windows clients think
# they have written to the files
# vfs objects = fake_perms

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients or upload the printer driver to the
# server from Windows (NT/2000/XP). On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to use 'printcap name = cups' or swap the 'print command' line below
# with the commented one. Note that print commands only work if not using
# 'printing=cups'
[printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = no
    # to allow user 'guest account' to print.
    guest ok = yes
    writable = no
    printable = yes
    create mode = 0700
    # =====================================
    # print command: see above for details.
    # =====================================
    print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
    #   print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients).
    # If you install drivers on the server, you will want to uncomment this so
    # clients request the driver
    use client driver = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
#
# A special case is using the CUPS Windows Postscript driver, which allows
# all features available via CUPS on the client, by publishing the ppd file
# and the cups driver by using the 'cupsaddsmb' tool. This requires the
# installation of the CUPS driver (http://www.cups.org/windows.php)
# on the server, but doesn't require you to use Windows at all :-).
[print$]
    path = /var/lib/samba/printers
    browseable = yes
    write list = @adm root
    guest ok = yes
    inherit permissions = yes
# Settings suitable for Winbind:
# write list = @"Domain Admins" root
# force group = +@"Domain Admins"

# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.
# Note that this only works if 'printing' is *not* set to 'cups'

[pdf-gen]
    path = /var/tmp
    guest ok = No
    printable = Yes
    comment = PDF Generator (only valid users)
    printing = bsd
    #print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP &
    print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
    lpq command = /bin/true

# A share allowing administrators to set ACLs on, or access for backup purposes
# all files (as root).
#[admin]
#  path = /
#  admin users = @"Domain Admins"
#  valid users = @"Domain Admins"
#  browseable = no
#  writeable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba/public
;   public = yes
;   writable = no
;   write list = @staff
# Audited directory through experimental VFS audit.so module:
# Uncomment next line.
#   vfs object = /usr/lib/samba/vfs/audit.so

# Other examples.
#
# A private printer, usable only by Fred. Spool data will be placed in Fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by Fred. Note that Fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

[Home map]
    path = /home/patrick
[PATRICKDSKTP]
    path = /home/patrick/Desktop
    comment = /home/patrick/Desktop
    browseable = yes
    public = yes
    writable = no



SMB.CONF (laptop)


[global]
    name resolve order = wins lmhosts bcast
    idmap gid = 16777216-33554431
    passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*\n
    preserve case = no
    remote browse sync = 192.168.0.255
    time server = no
    passwd program = /usr/bin/passwd '%u'
    dns proxy = no
    netbios name = samba24
    cups options = raw
    printing = cups
    idmap uid = 16777216-33554431
    logon script = %G.bat
    local master = no
    remote announce = 192.168.0.255
    workgroup = MDKGROUP
    os level = 33
    printcap name = /etc/printcap
    security = user
    max log size = 1000
    log file = /var/log/samba/samba.log
    load printers = yes
    guest account = smbguest
    smb passwd file = /etc/samba/smbpasswd
    username level = 8
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
    wins server =
    logon drive = m:
    username map = /etc/samba/smbusers
    null passwords = no
    interfaces = 127.0.0.1/8 192.168.0.0/24
    domain master = no
    encrypt passwords = yes
    winbind use default domain = yes
    wins proxy = no
    logon home = \\%L\homes\%u
    template shell = /dev/null
    wins support = no
    password level = 8
    server string = CAD architects, Stockholm, east 32nd st, 34th floor
    path = /home/patrick
    unix password sync = Yes
    logon path = \\%L\profiles\%u
    add user script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M %u
    preferred master = no
    domain logons = no
;  short preserve case = no
;  default case = lower
;  case sensitive = no

[netlogon]
    comment = Network Logon Service
    path = /home/netlogon
    read only = no
    available = yes
    browseable = yes
    writable = yes
    guest ok = no
    public = no
    printable = no
    share modes = no
    locking = no

[profiles]
    comment = User Profiles
    path = /home/profiles
    read only = no
    available = yes
    browseable = no
    writable = yes
    guest ok = no
    public = no
    printable = no
    locking = no
    create mode = 0600
    directory mask = 0700

[printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = yes
    writable = no
    guest ok = no
    public = no
    printable = yes
    share modes = no
    locking = no

[pdf-documents]
    path = /home/pdf-documents
    comment = Converted PDF Documents
    available = yes
    browseable = yes
    writeable = yes
    guest ok = yes

[pdf-printer]
    path = /tmp
    comment = PDF Printer Service
    printable = yes
    guest ok = yes
    use client driver = yes
    printing = bsd
    print command = /usr/bin/gsambadpdf %s %u
    lpq command =
    lprm command =
[homes]
    path = /home
    comment = Home Directories
    browseable = yes
    public = yes
    writable = yes
[homefgfggf]
    path = /home/patrick/
    comment = homeh
    browseable = yes
    public = yes
    writable = yes

[home laptop]
    writeable = yes
    write list = patrick

[PATRICKDSKTP]
   path = /home/patrick/Desktop
   comment = /home/patrick/Desktop
   public = yes
   guest ok = yes
   writable = no
   wide links = no



En dat ik de service moet herstarten dat was me idd bekend, maar niet geholpen tot nu toe....
RvP
Kijk even Hier op dit forum.
Less is more, of te wel; strippen van je instellingen helpt.
Kareltje
Ik heb de smb.conf's maar even aangepast, het uitleggen kost me meer tijd dan de aanpassingen maken. icon_cool.gif
Kleine toelichting: de opties, die -mogelijk- problemen veroorzaken, heb ik ongedaan gemaakt door een " ; " ervoor te zetten. Ook een " # " heeft hetzelfde effect. In oude "Dos-termen" heet dit: "eruit remmen" (oftewel "rem" ervoor zetten.)
Verder wat (netbios)namen aangepast enz. enz. Wat ik uit de conf-file van je laptop begreep, probeerde die de "baas" te spelen over het netwerk, wat niet lukte. Ook toegang met w8woorden heb ik uitgeschakeld, pas dus een beetje op. Trek desnoods het snoer naar het Internet er tijdelijk uit, terwijl je aan het testen bent.
De truc is nu, dat in ieder geval de pc's elkaar kunnen "zien". (hopelijk ;).gif )Door nu één voor één een " ; " uit het smb.conf-file weg te halen, service opnieuw starten en testen, kom je erachter, wat het doet en/of waar het fout gaat. Dus op de toer van "try on error", zoals RvP je hierboven heeft verwezen. rolleyes.gif Dit kan je dus wel een paar avonden kosten. icon_cheesygrin.gif icon_cry.gif

Kom je daar niet uit, dan (heb ik ook vaak gedaan) ALLES wat met "smb" te maken heeft eraf gooien, (webmin, swat, smb x 3) fstab opruimen, smb.conf's deleten enz. enz. Nadien òf webmin òf swat weer installeren. samen met smb x 3.
Andere mogelijkheid: Alles verwijderen, dan via het pad: menu - systeem - configuratie - KDE -internet/netwerk - samba instellen. (Je zegt, dat je die optie niet hebt in het menu, die moet er staan, als je een normale standaard install hebt gedaan; ik heb die optie wel.)

Succes.


[global]

    # 1. Server Naming Options:
    # workgroup = NT-Domain-Name or Workgroup-Name
    workgroup = GROEPPATRICK

    # netbios name is the name you will see in "Network Neighbourhood",
    # but defaults to your hostname
    netbios name = samba42

    # server string is the equivalent of the NT Description field
    server string = Samba Server %v

    # Message command is run by samba when a "popup" message is sent to it.
    # The example below is for use with LinPopUp:
;    message command = /usr/bin/linpopup "%f" "%m" %s; rm %s

    # 2. Printing Options:
    # CHANGES TO ENABLE PRINTING ON ALL CUPS PRINTERS IN THE NETWORK
    # (as cups is now used in linux-mandrake 7.2 by default)
    # if you want to automatically load your printer list rather
    # than setting them up individually then you'll need this
    printcap name = cups
    load printers = yes

    # printcap cache time, so samba will automatically load new cups printers
    printcap cache time = 60

    # It should not be necessary to spell out the print system type unless
    # yours is non-standard. Currently supported print systems include:
    # bsd, sysv, plp, lprng, aix, hpux, qnx, cups
    printing = cups

    # Samba 2.2 supports the Windows NT-style point-and-print feature. To
    # use this, you need to be able to upload print drivers to the samba
    # server. The printer admins (or root) may install drivers onto samba.
    # Note that this feature uses the print$ share, so you will need to
    # enable it below.
    # Printer admins are now defined by granting the SePrintOperatorPrivilege, ie:
    # run: net rpc rights grant 'DOMAIN\Printer Operators' SePrintOperatorPrivilege

    # 3. Logging Options:
    # this tells Samba to use a separate log file for each machine
    # that connects
    log file = /var/log/samba/%m.log

    # Put a capping on the size of the log files (in Kb).
    max log size = 50

    # Set the log (verbosity) level (0 <= log level <= 10)
    # log level = 3

    # 4. Security and Domain Membership Options:
    # This option is important for security. It allows you to restrict
    # connections to machines which are on your local network. The
    # following example restricts access to two C class networks and
    # the "loopback" interface. For more examples of the syntax see
    # the smb.conf man page. Do not enable this if (tcp/ip) name resolution does
    # not work for all the hosts in your network.
    #   hosts allow = 192.168.1. 192.168.2. 127.

    # Uncomment this if you want a guest account, you must add this to /etc/passwd
    # otherwise the user "nobody" is used
    #  guest account = pcguest
    # Allow users to map to guest:
;    map to guest = bad user

    # Security mode. Most people will want user level security. See
    # security_level.txt for details.
;    security = user
    # Use password server option only with security = server or security = domain
    # When using security = domain, you should use password server = *
    #   password server = <NT-Server-Name>
    #   password server = *

    # Password Level allows matching of _n_ characters of the password for
    # all combinations of upper and lower case.
    #  password level = 8
    #  username level = 8

    # You may wish to use password encryption. Please read
    # ENCRYPTION.txt, Win95.txt and WinNT.txt in the Samba documentation.
    # Do not enable this option unless you have read those documents
    # Encrypted passwords are required for any use of samba in a Windows NT domain
    # The smbpasswd file is only required by a server doing authentication, thus
    # members of a domain do not need one.
;    encrypt passwords = yes
    smb passwd file = /etc/samba/smbpasswd

    # The following are needed to allow password changing from Windows to
    # also update the Linux system password.
    # NOTE: Use these with 'encrypt passwords' and 'smb passwd file' above.
    # NOTE2: You do NOT need these to allow workstations to change only
    #        the encrypted SMB passwords. They allow the Unix password
    #        to be kept in sync with the SMB password.
;    unix password sync = Yes
    # You either need to setup a passwd program and passwd chat, or
    # enable pam password change
;    pam password change = yes
    #  passwd program = /usr/bin/passwd '%u'
;    passwd chat = *New*UNIX*password* %n\n *Re*ype*new*UNIX*password* %n\n \
;  *passwd:*all*authentication*tokens*updated*successfully*

    # Unix users can map to different SMB User names
;    username map = /etc/samba/smbusers

    # Using the following line enables you to customise your configuration
    # on a per machine basis. The %m gets replaced with the netbios name
    # of the machine that is connecting
    #   include = /etc/samba/smb.conf.%m

    # Options for using winbind. Winbind allows you to do all account and
    # authentication from a Windows or samba domain controller, creating
    # accounts on the fly, and maintaining a mapping of Windows RIDs to unix uid's
    # and gid's. winbind uid and winbind gid are the only required parameters.
    #
    # winbind uid is the range of uid's winbind can use when mapping RIDs to uid's
    #  idmap uid = 10000-20000
    #
    # winbind gid is the range of uid's winbind can use when mapping RIDs to gid's
    #  idmap gid = 10000-20000
    #
    # winbind separator is the character a user must use between their domain
    # name and username, defaults to "\"
    #  winbind separator = +
    #
    # winbind use default domain allows you to have winbind return usernames
    # in the form user instead of DOMAIN+user for the domain listed in the
    # workgroup parameter.
    #  winbind use default domain = yes
    #
    # template homedir determines the home directory for winbind users, with
    # %D expanding to their domain name and %U expanding to their username:
    #  template homedir = /home/%D/%U

    # When using winbind, you may want to have samba create home directories
    # on the fly for authenticated users. Ensure that /etc/pam.d/samba is
    # using 'service=system-auth-winbind' in pam_stack modules, and then
    # enable obedience of pam restrictions below:
    #  obey pam restrictions = yes

    #
    # template shell determines the shell users authenticated by winbind get
    #  template shell = /bin/bash

    # 5. Browser Control and Networking Options:
    # Most people will find that this option gives better performance.
    # See speed.txt and the manual pages for details
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192

    # Configure Samba to use multiple interfaces
    # If you have multiple network interfaces then you must list them
    # here. See the man page for details.
    #   interfaces = 192.168.12.2/24 192.168.13.2/24

    # Configure remote browse list synchronisation here
    #  request announcement to, or browse list sync from:
    #       a specific host or from / to a whole subnet (see below)
    #   remote browse sync = 192.168.3.25 192.168.5.255
    # Cause this host to announce itself to local subnets here
    #   remote announce = 192.168.1.255 192.168.2.44

    # set local master to no if you don't want Samba to become a master
    # browser on your network. Otherwise the normal election rules apply
    #   local master = no

    # OS Level determines the precedence of this server in master browser
    # elections. The default value should be reasonable
    #   os level = 33

    # Domain Master specifies Samba to be the Domain Master Browser. This
    # allows Samba to collate browse lists between subnets. Don't use this
    # if you already have a Windows NT domain controller doing this job
    #   domain master = yes

    # Preferred Master causes Samba to force a local browser election on startup
    # and gives it a slightly higher chance of winning the election
    #   preferred master = yes

    # 6. Domain Control Options:
    # Enable this if you want Samba to be a domain logon server for
    # Windows95 workstations or Primary Domain Controller for WinNT and Win2k
    #   domain logons = yes

    # if you enable domain logons then you may want a per-machine or
    # per user logon script
    # run a specific logon batch file per workstation (machine)
    #   logon script = %m.bat
    # run a specific logon batch file per username
    #   logon script = %u.bat

    # Where to store roaming profiles for WinNT and Win2k
    #        %L substitutes for this servers netbios name, %u is username
    #        You must uncomment the [Profiles] share below
    #   logon path = \\%L\Profiles\%u

    # Where to store roaming profiles for Win9x. Be careful with this as it also
    # impacts where Win2k finds it's /HOME share
    # logon home = \\%L\%u\.profile


    # The add user script is used by a domain member to add local user accounts
    # that have been authenticated by the domain controller, or when adding
    # users via the Windows NT Tools (ie User Manager for Domains).

    # Scripts for file (passwd, smbpasswd) backend:
    # add user script = /usr/sbin/useradd -s /bin/false '%u'
    # delete user script = /usr/sbin/userdel '%s'
    # add user to group script = /usr/bin/gpasswd -a '%u' '%g'
    # delete user from group script = /usr/bin/gpasswd -d '%u' '%g'
    # set primary group script = /usr/sbin/usermod -g '%g' '%u'
    # add group script = /usr/sbin/groupadd %g && getent group '%g'|awk -F: '{print $3}'
    # delete group script = /usr/sbin/groupdel '%g'

    # Scripts for LDAP backend (assumes nss_ldap is in use on the domain controller,
    # and needs configuration in smbldap_conf.pm
    # add user script = /usr/sbin/smbldap-useradd -m '%u'
    # delete user script = /usr/sbin/smbldap-userdel '%u'
    # add user to group script = /usr/sbin/smbldap-groupmod -m '%u' '%g'
    # delete user from group script = /usr/sbin/smbldap-groupmod -x '%u' '%g'
    # set primary group script = /usr/sbin/smbldap-usermod -g '%g' '%u'
    # add group script = /usr/sbin/smbldap-groupadd '%g' && /usr/sbin/smbldap-groupshow %g|awk '/^gidNumber:/ {print $2}'
    # delete group script = /usr/sbin/smbldap-groupdel '%g'

    # The add machine script is use by a samba server configured as a domain
    # controller to add local machine accounts when adding machines to the domain.
    # The script must work from the command line when replacing the macros,
    # or the operation will fail. Check that groups exist if forcing a group.
    # Script for domain controller for adding machines:
    # add machine script = /usr/sbin/useradd -d /dev/null -g machines -c 'Machine Account' -s /bin/false -M '%u'
    # Script for domain controller with LDAP backend for adding machines (please
    # configure in /etc/samba/smbldap_conf.pm first):
    # add machine script = /usr/sbin/smbldap-useradd -w -d /dev/null -c 'Machine Account' -s /bin/false '%u'

    # Domain groups:
    # Domain groups are now configured by using the 'net groupmap' tool

    # Enable priveleges, ie allowing members of Domain Admins to join machines
    # to the domain
    # enable privileges = yes

    # Samba Password Database configuration:
    # Samba now has runtime-configurable password database backends. Multiple
    # passdb backends may be used, but users will only be added to the first one
    # Default:
    # passdb backend = smbpasswd guest
    # TDB backen with fallback to smbpasswd and guest
    # passdb backend = tdbsam smbpasswd guest
    # LDAP with fallback to smbpasswd guest
    # Enable SSL by using an ldaps url, or enable tls with 'ldap ssl' below.
    # passdb backend = ldapsam:ldaps://ldap.mydomain.com smbpasswd guest
    # Use the samba2 LDAP schema:
    # passdb backend = ldapsam_compat:ldaps://ldap.mydomain.com smbpasswd guest

    # Idmap settings (set idmap uid and idmap gid above):
    # Idmap backend to use:
    # idmap backend = ldap:ldap://ldap.mydomain.com

    # LDAP configuration for Domain Controlling:
    # The account (dn) that samba uses to access the LDAP server
    # This account needs to have write access to the LDAP tree
    # You will need to give samba the password for this dn, by
    # running 'smbpasswd -w mypassword'
    # ldap admin dn = cn=root,dc=mydomain,dc=com
    # ldap ssl = start_tls
    # start_tls should run on 389, but samba defaults incorrectly to 636
    # ldap port = 389
    # ldap suffix = dc=mydomain,dc=com
    # Seperate suffixes are available for machines, users, groups, and idmap, if
    # ldap suffix appears first, it is appended to the specific suffix.
    # Example for a unix-ish directory layout:
    # ldap machine suffix = ou=Hosts
    # ldap user suffix = ou=People
    # ldap group suffix = ou=Group
    # ldap idmap suffix = ou=Idmap
    # Example for AD-ish layout:
    # ldap machine suffix = cn=Computers
    # ldap user suffix = cn=Users
    # ldap group suffix = cn=Groups
    # ldap idmap suffix = cn=Idmap

    # 7. Name Resolution Options:
    # All NetBIOS names must be resolved to IP Addresses
    # 'Name Resolve Order' allows the named resolution mechanism to be specified
    # the default order is "host lmhosts wins bcast". "host" means use the unix
    # system gethostbyname() function call that will use either /etc/hosts OR
    # DNS or NIS depending on the settings of /etc/host.config, /etc/nsswitch.conf
    # and the /etc/resolv.conf file. "host" therefore is system configuration
    # dependant. This parameter is most often of use to prevent DNS lookups
    # in order to resolve NetBIOS names to IP Addresses. Use with care!
    # The example below excludes use of name resolution for machines that are NOT
    # on the local network segment
    # - OR - are not deliberately to be known via lmhosts or via WINS.
    # name resolve order = wins lmhosts bcast

    # Windows Internet Name Serving Support Section:
    # WINS Support - Tells the NMBD component of Samba to enable it's WINS Server
    #   wins support = yes

    # WINS Server - Tells the NMBD components of Samba to be a WINS Client
    #       Note: Samba can be either a WINS Server, or a WINS Client, but NOT both
    #   wins server = w.x.y.z

    # WINS Proxy - Tells Samba to answer name resolution queries on
    # behalf of a non WINS capable client, for this to work there must be
    # at least one  WINS Server on the network. The default is NO.
    #   wins proxy = yes

    # DNS Proxy - tells Samba whether or not to try to resolve NetBIOS names
    # via DNS nslookups. The built-in default for versions 1.9.17 is yes,
    # this has been changed in version 1.9.18 to no.
    dns proxy = no

# 8. File Naming Options:
# Case Preservation can be handy - system default is _no_
# NOTE: These can be set on a per share basis
#  preserve case = no
#  short preserve case = no
# Default case is normally upper case for all DOS files
#  default case = lower
# Be very careful with case sensitivity - it can break things!
#  case sensitive = no

# Enabling internationalization:
# you can match a Windows code page with a UNIX character set.
# Windows: 437 (US), 737 (GREEK), 850 (Latin1 - Western European),
# 852 (Eastern Eu.), 861 (Icelandic), 932 (Cyrillic - Russian),
# 936 (Japanese - Shift-JIS), 936 (Simpl. Chinese), 949 (Korean Hangul),
# 950 (Trad. Chin.).
# UNIX: ISO8859-1 (Western European), ISO8859-2 (Eastern Eu.),
# ISO8859-5 (Russian Cyrillic), KOI8-R (Alt-Russ. Cyril.)
# This is an example for french users:
#   dos charset = 850
#   unix charset = ISO8859-1


#============================ Share Definitions ==============================
[homes]
    comment = Home Directories
    browseable = yes
    writable = yes
# You can enable VFS recycle bin and on-access virus-scanning on a per
# share basis:
# Uncomment the next 2 lines (make sure you create a .recycle folder in
# the base of the share and ensure all users will have write access to it.
# For virus scanning, install samba-vscan-clamav and ensure the clamd service
# is running
#   vfs objects = vscan-clamav recycle
#   vscan-clamav: config-file = /etc/samba/vscan-clamav.conf

# Un-comment the following and create the netlogon directory for Domain Logons
# [netlogon]
#   comment = Network Logon Service
#   path = /var/lib/samba/netlogon
#   guest ok = yes
#   writable = no

#Uncomment the following 2 lines if you would like your login scripts to
#be created dynamically by ntlogon (check that you have it in the correct
#location (the default of the ntlogon rpm available in contribs)
#root preexec = /usr/bin/ntlogon -u '%u' -g '%g' -o %a -d /var/lib/samba/netlogon/
#root postexec = rm -f '/var/lib/samba/netlogon/%u.bat'

# Un-comment the following to provide a specific roving profile share
# the default is to use the user's home directory
#[Profiles]
#    path = /var/lib/samba/profiles
#    browseable = no
#    guest ok = yes
#    writable = yes
# This script can be enabled to create profile directories on the fly
# You may want to turn off guest acces if you enable this, as it
# hasn't been thoroughly tested.
# root preexec = PROFILE='/var/lib/samba/profiles/%u'; if [ ! -e $PROFILE ]; \
#                then mkdir -pm700 $PROFILE; chown '%u':'%g' $PROFILE;fi
# If you want read-only profiles, fake permissions so windows clients think
# they have written to the files
# vfs objects = fake_perms

# NOTE: If you have a CUPS print system there is no need to
# specifically define each individual printer.
# You must configure the samba printers with the appropriate Windows
# drivers on your Windows clients or upload the printer driver to the
# server from Windows (NT/2000/XP). On the Samba server no filtering is
# done. If you wish that the server provides the driver and the clients
# send PostScript ("Generic PostScript Printer" under Windows), you have
# to use 'printcap name = cups' or swap the 'print command' line below
# with the commented one. Note that print commands only work if not using
# 'printing=cups'
[printers]
    comment = All Printers
    path = /var/spool/samba
    # browseable = no
    # to allow user 'guest account' to print.
    guest ok = yes
    writable = yes
    printable = yes
    create mode = 0700
    # =====================================
    # print command: see above for details.
    # =====================================
    # print command = lpr-cups -P %p -o raw %s -r # using client side printer drivers.
    # print command = lpr-cups -P %p %s # using cups own drivers (use generic PostScript on clients).
    # If you install drivers on the server, you will want to uncomment this so
    # clients request the driver
    # use client driver = yes

# This share is used for Windows NT-style point-and-print support.
# To be able to install drivers, you need to be either root, or listed
# in the printer admin parameter above. Note that you also need write access
# to the directory and share definition to be able to upload the drivers.
# For more information on this, please see the Printing Support Section of
# /usr/share/doc/samba-<version>/docs/Samba-HOWTO-Collection.pdf
#
# A special case is using the CUPS Windows Postscript driver, which allows
# all features available via CUPS on the client, by publishing the ppd file
# and the cups driver by using the 'cupsaddsmb' tool. This requires the
# installation of the CUPS driver (http://www.cups.org/windows.php)
# on the server, but doesn't require you to use Windows at all :-).
[print$]
    path = /var/lib/samba/printers
    browseable = yes
;    write list = @adm root
    guest ok = yes
#   inherit permissions = yes
# Settings suitable for Winbind:
# write list = @"Domain Admins" root
# force group = +@"Domain Admins"

# A useful application of samba is to make a PDF-generation service
# To streamline this, install windows postscript drivers (preferably colour)
# on the samba server, so that clients can automatically install them.
# Note that this only works if 'printing' is *not* set to 'cups'

# [pdf-gen]
#    path = /var/tmp
#    guest ok = No
#    printable = Yes
#    comment = PDF Generator (only valid users)
#    printing = bsd
#    print command = /usr/share/samba/scripts/print-pdf file path win_path recipient IP &
#    print command = /usr/share/samba/scripts/print-pdf "%s" "%H" "//%L/%u" "%m" "%I" "%J" &
#    lpq command = /bin/true

# A share allowing administrators to set ACLs on, or access for backup purposes
# all files (as root).
#[admin]
#  path = /
#  admin users = @"Domain Admins"
#  valid users = @"Domain Admins"
#  browseable = no
#  writeable = yes

# This one is useful for people to share files
;[tmp]
;   comment = Temporary file space
;   path = /tmp
;   read only = no
;   public = yes

# A publicly accessible directory, but read only, except for people in
# the "staff" group
;[public]
;   comment = Public Stuff
;   path = /home/samba/public
;   public = yes
;   writable = no
;   write list = @staff
# Audited directory through experimental VFS audit.so module:
# Uncomment next line.
#   vfs object = /usr/lib/samba/vfs/audit.so

# Other examples.
#
# A private printer, usable only by Fred. Spool data will be placed in Fred's
# home directory. Note that fred must have write access to the spool directory,
# wherever it is.
;[fredsprn]
;   comment = Fred's Printer
;   valid users = fred
;   path = /homes/fred
;   printer = freds_printer
;   public = no
;   writable = no
;   printable = yes

# A private directory, usable only by Fred. Note that Fred requires write
# access to the directory.
;[fredsdir]
;   comment = Fred's Service
;   path = /usr/somewhere/private
;   valid users = fred
;   public = no
;   writable = yes
;   printable = no

# a service which has a different directory for each machine that connects
# this allows you to tailor configurations to incoming machines. You could
# also use the %u option to tailor it by user name.
# The %m gets replaced with the machine name that is connecting.
;[pchome]
;  comment = PC Directories
;  path = /usr/pc/%m
;  public = no
;  writable = yes

# The following two entries demonstrate how to share a directory so that two
# users can place files there that will be owned by the specific users. In this
# setup, the directory should be writable by both users and should have the
# sticky bit set on it to prevent abuse. Obviously this could be extended to
# as many users as required.
;[myshare]
;   comment = Mary's and Fred's stuff
;   path = /usr/somewhere/shared
;   valid users = mary fred
;   public = no
;   writable = yes
;   printable = no
;   create mask = 0765

[Home map]
    path = /home/patrick/Documenten
    browseable = yes
    public = yes

[PATRICKDSKTP]
    path = /home/patrick/Desktop
    comment = /home/patrick/Desktop
    browseable = yes
    public = yes
    writable = no

knip-------------------------------------------------knip

flaptop

SMB.CONF (laptop)


[global]
;    name resolve order = wins lmhosts bcast
;    idmap gid = 16777216-33554431
;    passwd chat = *New*UNIX*password* %n\n *ReType*new*UNIX*password* %n\n *passwd:*all*authentication*tokens*updated*successfully*\n
;    preserve case = no
;    remote browse sync = 192.168.0.255
;    time server = no
;    passwd program = /usr/bin/passwd '%u'
    dns proxy = no
    netbios name = samba24
;    cups options = raw
    printing = cups
;    idmap uid = 16777216-33554431
;    logon script = %G.bat
;    local master = no
    remote announce = 192.168.0.255
    workgroup = GROEPPATRICK
;    os level = 33
    printcap name = /etc/printcap
;    security = user
    max log size = 100
    log file = /var/log/samba/samba.log
    load printers = yes
    guest account = smbguest
    smb passwd file = /etc/samba/smbpasswd
;    username level = 8
    socket options = TCP_NODELAY SO_RCVBUF=8192 SO_SNDBUF=8192
;    wins server =
;    logon drive = m:
;    username map = /etc/samba/smbusers
;    null passwords = no
    interfaces = 127.0.0.1/8 192.168.0.0/24
;    domain master = no
;    encrypt passwords = yes
;    winbind use default domain = yes
;    wins proxy = no
;    logon home = \\%L\homes\%u
;    template shell = /dev/null
;    wins support = no
;    password level = 8
;    server string = CAD architects, Stockholm, east 32nd st, 34th floor
;    path = /home/patrick
;    unix password sync = Yes
;    logon path = \\%L\profiles\%u
;    add user script = /usr/sbin/useradd -d /dev/null -g sambamachines -c 'Samba Machine Account' -s /dev/null -M %u
;    preferred master = no
;    domain logons = no
;  short preserve case = no
;  default case = lower
;  case sensitive = no

;[netlogon]
;    comment = Network Logon Service
;    path = /home/netlogon
;    read only = no
;    available = yes
;    browseable = yes
;    writable = yes
;    guest ok = no
;    public = no
;    printable = no
;    share modes = no
;    locking = no

;[profiles]
;    comment = User Profiles
;    path = /home/profiles
;    read only = no
;    available = yes
;    browseable = no
;    writable = yes
;    guest ok = no
;    public = no
;    printable = no
;    locking = no
;    create mode = 0600
;    directory mask = 0700

[printers]
    comment = All Printers
    path = /var/spool/samba
    browseable = yes
;    writable = no
;    guest ok = no
;    public = no
;    printable = yes
;    share modes = no
;    locking = no

[pdf-documents]
    path = /home/pdf-documents
    comment = Converted PDF Documents
    available = yes
    browseable = yes
    writeable = yes
    guest ok = yes

;[pdf-printer]
;    path = /tmp
;    comment = PDF Printer Service
;    printable = yes
;    guest ok = yes
;    use client driver = yes
;    printing = bsd
;    print command = /usr/bin/gsambadpdf %s %u
;    lpq command =
;    lprm command =

[homes]
    path = /home/%u
    comment = Home Directories
    browseable = yes
    public = yes
    writable = yes

[homefgfggf]
    path = /home/patrick/Documenten
    comment = homeh
    browseable = yes
    public = yes
    writable = yes

[home laptop]
    writeable = yes
    browseable = yes
;    write list = patrick

[PATRICKDSKTP]
   path = /home/patrick/Desktop
   comment = /home/patrick/Desktop
   public = yes
   guest ok = yes
   writable = no
;   wide links = no

RvP
Voor de volledigheid: Ik heb noch Swat noch Webmin in gebruik, alleen samba client en server (op alle pc's)
Kareltje
(RvP @ Mar 27 2007, 10:21 PM) [snapback]81853[/snapback]

Voor de volledigheid: Ik heb noch Swat noch Webmin in gebruik, alleen samba client en server (op alle pc's)

Mee eens, beide hebben veel te veel instellingen en mogelijkheden. Swat werkt nog het beste van de twee.
Ik doe het ook altijd zonder. icon_cheesygrin.gif ;).gif
qpatrick
Ben er druk mee bezig, als ik een vorderig zie laat ik het meteen weten smile.gif alvast bedankt !!!

qpatrick
alles er af gegooid....het ging niet werken...Dus nu maar ff met een schone lei beginnen.... mad.gif mad.gif wacko.gif wacko.gif
qpatrick
CONTACT !!!!!! icon_idea.gif


Twee apparaten die vooralsnog niets met elkaar te maken hadden, lullen nu alsof ze elkaar jaren niet meer gezien hebben.....!!!

De stabiliteit en de rechten kwesties zijn nog niet helemaal opgelost, maar ik zit er nu trots naar te kijken.... icon_cheesygrin.gif
bedankt voor alle tips en hints en moeite die jullie erin hebben gestoken !! icon_frown.gif
doelman
Hoe heb je het voor elkaar gekregen?
qpatrick
sowieso alles eraf gegooid om ff schoon opnieuw te beginnen.
Daarna het advies van Kareltje enkele keren gevolgd. Het grootste probleem was dat het netwerk niet in de lucht kwam. Met de firewall helemaal open lukte het uiteindelijk wel. Nu moet ik het weer terug gaan zetten en kijken hoe deze reageert als ze één voor één dicht zet.

Ben erg benieuwd of het een stabiel netwerk wordt....maar ben nu al flink blij met het behaalde !!!!
RvP
Laat ons ook even weten hoe het netwerk met firewall poorten dichtmaken verloopt.
(gewoon nieuwsgierig 'ende ter lering ende vermaeck voor de overige forumbezoekers icon_idea.gif )
Dit is een "Print" versie van onze forums. Om de volledige versie met meer informatie, afbeeldingen en opmaakte bekijken, a.u.b. klik hier.