I get the same behavior on Ubuntu 6.06 with Samba 3.0.22 so it isn't just you. I notice that when an XP client first connects, the share behaves as it should with file and folder deletions showing up immediately. If left sitting with a share open for a few minutes, the behavior starts. You can test this by closing a share, reopening it on your XP client and then create some files in the share on another computer via remote desktop. If you size your windows correctly, you can put them side by side to watch it happen.

I played with some of the timeout settings in smb.conf to see if that made a difference. It didn't. I haven't tried FAM.

Honestly, I haven't had anyone complain about this. In fact, I haven't had anyone mention it at all. But I've known about the behavior for a while now.

What I think is interesting is how the Microsoft article you linked to shows that XP had this issue at one point in time with other Windows shares. My guess is that somewhere along the way, they broke their own share code and then fixed it later thereby breaking XP clients and Samba. Just a guess.

It would be interesting to see what happens with an unpatched XP client. My gut feeling is that shares would update as expected.


David Schulz wrote:
i tried now to install fam, dont really know how it works. got it started though, but to no avail. dont you think the issue is in xp itself? when connecting with a macosx machine to the samba share, i do not get this problem.

thanks
david

On Nov 29, 2006, at 8:42 PM, Volker Lendecke wrote:

On Wed, Nov 29, 2006 at 08:35:49PM +0800, David Schulz wrote:
sorry, i do not have this Problem on another Server using the same OS
and Windows XP as Clients. I cant believe that this is acceptable to
Users, there must be a way to improve this. :(

Does running with FAM help?

Volker
!DSPAM:1084,456d807a6571110418642!


--To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba


--
To unsubscribe from this list go to the following URL and read the
instructions:  https://lists.samba.org/mailman/listinfo/samba

Reply via email to