Nieuws:

Welkom, Gast. Alsjeblieft inloggen of registreren.
Heb je de activerings-mail niet ontvangen?

Auteur Topic: Samba share niet schrijven met ubuntu-client ,wel met windows-client  (gelezen 6305 keer)

Hoi,

Rare zaken. Ik heb een ubuntuservertje met samba ingericht, met een samba share.

Daar kan ik wel naar schrijven met mijn windows, maar niet met mijn ubuntu-client. " Toegang geweigerd tijdens schrijven naar...."

Voor de duidelijkheid: Ik heb dus een computer met dualboot met ubuntu en windows2000,zelfde gebruikersnaam.

De andere computer heb ik ingericht als server, logt ook in met zelfde gebruikersnaam, en gebruikt dezelfde samba-user. Alle hosts ,werkgroepen enzo zijn correct ingevoerd.

Ik kan dus lezen en schrijven met mijn windowsclient naar de sambashare, maar niet  schrijven met de ubuntu-client. Lezen kan wel, en ik kom ook op de share.
Raaarrrr. Iemand enig idee? Dank alvast!

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #1 Gepost op: 2007/07/12, 20:51:41 »
Hoe benader je de samba server?
Ik doe het via:Places -> Connect to server -> dinges invullen en op ok klikken.

Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #2 Gepost op: 2007/07/15, 12:59:30 »
Deed ik (onder andere ) ook. Maar dan bleef het alleen-lezen,terwijl ik toch als Gerard inlogde op een Gerard-share.

Maar het is al opgelost. Hebin mijn etc/samba/smb.conf

   create mask = 0600   veranderd in 0770
   directory mask = 0700 veranderd in 770

Nu doet ie het wel. Beetje kullig, aangezien inloggen met mijn windowspartitie
,ik wel meteen schrijfbevoegdheid heb. Maar goed, opgelost.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #3 Gepost op: 2007/08/10, 13:14:30 »
hier wil ik toch wel het fijne van weten eigenlijk...

waarom krijgt die windowsbak wel schrijfrecht? ik heb nl hetzelfde probleem en ik vertik het eigenlijk om de rechten te versoepelen.

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #4 Gepost op: 2007/08/10, 13:28:10 »
Wel, ik heb het probleem niet omdat al mijn Ubuntu en windows machines in hetzelfde domein zitten. Hierdoor zijn accounts op alle machines dezelfde. Beschrijf even in detail wat je precies probeert te doen. Beschrijf ook uw netwerk. Geef ook de smb.conf bestanden van beide ubuntu machines.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #5 Gepost op: 2007/08/10, 15:41:27 »
Ok.

Het gaat hier om 3 pc's:

PC1 XP, gebruiker Sander, kan lezen en schrijven op de server.

Windows IP-configuratie

        Host-naam  . . . . . . . . . . . .: p4-2400
        Primair DNS-achtervoegsel. . . . .:
        Knooppunttype: . . . . . . . . . .: onbekend
        IP-routering ingeschakeld. . . . .: nee
        WINS-proxy ingeschakeld . . . . . : nee

Ethernet-adapter LAN-verbinding:

        Verbindingsspec. DNS-achtervoegsel:
        Beschrijving . . . . . . . . . . .:
          Intel(R) PRO/1000 MT Desktop Adapter
        Fysiek adres. . . . . . . . . . . : 00-10-DC-DF-31-12
        DHCP ingeschakeld:. . . . . . . . : nee
        IP-adres. . . . . . . . . . . . . : 192.168.1.151
        Subnetmasker. . . . . . . . . . . : 255.255.255.0
        Standaardgateway. . . . . . . . . : 192.168.1.1
        DNS-servers . . . . . . . . . . . : 192.168.1.201
                                            192.168.1.1
PC 2, Server "Butler" IP adres 192.168.1.200. SMB.conf:
[global]
        local master = yes
        perferred master = yes
        dns proxy = No
        log file = /var/log/samba/log.%m
        load printers = No
        server string = %h server
        invalid users = root
        obey pam restrictions = Yes
        workgroup = MSHOME
        encrypt passwords = yes
        syslog = 0
        panic action = /usr/share/samba/panic-action %d
        passdb backend = tdbsam
        passwd program = /usr/bin/passwd %u
        max log size = 1000
        wins support = yes

[homes]
        comment = Home Directories
        valid users = %S
        create mask = 0770
        directory mask = 0770
        browseable = No



[SANDER_MEDIA] !!!hier gaat het om!!!!
        path = /home/sander/Media
        valid users = sander, sanderr
        admin list = sander, sanderr
        write list = sander, sanderr
        read only = Yes
        Guest ok = Yes
        hosts allow = 192.168.1.0/255.255.255.0
        create mask = 0777
        directory mask = 0777
PC 3, Mediacomputertje, 192.168.1.199 gebruiker Sanderr aangemaakt met smbpasswd. smb.conf:
Ik heb hier overigens niets op ingesteld met samba, hij heeft niets te delen...Maar mag ook niet schrijven op de server op 1 of andere manier.
[global]

## Browsing/Identification ###

# Change this to the workgroup/NT-domain name your Samba server will part of
   workgroup = MSHOME

# server string is the equivalent of the NT Description field
   server string = %h server (Samba, Ubuntu)

# Windows Internet Name Serving Support Section:
# WINS Support - Tells the NMBD component of Samba to enable its WINS Server
;   wins support = no

# 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

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #6 Gepost op: 2007/08/11, 08:30:03 »
- Dus, gebruiker sander en sanderr bestaan op butler en zijn beide voorzien van een samba paswoord?
- Wat vind je in de logs van samba op butler (/var/log/samba/log.smbd, log.nmbd, log.PC 1, log.PC 3)

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #7 Gepost op: 2007/08/12, 14:14:08 »
Hoi Kenny,

Ik kom nu een paar hele rare dingen tegen...

ik heb meerdere logbestanden voor 1 pc. Voorbeeld, Media1 heeft 2 logbestanden. 1 op naam van zijn pc-naam, log.media1 en 1 op ip. log.192.168.1.199. Het bestand log.media1 is vanaf 13-07-2007 niet meer bijgewerkt en werkt vanuit 192.168.1.12 (??) Dit ip heeft hij nooit gehad voor zover ik weet.

Log.media1
[2007/07/07 12:00:23, 1] smbd/process.c:async_processing(312)
  Reloading services after SIGHUP
[2007/07/07 12:00:23, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/07 12:00:23, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/07 12:00:23, 1] smbd/process.c:async_processing(312)
  Reloading services after SIGHUP
[2007/07/07 12:00:23, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/07 12:00:23, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/07 12:01:49, 1] smbd/service.c:make_connection_snum(950)
  media1 (192.168.1.12) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 8620)
[2007/07/07 12:06:02, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.12. Error = Connection reset by peer
[2007/07/07 12:06:02, 1] smbd/service.c:close_cnum(1150)
  media1 (192.168.1.12) closed connection to service SANDER_MEDIA
[2007/07/07 12:06:02, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.12. Error = Connection reset by peer
[2007/07/07 12:15:49, 1] smbd/service.c:make_connection_snum(950)
  media1 (192.168.1.12) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 8625)
[2007/07/07 12:22:23, 1] smbd/service.c:close_cnum(1150)
  media1 (192.168.1.12) closed connection to service SANDER_MEDIA
[2007/07/08 09:23:30, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/08 09:23:30, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/08 09:25:00, 1] smbd/process.c:async_processing(312)
  Reloading services after SIGHUP
[2007/07/08 09:25:00, 0] param/loadparm.c:service_ok(2940)
  WARNING: No path in service print$ - making it unavailable!
[2007/07/08 09:25:00, 1] param/loadparm.c:service_ok(2947)
  NOTE: Service print$ is flagged unavailable.
[2007/07/08 09:25:00, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/08 09:25:00, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/07/08 09:25:46, 1] smbd/service.c:make_connection_snum(950)
  media1 (192.168.1.12) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 5773)
[2007/07/08 09:31:21, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.12. Error = Connection reset by peer
[2007/07/08 09:31:21, 1] smbd/service.c:close_cnum(1150)
  media1 (192.168.1.12) closed connection to service SANDER_MEDIA
[2007/07/12 16:51:47, 0] smbd/negprot.c:reply_nt1(316)
  reply_nt1: smb signing is incompatible with share level security !
[2007/07/13 14:23:38, 0] smbd/service.c:make_connection_snum(849)
  Can't become connected user!
[2007/07/13 14:23:51, 1] smbd/service.c:make_connection_snum(950)
  media1 (192.168.1.199) connect to service SANDER_MEDIA initially as user sanderr (uid=1001, gid=100) (pid 3839)
[2007/07/13 14:29:55, 1] smbd/service.c:close_cnum(1150)
  media1 (192.168.1.199) closed connection to service SANDER_MEDIA
[2007/07/14 00:45:22, 0] smbd/service.c:make_connection_snum(849)
  Can't become connected user!
[2007/07/14 00:45:30, 1] smbd/service.c:make_connection_snum(950)
  media1 (192.168.1.199) connect to service SANDER_MEDIA initially as user sanderr (uid=1001, gid=100) (pid 6120)
[2007/07/14 00:51:52, 1] smbd/service.c:close_cnum(1150)
  media1 (192.168.1.199) closed connection to service SANDER_MEDIA
[2007/07/15 13:05:35, 0] smbd/service.c:make_connection_snum(849)
  Can't become connected user!
Log.192.168.1.199 (is echt heeeeeeeel lang...) Let op de tijdsoverlap van log.media1 en log.192.168.1.199. Ze zijn tegelijkertijd actief geweest??

[2007/07/09 22:55:16, 0] smbd/negprot.c:reply_nt1(316)
  reply_nt1: smb signing is incompatible with share level security !
[2007/07/09 22:55:18, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 2479)
[2007/07/09 23:04:20, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!

---
----

2007/07/10 00:00:30, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.199. Error = No route to host
[2007/07/10 00:00:30, 1] smbd/service.c:close_cnum(1150)
  192.168.1.199 (192.168.1.199) closed connection to service SANDER_MEDIA
[2007/07/10 10:37:24, 0] smbd/negprot.c:reply_nt1(316)
  reply_nt1: smb signing is incompatible with share level security !
[2007/07/10 10:37:24, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 2707)

----(deze regel heb ik een aantal (100 en) malen verwijderd uit het log hier---
2007/07/10 18:50:07, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
----(deze regel heb ik een aantal malen verwijderd uit het log hier---


[2007/07/11 10:16:36, 0] smbd/negprot.c:reply_nt1(316)
  reply_nt1: smb signing is incompatible with share level security !
[2007/07/11 10:16:38, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user nobody (uid=65534, gid=65534) (pid 4808)

----------Tijdsprong-----------

[2007/08/02 17:20:47, 1] smbd/service.c:close_cnum(1150)
  192.168.1.199 (192.168.1.199) closed connection to service SANDER_MEDIA
[2007/08/03 22:38:00, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user sanderr (uid=1001, gid=100) (pid 5191)

[2007/08/03 22:51:16, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/03 23:03:55, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/03 23:03:55, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!


[2007/08/10 19:29:16, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user sanderr (uid=1001, gid=100) (pid 2507)
[2007/08/10 19:32:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 19:32:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 04:51:38, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 04:51:38, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 05:04:38, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 05:04:38, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 10:55:06, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 10:55:06, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 10:57:03, 1] smbd/service.c:make_connection_snum(950)
  192.168.1.199 (192.168.1.199) connect to service SANDER_MEDIA initially as user sanderr (uid=1001, gid=100) (pid 6598)
[2007/08/11 11:08:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 16:09:37, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 16:10:57, 1] smbd/service.c:close_cnum(1150)
  192.168.1.199 (192.168.1.199) closed connection to service SANDER_MEDIA
[2007/08/11 16:10:57, 1] smbd/service.c:close_cnum(1150)
  192.168.1.199 (192.168.1.199) closed connection to service SANDER_MEDIA
PC 1, 192.168.1.151 p4-2400

log. 192.168.1.151 wordt vanaf juli niet meer bijgewerkt
log.p4-2400:

[2007/08/10 10:02:58, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Verbinding door partner opnieuw ingesteld
[2007/08/10 10:02:58, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/10 10:02:58, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 30138)
[2007/08/10 10:03:09, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 10:04:03, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Verbinding door partner opnieuw ingesteld
[2007/08/10 10:04:03, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/10 10:06:03, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Verbinding door partner opnieuw ingesteld
[2007/08/10 10:06:03, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/10 11:42:23, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 11:42:23, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 11:49:51, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2933)
[2007/08/10 11:59:19, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 11:59:20, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3171)
[2007/08/10 12:03:16, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 12:03:16, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 12:04:37, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 12:04:43, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3190)
[2007/08/10 12:04:43, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 12:04:43, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 12:04:53, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 12:14:24, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 12:14:24, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 12:37:48, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2571)
[2007/08/10 12:37:48, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2571)
[2007/08/10 12:37:57, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 12:37:57, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 12:38:20, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2574)
[2007/08/10 12:38:20, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2574)
[2007/08/10 12:38:28, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 12:38:28, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 12:38:58, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2576)
[2007/08/10 12:38:58, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2576)
[2007/08/10 12:39:07, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 12:39:07, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 12:46:23, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 12:46:23, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 13:26:43, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2914)
[2007/08/10 13:32:04, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 13:32:04, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 13:41:31, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2959)
[2007/08/10 13:41:31, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2959)
[2007/08/10 13:41:40, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 13:41:40, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 13:44:44, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 13:44:44, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!

--------regel heel vaak verwijderd----------------

[2007/08/10 16:05:33, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 16:17:23, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 16:30:24, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 16:30:24, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 16:35:21, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3535)
[2007/08/10 16:35:33, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 16:37:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 16:37:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 17:09:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 17:09:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 17:41:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 17:41:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 18:13:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 18:13:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 18:45:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 18:45:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 19:00:04, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 4003)
[2007/08/10 19:00:04, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 4003)
[2007/08/10 19:00:12, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:00:12, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 19:00:16, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 4005)
[2007/08/10 19:00:16, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 4005)
[2007/08/10 19:00:25, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:00:25, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 19:06:16, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 4074)
[2007/08/10 19:06:16, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 4074)
[2007/08/10 19:06:20, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:06:20, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 19:17:32, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 19:17:32, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 19:28:28, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2504)
[2007/08/10 19:28:28, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2504)
[2007/08/10 19:28:37, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:28:37, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 19:28:56, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2505)
[2007/08/10 19:28:56, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2505)
[2007/08/10 19:29:06, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:29:06, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 19:33:44, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2521)
[2007/08/10 19:40:34, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2541)
[2007/08/10 19:46:08, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:47:12, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 19:47:12, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 19:48:07, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2564)
[2007/08/10 19:48:18, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 19:48:33, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2575)
[2007/08/10 19:51:53, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.151. Error = Connection timed out
[2007/08/10 19:51:53, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Broken pipe
[2007/08/10 19:51:53, 0] lib/util_sock.c:send_smb(769)
  Error writing 75 bytes to client. -1. (Broken pipe)
[2007/08/10 20:02:21, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 20:02:21, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/10 20:04:52, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 20:06:02, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2677)
[2007/08/10 20:06:13, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 20:08:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 20:08:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 20:46:07, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2844)
[2007/08/10 20:46:07, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 2844)
[2007/08/10 20:46:17, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 20:46:17, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 21:30:12, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/10 21:30:12, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 21:30:12, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 2996)
[2007/08/10 21:30:22, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 21:44:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 21:44:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 22:04:12, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3104)
[2007/08/10 22:04:12, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 3104)
[2007/08/10 22:04:20, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 22:04:20, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/10 22:16:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 22:16:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 22:27:00, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 22:27:00, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 22:27:00, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3185)
[2007/08/10 22:27:10, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/10 23:49:09, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/10 23:49:09, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/10 23:49:09, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 3463)
[2007/08/11 00:03:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 00:03:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 10:45:56, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 10:57:02, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/11 11:04:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/11 11:04:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/11 11:36:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/11 11:36:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/11 11:53:18, 0] lib/util_sock.c:read_data(534)
  read_data: read failure for 4 bytes to client 192.168.1.151. Error = Connection reset by peer
[2007/08/11 11:53:18, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 6845)
[2007/08/11 11:53:41, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/11 15:20:19, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/11 15:20:19, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/11 16:25:57, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 7814)
[2007/08/11 16:26:09, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/11 16:38:31, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/11 16:38:31, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/11 16:38:31, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 7895)
[2007/08/11 16:51:59, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 16:51:59, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 17:04:51, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 17:04:51, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/11 17:05:30, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 00:30:38, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/12 00:30:38, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 00:30:38, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 9447)
[2007/08/12 00:30:49, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 00:32:11, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/12 00:32:11, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 00:34:11, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/12 00:34:11, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 00:57:23, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/12 00:57:23, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 00:57:23, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 9535)
[2007/08/12 00:57:33, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 01:06:11, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/12 01:06:11, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 01:34:08, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/12 01:34:08, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 01:34:08, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 9665)
[2007/08/12 01:47:44, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/12 01:47:44, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/12 01:57:39, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 07:32:04, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/12 07:32:04, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 07:32:05, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 11160)
[2007/08/12 07:32:16, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 07:33:56, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Connection reset by peer
[2007/08/12 07:33:56, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 12:18:37, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/12 12:18:37, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 12:18:37, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12099)
[2007/08/12 12:18:48, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 12:20:39, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Connection reset by peer
[2007/08/12 12:20:39, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Connection reset by peer)
[2007/08/12 12:41:34, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12337)
[2007/08/12 12:41:34, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 12337)
[2007/08/12 12:41:44, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 12:41:44, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/12 12:41:49, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12340)
[2007/08/12 12:41:49, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service sander initially as user sander (uid=1000, gid=1000) (pid 12340)
[2007/08/12 12:41:59, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 12:41:59, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service sander
[2007/08/12 12:44:57, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Verbinding door partner opnieuw ingesteld
[2007/08/12 12:44:57, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/12 12:44:57, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12350)
[2007/08/12 12:45:08, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 12:52:39, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Verbinding door partner opnieuw ingesteld
[2007/08/12 12:52:39, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/12 13:18:35, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Verbinding door partner opnieuw ingesteld
[2007/08/12 13:18:35, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/12 13:18:35, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12487)
[2007/08/12 13:18:46, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 13:18:48, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12488)
[2007/08/12 13:19:00, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 13:19:10, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12490)
[2007/08/12 13:19:21, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 13:32:52, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 0.0.0.0. Error Verbinding door partner opnieuw ingesteld
[2007/08/12 13:32:52, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/12 13:32:52, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12564)
[2007/08/12 13:33:03, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
[2007/08/12 13:43:34, 0] lib/util_sock.c:write_data(562)
  write_data: write failure in writing to client 192.168.1.151. Error Verbinding door partner opnieuw ingesteld
[2007/08/12 13:43:34, 0] lib/util_sock.c:send_smb(769)
  Error writing 4 bytes to client. -1. (Verbinding door partner opnieuw ingesteld)
[2007/08/12 13:43:34, 1] smbd/service.c:make_connection_snum(950)
  p4-2400 (192.168.1.151) connect to service SANDER_MEDIA initially as user sander (uid=1000, gid=1000) (pid 12612)
[2007/08/12 13:47:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/12 13:47:03, 0] printing/pcap.c:pcap_cache_reload(159)
  Unable to open printcap file /etc/printcap for read!
[2007/08/12 13:47:52, 1] smbd/service.c:close_cnum(1150)
  p4-2400 (192.168.1.151) closed connection to service SANDER_MEDIA
Graag hoor ik wat je hier over te zeggen hebt... ik snap het ff niet meer.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #8 Gepost op: 2007/08/12, 15:20:57 »
oh ja, log.nmbd:

[2007/08/12 06:33:11, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 06:48:17, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 07:03:23, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 07:18:29, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 07:33:32, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 07:48:37, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 08:03:43, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 08:18:49, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 08:33:55, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 08:49:01, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 09:04:07, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 09:19:13, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 09:34:19, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 09:49:25, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 10:04:31, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 10:19:37, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 10:34:43, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 10:49:49, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 11:04:56, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 11:20:02, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 11:35:08, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 11:50:14, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 12:05:20, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 12:20:22, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 12:33:27, 0] nmbd/nmbd.c:terminate(58)
  Got SIGTERM: going down...
[2007/08/12 12:33:27, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 192.168.1.255(138) ERRNO=Network is unreachable
[2007/08/12 12:33:27, 0] libsmb/nmblib.c:send_udp(791)
  Packet send failed to 192.168.1.255(138) ERRNO=Network is unreachable
[2007/08/12 12:33:36, 0] nmbd/nmbd.c:main(699)
  Netbios nameserver version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/08/12 12:33:36, 0] param/loadparm.c:map_parameter(2698)
  Unknown parameter encountered: "perferred master"
[2007/08/12 12:33:36, 0] param/loadparm.c:lp_do_parameter(3428)
  Ignoring unknown parameter "perferred master"
[2007/08/12 12:33:36, 0] nmbd/nmbd_subnetdb.c:create_subnets(190)
  create_subnets: No local interfaces !
[2007/08/12 12:33:36, 0] nmbd/nmbd_subnetdb.c:create_subnets(191)
  create_subnets: Waiting for an interface to appear ...
[2007/08/12 12:34:04, 0] nmbd/nmbd.c:main(699)
  Netbios nameserver version 3.0.24 started.
  Copyright Andrew Tridgell and the Samba Team 1992-2006
[2007/08/12 12:34:04, 0] param/loadparm.c:map_parameter(2698)
  Unknown parameter encountered: "perferred master"
[2007/08/12 12:34:04, 0] param/loadparm.c:lp_do_parameter(3428)
  Ignoring unknown parameter "perferred master"
[2007/08/12 12:39:49, 0] nmbd/nmbd_become_lmb.c:become_local_master_stage2(396)
  *****
 
  Samba name server BUTLER is now a local master browser for workgroup MSHOME on subnet 192.168.1.200
 
  *****
[2007/08/12 12:39:49, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 12:55:00, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 13:10:05, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 13:25:09, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 13:40:16, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 13:55:23, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 14:10:26, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 14:25:34, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 14:40:43, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 14:55:43, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.
[2007/08/12 15:10:43, 0] nmbd/nmbd_browsesync.c:find_domain_master_name_query_fail(351)
  find_domain_master_name_query_fail:
  Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.
  Unable to sync browse lists in this workgroup.

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #9 Gepost op: 2007/08/12, 16:50:45 »
Het feit dat je logbestanden hebt met IP en naam is normaal. Het duurt eventjes voor SAMBA weet welke naam overeen stemt met welk IP. Dus initieel wordt alles gelogd in het bestand met een IP, later in het bestand met de eigenlijke naam.
sander en sanderr bestaan ook als gebruiker op Butler en zijn voorzien van een samba passwoord?

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #10 Gepost op: 2007/08/12, 17:15:44 »
Voor zover ik weet wel

smbpasswd -a sanderr is uitgevoerd.

hoe kan ik het controleren of die gebruiker bestaat?

Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #11 Gepost op: 2007/08/12, 20:32:20 »
Even tussendoor een tip: wel naderhand je passwords even wijzigen, just in case.

Monk.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #12 Gepost op: 2007/08/12, 21:08:05 »
eh waarom? ik geef ze hier niet op toch?

Offline Pivni Pes

  • Lid
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #13 Gepost op: 2007/08/12, 22:31:02 »
Hallo,

Ik heb een beetje het zelfde probleem.
Ik kan een linux pc en een Win2000 pc niet schrijven in een map op mijn fileserver (Ubuntu)
Maar met een WinXP pc en Mac Osx pc weer wel.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #14 Gepost op: 2007/08/13, 07:55:48 »
KennyW,

Ik weet niet of je al tijd gehad hebt om te kijken maar hier vond ik nog iets over Samba.

Met name dat ik de nsswitch.onf en /etc/hosts moet aanpassen. Daarbij bestaat bij mij het bestand /etc/sm/smbusers helemaal niet.  (heb tuto van Timmen gevolgd toen)

Maar ik kan me slecht voor stellen dat ik elke pc handmatig in hosts moet zetten.....

Klopt dit verhaal? :

http://ictfreak.wordpress.com/2007/03/20/how-to-configure-samba-on-ubuntu-610/

en zo ja, deze is voor ubuntu 6.10 in hoeverre zal dit afwijken van feisty fawn en Debian zelf?

nogmaals bedankt voor de moeite.

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #15 Gepost op: 2007/08/13, 08:06:32 »
Bon, vanavond zit ik terug thuis achter mijn ubuntu machientje. Ik zal even proberen uw probleem te reproduceren. Nu werken :)

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #16 Gepost op: 2007/08/13, 19:02:16 »
Alvast bedankt kenny,

Weet je misschien ook waar dit vandaan komt? of liever, hoe ik het eruit krijg?

Unable to find the Domain Master Browser name MSHOME<1b> for the workgroup MSHOME.

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #17 Gepost op: 2007/08/13, 20:27:32 »
Bon, ik heb hier even uw situatie gereproduceerd op een virtuele machine. Ik kan met sander en sanderr schrijven in /home/sander/Media op voorwaarde dat /home/sander/Media volgend rechten heeft voor "others": rwx. Dus als je ls -l doet in /home/sander moet er voor Media dit staan:
drwxr-xrwx ... Media
Je doet dit door chmod o=rwx ./Media uit te voeren in /home/sander
Dit is echter een niet zo veilige situatie. Het zou beter zijn dat sander en sanderr in dezelfde groep zitten (bijvoorbeeld MijnGroep) en deze groep rwx rechten geven op deze folder en others totaal geen rechten.

De "Unable to find the Domain Master Browser" is normaal denk ik. Windows en uw samba machientjes houden verkiezingen om Domain Master Browser te worden. Ooit zal een van de machientjes winnen en verdwijnt ook die melding.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #18 Gepost op: 2007/08/23, 11:52:12 »
Maar ze zitten toch beide in de groep samba? of niet? als ik smbpasswd -a heb gedaan komen ze daar toch in ?

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #19 Gepost op: 2007/08/23, 13:21:43 »
Nope. smbpasswd zorgt er gewoon voor dat de betreffende gebruiker kan aanloggen op een samba share. Het toekennen van groepen wordt nog steeds gedicteerd door het /etc/groups bestand. Samba heeft daar niets met te maken.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #20 Gepost op: 2007/09/01, 03:18:42 »
Ha, daar is ie weer

Raar verhaal weer....

Voor zover ik weet hebben de gebruikers Sander en Sanderr dezelfde rechten in SMB.conf maar als ik mount met Sanderr kan ik sommige submappen niet lezen op de server en kan ik geen fotos bekijken.

Mount ik met Sander kan ik dat allemaal wel?

hoe kan dit?

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #21 Gepost op: 2007/09/01, 08:33:41 »
Post eens de output van de volgende commando's (op de machine waar de share staat):
- id sander
- id sanderr
- ls -l NaamVanDSubFolderDieJeNietKanLezen

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #22 Gepost op: 2007/09/01, 13:11:53 »
id sander (is tevens ook de gebruiker op deze pc)

Butler:/home/sander# id sander
uid=1000(sander) gid=1000(sander) groepen=1000(sander),20(dialout),24(cdrom),25(floppy),29(audio),44(video),46(plugdev)
id sanderr (kan niet inloggen, bash/false)

Butler:/home/sander# id sanderr
uid=1001(sanderr) gid=1002(sanderr) groepen=1002(sanderr)
Ik kwam er achter dat de rechten van de bestanden niet juist waren, allemaal -rw------- ..

Deze zijn vanuit een XP machine daar heen gekopieerd.

lordwodan

  • Gast
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #23 Gepost op: 2007/09/01, 16:31:30 »
Citaat van: kennywest
Nope. smbpasswd zorgt er gewoon voor dat de betreffende gebruiker kan aanloggen op een samba share. Het toekennen van groepen wordt nog steeds gedicteerd door het /etc/groups bestand. Samba heeft daar niets met te maken.
Hoi Kenny,

Deze post staat toch haaks op jouw antwoord op mijn vraag..

http://forum.ubuntu-nl.org/topic/14137#9

Moet er dus toch een groep zijn?

Offline kennywest

  • Lid
    • http://kennywest.blogspot.com
Samba share niet schrijven met ubuntu-client ,wel met windows-client
« Reactie #24 Gepost op: 2007/09/01, 16:41:00 »
Neen, eigenlijk niet. In jouw post suggereerde je dat het toekennen van een smb paswoord aan een gebruiker er automatisch voor zorgt dat deze gebruiker in een "samba" groep zou komen. Dat is niet het geval.
Het feit dat bestanden -rw------ permissies hebben is logisch. Je zal het create mask moeten aanpassen zodat op zijn minst een gemeenschappelijke groep toegang heef. Dus -rw-rw--- ofte mask 0077 (dacht ik). Zorg er ook voor dat de gebruikers in een gemeenschappelijke groep zitten, bijvoorbeeld sanders.