Dan,
Yes, of course, overall TAS is still needed to make your vobstore and
viewstore directories visible on the NT side.
I appreciate you taking the time to read my message, and corrections and
clarifications are always appreciated, but in this case, I'd have to
stick with what I said. Please that part of my message again. What I
was referring to in my message which you quoted was, specifically, the
view process on the Unix side. I was not talking about the MVFS running
on the NT side. I still think if a view process is running on the Unix
side(viewstorage on Unix), then that VIEW PROCESS does not need TAS to
look into viewstore directories and vobstore directories stored also on
the Unix side. Yes, the MVFS and the overall process on NT of course
requires TAS, but, specifically, a view process on the Unix side does
not, in my opinion. This is my only explanation as to why we weren't
experiencing any authentication problems using unix-hosted views on
running on NT clients where as we had frequent problems with local NT
views.
As always, if someone can clarify this, please let us know. It makes us
all smarter.
Thanks,
Chris
-----Original Message-----
From: Dan Rickhoff [mailto:dan.rickhoff@home.com
Sent: Monday, July 23, 2001 8:48 AM
To: Robinson, Christopher; cciug@rational.com
Subject: Re: [cciug] TAS, Windows 2000 PDC, Proxy Authentication in TAS
Chris,
Regarding one very-specific thing you mentioned:
"We also do not experience problems when we use 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."
My understanding of this is:
When using a dynamic view while working on an NT CC client, he mvfs file
system on that NT CC client needs to access VOB storage as though the
VOB
storage is on an NT filesystem. TAS or Samba is used to "share" the
UNIX-resident VOB storage as if it was an NT filesystem, so the NT CC
client's mvfs filesystem can access it. My point being: I disagree with
your statement (above); TAS *is* required.
BTW - As far as where the view is hosted: When using a dynamic view
while
working on an NT CC client, he mvfs file system on that NT CC client
needs
to access the view storage as though the view storage is on an NT
filesystem. If the view is hosted on UNIX, then TAS or Samba is used to
"share" the UNIX-resident view storage as if it was an NT filesystem, so
the
NT CC client's mvfs filesystem can access it.
Another BTW - CCIUGers, please correct me if I'm wrong. Other than the
VOB
storage and view storage file system accesses I've described above,
i.e.,
NT CC client mvfs <--> VOB storage on a NT or UNIX machine
NT CC client mvfs <--> view storage on a NT or UNIX machine
There is no CC-required "sharing", via TAS, Samba, or NFS, of VOB
storage or
view storage that needs to be established. For example, if VOB storage
is
on machine "A", and a view's storage is on machine "B", then for CC
client
machine "C" to use those VOBs and that view, there is no need to "share"
(via TAS, Samba, or NFS) A's VOB storage to B, or B's view storage to A.
Dan
> From: "Robinson, Christopher" <chr@hnc.com>
> Date: Mon, 23 Jul 2001 06:38:02 -0700
> To: "Evgeny Dreyman" <evgeny_dreyman@atrica.com>
> Cc: <cciug@rational.com>
> Subject: RE: [cciug] TAS, Windows 2000 PDC, Proxy Authentication in
TAS
>
>
> The folks at TAS and Microsoft are currently working on correcting the
> problem. Microsoft has a hotfix and TAS has some instructions for
> changing the registry on your PDC that they "believe" will work. I'm
> going to wait until I get an email from TAS support saying: "Try this,
> it will absolutely fix the problem." Going to our admin and telling
him
> to muck around with the registry and reboot our PDC for our entire
> company is something I'd rather not do since I don't know if it'll
even
> work.
>
> Until a fix is totally verified, I changed TAS to use "Local
> Authentication" instead of "Proxy Authenticaion". Yes, I did have to
> enter all of our users into TAS's system, and yes, all users then had
to
> go into TNAS and set their password to their current NT domain
password.
> This is quite a bit of work, but it did fix the problem and I'm just
> happy about that. Honestly, I've thought about Samba many times
during
> this whole mess, but I'd rather try to fix this problem then trying to
> uninstall TAS and install Samba. Besides, since the problem comes
from
> Microsoft Win2K running on our PDC, I wasn't sure if we wouldn't see
the
> same problem in Samba.
>
> TAS seems to be working fine now under "Local Authentication", and
when
> they get a solid fix for "Proxy Authentication", we'll switch back to
> it.
>
> -----Original Message-----
> From: Evgeny Dreyman [mailto:evgeny_dreyman@atrica.com
> Sent: Sunday, July 22, 2001 11:36 PM
> To: Robinson, Christopher
> Subject: RE: [cciug] TAS, Windows 2000 PDC, Proxy Authentication in
TAS
>
>
>
> Hi !
> Thanks for your mail, it explained most of our problems with UNIX/NT
> interoperation.
> Do you think about SAMBA installation, instead of TAS ?
>
> Regards
> Evgeny
>
> Phone : (+972)-9-9707434
> E-mail : evgeny_dreyman@atrica.com
>
>
> -----Original Message-----
> From: Robinson, Christopher [ mailto:chr@hnc.com <mailto:chr@hnc.com>
]
> Sent: Thursday, July 19, 2001 6:25 PM
> To: cciug@rational.com
> Subject: [cciug] TAS, Windows 2000 PDC, Proxy Authentication in TAS
>
>
>
> 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
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> can also
unsubscribe
>
> http://clearcase.rational.com/cciug/mailing_list.html
> <http://clearcase.rational.com/cciug/mailing_list.html> ]
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
> can also
unsubscribe
>
> http://clearcase.rational.com/cciug/mailing_list.html
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
This archive was generated by hypermail 2b29 : Tue Jul 31 2001 - 22:03:59 EDT