serious application crash during cliconnect session_request
mthomas at rhrk.uni-kl.de
Tue Jan 29 13:19:07 GMT 2002
could someone please explain this entries in a smbd.log:
[2002/01/29 17:08:05, 0] libsmb/cliconnect.c:attempt_netbios_session_request(839)
attempt_netbios_session_request: SCRATCHY rejected the session for name *SMBSEVER \
with error Not listening on calling name
[2002/01/29 17:08:05, 0] rpc_client/cli_spoolss_notify.c:spoolss_connect_to_client(75)
connect_to_client: machine SCRATCHY rejected the NetBIOS session request. Error was code 0
[2002/01/29 18:31:24, 2] lib/access.c:check_access(318)
Allowed connection from (220.127.116.11)
This happened while someone used MS Word 2000 (sp-1, german) on an
Windows 2000 client (sp-2, german). Word crashed and when the user
opened his document again it was broken and the text consisted of parts
of the "log.smbd.scratchy" file and a lot of 'nonsense'. So some parts of the
internal samba log files are now in the users broken word document file,
which is frightening.
Server is a linux box (Kernel 2.4.16) with Samba 2.2.2, compiled with no special options.
Printing works without problems. The printer setup on the clients was done before
the new print support.
On the clients 'file and print sharing' is disabled in the settings for the network-connection
for security reasons which my result in the 'not listening' error. As you can see, the next
entry in the log after the error was more than one hour later after I restartet the
samba server. Although the user worked with other files on different shares before the
restart there where no more entries for this in the log for his machine.
Please help - thank you.
University of Kaiserslautern, Institute of Environmental Engineering,
Kaiserslautern (ZIP 67663), Germany
More information about the samba-technical