Bug 2513 - Contents of services occasionally confused
Summary: Contents of services occasionally confused
Status: RESOLVED FIXED
Alias: None
Product: Samba 3.0
Classification: Unclassified
Component: File Services (show other bugs)
Version: 3.0.11
Hardware: Sparc Solaris
: P3 normal
Target Milestone: none
Assignee: Samba Bugzilla Account
QA Contact: Samba QA Contact
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-03-22 01:25 UTC by Sean Wang
Modified: 2006-04-14 14:59 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Sean Wang 2005-03-22 01:25:53 UTC
Envioronment description:
A Solaris 8 server acts as a file server in the domain, using Samba 3.0.11. 
User authentication is done by another DC/(Win2K Server) via usermap. There are 
more than 40 Win2K clients who need to access Samba.

I opened several share folders on SambaServer, for example, Service_A & 
Service_B. Clients will frequently connect to both Service_A & Service_B.  I 
set deadtime to 1 minute to shutdown idle connections. So the connection will 
be shutdown randomly depending on the idle time.

Issues found:
Sometime when a user click on \\SambaServer\Service_B with his explorer,  the 
content of \\SambaServer\Service_A is listed instead. The user has to wait 
until the deadtime expires and try again and  succeed. I set log level to 5, 
and find no any clue either in the log file nor the source code.  I am really 
puzzled. Is it a netbios problem of Win2K system or a bug of Samba? (I met this 
issue also when SambaServer is running  Samba 2.0.7, but this never happened to 
Samba2.2.2). 
Another point is that when user_A logs off from a workstation, and another user 
B logs on soon after that(the connection is not shutdown by Samba). User_B 
could view the home directory of User_A on SambaServer, but actually this 
directory is a fake directory, while clicking on it, it's directed to User_B's 
home directory too.
Comment 1 Gerald (Jerry) Carter (dead mail address) 2006-04-14 14:59:41 UTC
Please retest against a current release and reopen if the issue is still present.