[Samba] Win2k and Samba

[Kurt Weiss]

hi again!

Al Bean schrieb:

> 
> The first few entries are on trying to copy a file from win2k to the 
> linux share.
> The last few entries are on trying to delete a file on the linux share.
> 


> As you can see from the conf file the path to the linux share is "/ark"
> and I'm copying from the win2k desktop to that linux share so the path is:
> "C:\Documents and Settings\Administrator\Desktop\"
> I know the "/ark" path is not deep and I really don't thing the path to 
> the desktop is that deep either.

ok - i believe - it's not that i thought ;-)

> ---------------------------
> [2003/02/23 08:45:25, 0] lib/util_sock.c:read_data(436)
>  read_data: read failure for 19168. Error = Connection reset by peer
> [2003/02/23 08:52:57, 0] lib/util_sock.c:read_data(436)
>  read_data: read failure for 29388. Error = Connection reset by peer
> [2003/02/23 09:11:06, 0] lib/util_sock.c:read_data(436)
>  read_data: read failure for 49828. Error = Interrupted system call
> [2003/02/23 09:14:09, 0] smbd/oplock.c:request_oplock_break(981)
>  request_oplock_break: no response received to oplock break request to 
> pid 968 on port 1029 for dev = 303, inode = 140233, fi
> le_id = 2
> [2003/02/23 09:14:41, 0] smbd/oplock.c:request_oplock_break(981)
>  request_oplock_break: no response received to oplock break request to 
> pid 968 on port 1029 for dev = 303, inode = 140233, fi
> le_id = 2
> [2003/02/23 09:15:13, 0] smbd/oplock.c:request_oplock_break(981)
>  request_oplock_break: no response received to oplock break request to 
> pid 968 on port 1029 for dev = 303, inode = 140233, fi
> le_id = 2

what's that? - seems, something is running bad in network communication!
i'm looking for the errno. (436) -stay tuned

>        encrypt passwords = Yes
>        obey pam restrictions = Yes
 >        pam password change = Yes

man smb.conf:
"Note that samba always ignores PAM for authentication in case of 
"encrypt password = yes"
(samba 2.2.4)


>        socket options = TCP_NODELAY IPTOS_LOWDELAY SO_SNDBUF=8192 
> SO_RCVBUF=8192

only an idea: won't u play with this to see, which effect it has to your 
error log?

>        local master = No
>        dns proxy = No
>        remote announce = 192.168.0.255
>        remote browse sync = 192.168.0.255
>        hosts allow = 192.168.0. 127.
>        case sensitive = Yes

i think, that's dangerous: windows mostly changes case! - try 'no'


so i hope it helped
gk