RE: Warning messages not being sent

Rainer Link wrote:
> Plant, Dean wrote:
> 
>> I am testing samba-vscan 0.3.5 / clamav 0.75-1 with samba 3.0.7
>> built from source on Solaris 9.
> [..]
>> [2004/10/15 12:46:06, 5]
>> global/vscan-message.c:vscan_send_warning_message(88)
>>   session request failed
> 
>> Anyone any idea as to what may be stopping the message. I can
>> successfully send a message to the remote machine using smbclient.
> 
> Sorry for the late reply, I was ill. I had a short discussion with
>   Metze today but so far no real idea.
> 
> Would it be possible to get a ethereal capture of the SMB traffic with
> samba-vscan  and smblcient -M to see what's the difference here. I
> will also send you a small diff by tomorrow which adds some more debug
> statements to the samba-vscan which hopfefully helps to track this
> issue down.
> 
> Thanks
> 
> best regards
> Rainer Link

Thanks for your reply, hope your feeling better.

I have looked into this further and it seems to be a problem with samba not
being able to correctly resolve the IP/name.

On the SWAT status page I noticed that most active connections don't show
client machine names, so it looks like I have a samba mis-configuration and
not a samba-vscan problem.

PID	Client		IP address		Date 		
746	193.118.198.186	193.118.198.186	Fri Oct 15 16:04:15 2004

On rebooting one of my test client machines and then connecting to the virus
scanned share, the name was correctly displayed in the SWAT status page and
notifications were then sent and displayed on the client.

I'm going on holiday tomorrow for a few weeks so I will continue my tests
when I come back.

Thanks for your help.

Dean Plant


-------------------------------------------------------
This SF.net email is sponsored by: IT Product Guide on ITManagersJournal
Use IT products in your business? Tell us what you think of them. Give us
Your Opinions, Get Free ThinkGeek Gift Certificates! Click to find out more
http://productguide.itmanagersjournal.com/guidepromo.tmpl