Loss of Samba service after 5 days

[Asa Beattie]

I'm having two problems with Samba that only occur when I use versions
later than 2.0.4.  The main problem is that the server becomes
inaccessible from PCs occasionally. This is easily cured by stopping and
restarting Samba but it is a bit annoying. With Samba 2.0.5 this
behaviour would occur randomly about three times a week. Using Samba
2.0.7 it seems to occur once every five days. Has anyone else
experienced this problem? 

Possibly unrelated error is the following error messages filling up
log.UNKNOWN in my samba log directory:

[2000/08/22 09:29:48, 0] lib/util_sock.c:(999)
  getpeername failed. Error was Bad file number
[2000/08/22 09:32:49, 0] lib/util_sock.c:(999)
  getpeername failed. Error was Bad file number
[2000/08/22 09:32:49, 0] lib/util_sock.c:(999)
  getpeername failed. Error was Bad file number
[2000/08/22 09:35:57, 0] lib/util_sock.c:(999)
  getpeername failed. Error was Bad file number
[2000/08/22 09:35:57, 0] lib/util_sock.c:(999)
  getpeername failed. Error was Bad file number

I am currently using Samba 2.0.7 on Solaris 7. I would be very grateful
for any advice, let me know if there's more information I need to
supply.

Thanks,

Asa

__________________________
Asa Beattie, IT Systems Administrator
WS Atkins Consultants, Bristol, UK
01454 628729   abeattie at wsatkins.co.uk