I have had a Snap4100 Server in my Win 2003 AD Domain environment for some time now and I have been dealing with the the following issue:
A user logs in and connects to a share on the Snap using the Snap’s domain authentication feature. However, if that user logs off; all subsequent users that log onto this very same client cannot connect to any share on the Snap. The Snap debug log show that the first user is still authenticated while the new user is logging in
Here is what the log shows:
————————–
06/18/2005 14:01:01 68 D SMB | SMB : Attempt by OPERATIONSPC(IP) to login as jsmith while already logged in as swhite
06/18/2005 14:01:01 68 D SMB | SMB : Attempt by OPERATIONSPC(IP) to login as jsmith while already logged in as swhite
—————————
Well the outcome is that jsmith is unable to connect to any shares, but get a challenge login box instead. If he enters his credentials it denies him, but if I enter the Administrator credentials; it works.
Why does the Snap still think swhite is connected/logged in?
I have a case open with Adaptec, but they seem stumped as of yet…