[Samba] Server crash when desktop PALM Sync with Samba mapped drive

[Sam Chow]

Hello, I am new to Samba and to this mailing list so please excuse my
ignorance.

I have a situation where when a user syncs his Desktop PALM V PDA to his
Windows 2000 PRo
PC - user account being a Samba mapped drive, the Server crashes...any
clues???

endpoint is not connected
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
get_peer_addr(1000)
Jan  4 16:42:06 myserver smbd[10914]:   getpeername failed. Error was
Transport
 endpoint is not connected
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/access.c:che
ck_access(328)
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
get_peer_addr(1000)
Jan  4 16:42:06 myserver smbd[10914]:   getpeername failed. Error was
Transport
 endpoint is not connected
Jan  4 16:42:06 myserver smbd[10914]:   Denied connection from  (0.0.0.0)
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
get_peer_addr(1000)
Jan  4 16:42:06 myserver smbd[10914]:   getpeername failed. Error was
Transport
 endpoint is not connected
Jan  4 16:42:06 myserver smbd[10914]:   Connection denied from 0.0.0.0
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
write_socket_data(430)
Jan  4 16:42:06 myserver smbd[10914]:   write_socket_data: write failure.
Error
 = Connection reset by peer
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
write_socket(455)
Jan  4 16:42:06 myserver smbd[10914]:   write_socket: Error writing 5 bytes
to
socket 22: ERRNO = Connection reset by peer
Jan  4 16:42:06 myserver smbd[10914]: [2005/01/04 16:42:06, 0]
lib/util_sock.c:
send_smb(647)
Jan  4 16:42:06 myserver smbd[10914]:   Error writing 5 bytes to client. -1.
(C
onnection reset by peer)
Jan  4 16:42:06 myserver smbd[10915]: [2005/01/04 16:42:06, 0]
lib/username.c:m
ap_username(128)
Jan  4 16:42:06 myserver smbd[10915]:   can't open username map no username
map
. Error No such file or directory
Jan  4 18:09:39 myserver syslogd 1.4.1: restart.
Jan  4 18:09:39 myserver syslog: syslogd startup succeeded
Jan  4 18:09:39 myserver kernel: klogd 1.4.1, log source = /proc/kmsg
started.
Jan  4 18:09:39 myserver kernel: Linux version 2.6.8-1.521
(bhcompile at tweety.bu
ild.redhat.com) (gcc version 3.3.3 20040412 (Red Hat Linux 3.3.3-7)) #1 Mon
Aug