samba - Oct 1997 - Problems with 1.9.17p2

We upgraded from 1.9.16p10 to 1.9.17p2 about two weeks ago.  Following 
the upgrade we experienced problems with the performance being much 
slower, particularly stalls on reconnecting after timeout.  
Occasionally, we also experienced SAMBA services not being available 
("The network path was not found") temporarily (similar time delays to
the stalls), and then becoming available again without any intervention 
on the Unix side.    Judging from the list messages, other have 
experienced possibly similar problems on Windows 95.  (We are using NT.)

We have not time to make a detailed investigation currently.  I have 
reverted our Samba servers to 1.9.16p10 and the problem seems to have 
gone away.  I am keen to know what the cause of this might be, and 
whether it is an identified problem in 1.9.17 series.  Has it been 
fixed in 1.9.17p3 or 1.9.17p4?

Andrew

=====================================================================Dr Andrew
Boswell		email : A.Boswell@uea.ac.uk
Computing Centre		phone : +44-1603-592386
University of East Anglia	fax   : +44-1603-593467
Norwich, NR4 7TJ, UK

These views are personal unless otherwise stated.

Remove #NOSPAM# from email address when replying.

I have experienced some of these symptoms using 95 clients that use a
Samba box for WINS resolution.  I upgraded from 1.9.16p11 to 1.9.17p3 using
the same configurations and discovered that the server would disappear from
the network neighborhood at random sometime after connecting.  On some
occasions the server would never appear.  On occasions when it did not
appear connections set up to reconnect at log on would fail, but I was able
to reconnect using net use.

	The problem has not occur for systems on the same subnet.

	Comments and suggestions are appreciated.

	Thanks,

	Ben Fornshell