Announcement

Collapse
No announcement yet.

Anyone remember NTconnect?

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • kstanush
    replied
    Re: Anyone remember NTconnect?

    Thanks for letting us know. Its been about 3 years since I worked with NTconnect, and remember adding this feature, as it was considered a bug to not check nested group memberships. Imagine nesting groups in Windows 2000 and trying to resolve that !.

    Leave a comment:


  • jberner
    replied
    Re: Anyone remember NTconnect?

    Sorry for the delay.
    We found the reason for this strange behaviour.
    If you create a local group that contains global groups as members someone (the OS or NTconnect) looks "into" the local groups and the portions of the login script that apply to the global groups are executed.
    Quite easy but it took two people two days to sort it out
    But thanks for the help.

    Leave a comment:


  • kstanush
    replied
    Re: Anyone remember NTconnect?

    Please email the relevant section of your script to [email protected]. Also, indicate the name(s) of the groups involved. I'll try to reproduce.

    Thanks

    Leave a comment:


  • jberner
    replied
    Re: Anyone remember NTconnect?

    Why does NTconnect try to assign the drives of the second group (B), when the user is only a member of group A? It shouldn't do this because the starting line of the section clearly says [Group:A].

    Leave a comment:


  • kstanush
    replied
    Re: Anyone remember NTconnect?

    Is the problem the error messages, or what is the problem ?

    Leave a comment:


  • jberner
    started a topic Anyone remember NTconnect?

    Anyone remember NTconnect?

    We're using the tool NTconnect during our login process and encounter a very strange phenomenon.
    It goes like this: a user X is only a member of a global group A. In the login script is a section where group A is assigned some network drives. There is also a section that assigns a group B network drives. Now for the phenomenon: when X logs on NTconnect tries to assign the drives for both groups A and B and gives error messages that the ressources are already in use (which is okay). I've tried everything but to no avail and now I'm at my wits end.
    Any suggestion is greatly welcome.

    Bye

    Jochen Berner
Working...
X