Hello Andrew, Andrew Bartlett wrote: >> Oct 27 01:51:57 linuxamd64 smbd[6686]: [2005/10/27 01:51:57, 0] >> lib/util_sock.c:get_peer_addr(1150) >> Oct 27 01:51:57 linuxamd64 smbd[6686]: getpeername failed. Error was >> Transport endpoint is not connected
>The client (XP) makes two connections to the server, one 1ms after the >other. The second one to be accepted is then dropped. Or perhaps you >just had a client suddenly reboot, or a number of other things. >This is normal, we really should push it down to debug 2... There is this only logentry in var/log/samba/smbd, when I want to connect Win XP workstation to smb/ldap domain. There is no other, 1ms later: [2005/10/26 16:24:04, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2005/10/26 16:26:28, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected >> Oct 27 01:37:55 linuxamd64 kernel: end_request: I/O error, dev fd0, sector 0 >Put a floppy in the drive :- I have installed no floppy in my Suse server! I have build out the floppy, because hardware tools indicated device read fault. Thanks a lot Andreas -- To unsubscribe from this list go to the following URL and read the instructions: https://lists.samba.org/mailman/listinfo/samba
