CCIUG'ers:
Just got off the phone with TAS support and Rational and finally found
some interesting info:
(for background information concerning the problem, see the email to TAS
support at the bottom of this message)
If you use TAS, and your primary domain controller(PDC) is running
Windows 2000, then simply forget about using the Proxy Authentication
method in TAS for user authentication. TAS support says they've been
working with Microsoft and Rational to solve the problem, but nothing's
been finalized yet. TAS support, after several phone calls, finally
came out and said that I'd need to use Local Authentication which means
I need to enter all the users into TAS. There's another
userlist/password list that will need to be maintained - great! TAS
support said there was a hotfix offered by Microsoft for Windows 2000,
but they said it's hard to get and they didn't guarantee it would fix
the problem.
If anybody is using TAS with a PDC running Windows 20000, I'd love to
hear how you've got it setup.
Thanks!
Chris Robinson
Sr. Configuration Engineer
HNC Software Inc.
chr@hnc.com
-------------------------------------
Email to TAS support:
Hi,
I've written in about this several times. I have worked with Abraham @
extension 117 to fix this problem but the problem still exists. He's
always been very courteous and professional, but unfortunately, I still
need help.
Problem:
We are using TAS 5.4.1 patch level 3 on a Solaris 2.6 box and we are
accessing ClearCase repositories setup through TAS volumes. Our clients
are NT4.0/SP6a. Our PDC is Windows 2000 Patch 2. Very frequently we
experienced a permission denied when trying to access a data container
in the ClearCase repository on the Unix server, as if TAS forgets who we
are during the authentication process. Once this happens, the ClearCase
view becomes useless and everytime we click on the file, it says
permission denied. When I examine the file permissions in the VOB data
storage directory, the permissions are read-only for EVERYONE. If I go
through the network neighborhood and open the file directly, I have no
problems. It's only when a ClearCase View on NT tries to open the file,
that it gets a problem. So the problem exists somewhere with the
interaction between ClearCase and TAS.
It seems this problem has been experienced by other users because they
have written about it in the ClearCase User Group(CCIUG).
I have properly installed ClearCase, setup the correct permissions, user
accounts, username maps in TAS. The credentials map correctly from NT
to Unix for all users and clearcase_albd. I have installed all the
patches Abraham told me to install and setup everything the way it's
suppose to be, and it still gives me and all other users the same
problem.
We do not experience these problems when we use Unix clients to access
the Unix VOBs, probably because TAS and the PDC are not used in this
scenario. We also do not experience problems when we you a Unix-hosted
view on an NT client to access the Unix VOBs, because again, I believe
the process for the view runs on the Unix side which means it doesn't
need TAS or the PDC to look into the Unix VOB.
There must be some hidden thing that I/we've missed and I'm hoping to
find out what that is immediately because this is quite disturbing.
Help!
Thanks,
Chris
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:58 EDT