Anzeige:
Ergebnis 1 bis 6 von 6

Thema: Samba-PDC - Fehlermeldung bei Zugriff auf Freigaben

  1. #1
    Registrierter Benutzer
    Registriert seit
    Jan 2005
    Beiträge
    6

    Samba-PDC - Fehlermeldung bei Zugriff auf Freigaben

    Hallo zusammen,

    ich hoffe ihr könnt mir weiterhelfen.

    Wenn ich mit meinen XP-Clients auf den Samba-Freigaben arbeite, bekomme ich häufig Fehlermeldungen beim Ändern, Erstellen und Löschen von Dateien.

    Wenn ich bespielsweise das Archivbit einer Datei ändere kommt folgender Fehler:



    Die Änderungen werden aber trotzdem vorgenommen
    .
    Aber nur beim ersten Mal - nur wenn ich die Fenster schliesse und mich erneut mit dem Server verbinde kommt der Fehler wieder.

    Ebenso beim Löschen mehrerer Dateien. Wenn ich diese markiere und dann lösche kommt folgender Fehler:



    Er löscht dann auch nur eine Datei und zwar die die in der Fehlermeldung genannt wird. Die anderen vorher markierten sind noch da! Dieser Fehler tritt nur nach dem ersten Verbinden mit dem Sambaserver auf - wenn ich längere Zeit auf der Freigabe arbeite kommen keine Fehler.


    Ein andres Problem besteht schon beim Zugriff auf die Domäne über die Netzwerkumgebung von den XP-Clients aus.
    Dort bekommen ich folghenden Fehler:



    Das kann schon 3-4 mal passieren, dann gehts plötzlich und ich kann mich auf den Server verbinden.

    Ebenso tritt der ein Fehler beim Kopieren Dateien auf. Zwar angelegt diesewerden, dieser aber nicht gefüllt! Nur beim einzelnen Kopieren der Dateien klappt die Chose!

    Hat keiner eine Idee? Puffer, Cache??

    Sepp Ultura
    Geändert von Ulturasepp (14.02.05 um 10:46 Uhr)

  2. #2
    Registrierter Benutzer
    Registriert seit
    Jun 2004
    Beiträge
    801
    Die Fehlermeldungen von WIndows sagen mir nicht viel, da sind mir die Logs vom Sambaserver lieber und zeig uns die betroffene Freigabe mit ls -al Ausgabe.

    Hast du ein chmod 777 share gemacht? Im smb.conf wird create mask und directory mask verwendet?

  3. #3
    Registrierter Benutzer
    Registriert seit
    Jan 2005
    Beiträge
    6
    Danke für die Nachfrage Fly! Werde versuchen Deine Fragen zu beantworten!

    Habe hier mal nen Auszug aus der log.smbd ! Denke mal da sind die Fehler gut zu sehen - leider kann ich damit nicht viel anfangen.

    Klick mich!

    Code:
    [2005/02/14 15:09:27, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 930)
    [2005/02/14 15:09:30, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:09:30, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:09:30, 0] lib/util_sock.c:write_socket_data(430)
      write_socket_data: write failure. Error = Connection reset by peer
    [2005/02/14 15:09:30, 0] lib/util_sock.c:write_socket(455)
      write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer
    [2005/02/14 15:09:30, 0] lib/util_sock.c:send_smb(647)
      Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2005/02/14 15:09:31, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1702)
    [2005/02/14 15:09:31, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:09:31, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1702)
    [2005/02/14 15:09:38, 1] smbd/ipc.c:api_fd_reply(292)
      api_fd_reply: INVALID PIPE HANDLE: 7065
    [2005/02/14 15:09:40, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe2 initially as user user1 (uid=0, gid=100) (pid 1702)
    [2005/02/14 15:10:01, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1710)
    [2005/02/14 15:10:01, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:10:01, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1710)
    [2005/02/14 15:10:07, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe2 initially as user user1 (uid=0, gid=100) (pid 1710)
    [2005/02/14 15:10:09, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe2
    [2005/02/14 15:10:10, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:10:42, 1] smbd/ipc.c:api_fd_reply(292)
      api_fd_reply: INVALID PIPE HANDLE: 7793
    [2005/02/14 15:10:43, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1713)
    [2005/02/14 15:10:46, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1715)
    [2005/02/14 15:10:48, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:10:48, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1715)
    [2005/02/14 15:10:48, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:10:49, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1716)
    [2005/02/14 15:10:52, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:10:52, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:10:52, 0] lib/util_sock.c:write_socket_data(430)
      write_socket_data: write failure. Error = Connection reset by peer
    [2005/02/14 15:10:52, 0] lib/util_sock.c:write_socket(455)
      write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer
    [2005/02/14 15:10:52, 0] lib/util_sock.c:send_smb(647)
      Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2005/02/14 15:10:52, 1] smbd/service.c:make_connection_snum(648)
      pc2 (192.168.222.9) signed connect to service Freigabe2 initially as user user3 (uid=0, gid=100) (pid 1718)
    [2005/02/14 15:10:59, 1] smbd/service.c:close_cnum(837)
      sccenic-2 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1716)
    [2005/02/14 15:10:52, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:10:52, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:10:52, 0] lib/util_sock.c:write_socket_data(430)
      write_socket_data: write failure. Error = Connection reset by peer
    [2005/02/14 15:10:52, 0] lib/util_sock.c:write_socket(455)
      write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer
    [2005/02/14 15:10:52, 0] lib/util_sock.c:send_smb(647)
      Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2005/02/14 15:10:52, 1] smbd/service.c:make_connection_snum(648)
      pc2 (192.168.222.9) signed connect to service Freigabe2 initially as user user3 (uid=0, gid=100) (pid 1718)
    [2005/02/14 15:10:59, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    nic-2 (192.168.222.24) closed connection to service Freigabe1
    
    
    
    
    [2005/02/14 15:21:59, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:21:59, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:21:59, 0] lib/util_sock.c:write_socket_data(430)
      write_socket_data: write failure. Error = Connection reset by peer
    [2005/02/14 15:21:59, 0] lib/util_sock.c:write_socket(455)
      write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer
    [2005/02/14 15:21:59, 0] lib/util_sock.c:send_smb(647)
      Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2005/02/14 15:22:01, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe2 initially as user user1 (uid=0, gid=100) (pid 1775)
    [2005/02/14 15:22:04, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1775)
    [2005/02/14 15:22:07, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:22:07, 0] lib/util_sock.c:get_peer_addr(1000)
      getpeername failed. Error was Transport endpoint is not connected
    [2005/02/14 15:22:07, 0] lib/util_sock.c:write_socket_data(430)
      write_socket_data: write failure. Error = Connection reset by peer
    [2005/02/14 15:22:07, 0] lib/util_sock.c:write_socket(455)
      write_socket: Error writing 4 bytes to socket 25: ERRNO = Connection reset by peer
    [2005/02/14 15:22:07, 0] lib/util_sock.c:send_smb(647)
      Error writing 4 bytes to client. -1. (Connection reset by peer)
    [2005/02/14 15:22:07, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1777)
    [2005/02/14 15:22:07, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:22:07, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1777)
    [2005/02/14 15:22:10, 1] smbd/ipc.c:api_fd_reply(292)
      api_fd_reply: INVALID PIPE HANDLE: 72e8
    [2005/02/14 15:22:14, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:22:35, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1780)
    [2005/02/14 15:22:42, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1781)
    [2005/02/14 15:22:42, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:22:42, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1781)
    
    
    
    
    [2005/02/14 15:30:10, 1] smbd/ipc.c:api_fd_reply(292)
      api_fd_reply: INVALID PIPE HANDLE: 72df
    [2005/02/14 15:30:11, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1845)
    [2005/02/14 15:30:12, 0] rpc_server/srv_netlog_nt.c:get_md4pw(244)
      get_md4pw: Workstation GDS$: no account in domain
    [2005/02/14 15:30:14, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:14, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:14, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:14, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:16, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:16, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:16, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:16, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:20, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:21, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:21, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:21, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:23, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:23, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:23, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1849)
    [2005/02/14 15:30:23, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:46, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1855)
    [2005/02/14 15:30:53, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1856)
    [2005/02/14 15:30:55, 1] smbd/service.c:close_cnum(837)
      pc1 (192.168.222.24) closed connection to service Freigabe1
    [2005/02/14 15:30:56, 1] smbd/service.c:make_connection_snum(648)
      pc1 (192.168.222.24) signed connect to service Freigabe1 initially as user user1 (uid=0, gid=100) (pid 1856)
    [2005/02/14 15:31:29, 1] smbd/service.c:make_connection_snum(648)
      pc3 (192.168.222.71) signed connect to service Freigabe2 initially as user user2 (uid=0, gid=100) (pid 1869)
    Hier die smb.conf:

    Code:
    [global]
            workgroup = testdomain
            printcap cache time = 750
            cups options = raw
            printer admin = @ntadmin, root, administrator
            username map = /etc/samba/smbusers
            map to guest = Bad User
            include = /etc/samba/dhcp.conf
            logon path = \\%L\profiles\.msprofile
            logon home = \\%L\%U\.9xprofile
            logon drive = P:
            add machine script = /usr/sbin/useradd  -c Machine -d /var/lib/nobody -s /bin/false %m$
            domain logons = yes
            domain master = yes
            security = user
            ldap idmap suffix = ou=Idmap
            ldap machine suffix = ou=Computers
            os level = 65
            preferred master = yes
            ldap suffix = dc=example,dc=com
            restrict anonymous = no
            max protocol = NT
            ldap ssl = No
            server signing = Auto
            min password length = 0
            encrypt passwords = yes
            server string = testserver
    
    [homes]
            comment = Home Directories
            valid users = %S
            browseable = no
            read only = no
            inherit acls = yes
    
    [profiles]
            comment = Network Profiles Service
            path = %H
            read only = no
            store dos attributes = yes
            create mask = 0600
            directory mask = 0700
            browseable = no
    
    [users]
            comment = All users
            path = /home
            read only = no
            inherit acls = yes
            veto files = /aquota.user/groups/shares/
            browseable = no
    
    [groups]
            comment = All groups
            path = /home/groups
            read only = no
            inherit acls = yes
    		browseable = no
    
    [pdf]
            comment = PDF creator
            path = /var/tmp
            printable = yes
            print command = /usr/bin/smbprngenpdf -J '%J' -c %c -s %s -u '%u' -z %z
            create mask = 0600
            browseable = no
    
    [printers]
            comment = All Printers
            path = /var/tmp
            printable = yes
            create mask = 0600
            browseable = no
    
    [print$]
            comment = Printer Drivers
            path = /var/lib/samba/drivers
            write list = @ntadmin root
            force group = ntadmin
            create mask = 0664
            directory mask = 0775
    
    [test]
            comment = test
            path = /test/
            writeable = yes
            browswable = yes
            guest ok = yes
            create mask = 0777
            directory mask = 0777
            security mask = 0777
            directory security mask = 0777
            nt acl support = yes
            dos filemode = yes
            valid users = @testgroup,testuser
            admin users = @testgroup,testuser
    Wie Du siehst wird create mask und directory mask verwendet!!


    Hier die Ausgabe bei ls -al :

    Code:
    Freigabe:
    
    drwxrwxrwx    5 root root    120 Feb 14 15:30 test
    
    
    Ordner in der Freigabe:
    
    drwxrwxrwx   5 root root  120 Feb 14 15:30 .
    drwxr-xr-x  24 root root  608 Feb  9 17:12 ..
    drwxrwxrwx   2 root users  48 Feb 14 15:30 test1
    drwxrwxrwx   2 root users  48 Feb 14 15:30 test2
    drwxrwxrwx   2 root users  48 Feb 14 15:30 test3


    Hoffe Du kannst mir weiterhelfen!

    Gruss Ulturasepp

  4. #4
    Registrierter Benutzer
    Registriert seit
    Jan 2005
    Beiträge
    6
    So die momentane Freigabe in der smb.conf sieht so aus:


    Code:
    [Intranet]
    comment = test
    path = /test/
    read only = no
    guest ok = yes
    browseable = yes
    writeable = yes
    directory mask = 0777
    create mask = 0777
    dos filemode = yes
    nt acl support = yes
    case sensitive = no
    msdfs proxy = no
    valid users = @testgroup
    admin users = testuser
    Ich habe auch gestern mal den Server neugestartet und siehe da es geht wieder! Es kommt keine Fehlermeldung mehr!
    Würde aber gerne wissen warum! An der neuen smb.conf liegt es meiner Meinung nach nicht!
    Is da evtl irgendein Speicher, Cache etc. vollgelaufen???? Wenn ja wie kann ich da vorbeugen?
    Geändert von Ulturasepp (15.02.05 um 10:02 Uhr)

  5. #5
    Registrierter Benutzer
    Registriert seit
    Apr 2004
    Beiträge
    23
    Hey

    Binde mal deinen Samba an ein interface
    und/ oder versuch mal das Netzwerk mit host allow im Samba festzulegen
    Welche Samba Version hast du. Die 3.x sollen dahingehend eine Bug haben

    By Huflatisch

  6. #6
    Registrierter Benutzer
    Registriert seit
    Jan 2005
    Beiträge
    6
    Habe Samba 3 !!

    So habe jetzt mit hosts allow die erlaubten IP-Ranges festegelegt! Sieht bisher gut aus! Bisher keine Fehler aufgetreten.

    Was bewirkt das Binden von Samba an ein Interface?
    Ich habe 2 Netzwerkkarten drin.
    Interface1 für die Domäne wo der Linuxserver PDC ist und Interface2, die trusted Domain! Domain an Interface 2 kann auf Domain an Inteface1 zugreifen aber nicht umgekehrt!
    Will da nix kaputtmachen wenn ich Samba an eins binde - läuft nämlich ganz gut!

Ähnliche Themen

  1. Immer diese Sysadmin
    Von Sven_R im Forum Meldungen und Mitglieder
    Antworten: 15
    Letzter Beitrag: 27.01.05, 16:44
  2. Kein Zugriff auf Ordenr möglich unter Samba
    Von heinzelrumpel im Forum Linux in heterogenen Netzen
    Antworten: 2
    Letzter Beitrag: 01.10.04, 10:19
  3. Von Windows PDC auf Samba PDC konvertieren
    Von JD10 im Forum Linux in heterogenen Netzen
    Antworten: 1
    Letzter Beitrag: 02.11.03, 19:16
  4. freeswan - Linux-Gateway/Linux-Roadwarrior
    Von schuelsche im Forum Sicherheit
    Antworten: 96
    Letzter Beitrag: 21.07.03, 11:45
  5. Passwörter auf Benutzerebene bei Samba als PDC
    Von im Forum Linux in heterogenen Netzen
    Antworten: 2
    Letzter Beitrag: 10.08.02, 15:22

Lesezeichen

Berechtigungen

  • Neue Themen erstellen: Nein
  • Themen beantworten: Nein
  • Anhänge hochladen: Nein
  • Beiträge bearbeiten: Nein
  •