Annoying Samba Errors in Logs

[Giddens, Scott]

All day long I get these messages from smbd:

Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error] [2004/12/28
07:27:24, 0] smbd/service.c:(252)
Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error]   rhunt1-pc
(162.18.178.237) couldn't find service o

The last part, "couldn't find service o" is when the user is accessing a
share name "OESDL" but the name is truncated. I know this because the
other errors have more letters that correspond to the shared directory,
not the name. I also know this because the directory name "oesdl" is in
lower case. The next example shows a successful connection to the share
name "JWST". Note the truncated "jws" in reference to the "jwst"
directory.

Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error] [2004/12/28
07:27:24, 0] smbd/service.c:(252)
Dec 28 07:27:24 srv-pvcs smbd[638]: [ID 702911 daemon.error]   rhunt1-pc
(162.18.178.237) couldn't find service jws

This is not a fatal error but an extremely irritating numerous repeating
log message to us anal sys admins that we must cut out of the logs to
find the needle in the haystack when we scan the server logs. Other than
that the samba service runs perfectly.

This server provides a flat file database for a product called PVCS VM.
A version managing software for maintaining versions of software code. I
thought maybe it could be an issue with oplocks but I have not been able
to confirm that.

Is this a Windows DNS or WINS error message?

Thanks,
Scott