Trusted domains

[To-M]

Try export UIDs and GIDs then change authentication method to Internal LDAP reconnect to ADS import UIDS and GIDs after modifying the exported csv files.

Test with users in Domain Groups not Local Groups as this will not be imported correctly for Local Groups. Also we do not have support for multiple Domains only in DSS version in new release 1.30 due in August of this year.

Also this issue could be related to trusted domains. Please try to synchronize clocks on all. The best if use NTP server for this. Then try again. If it fails, please try to disable trusted for tests.

Did you send this to support back in 6-13-07 and did you get back with them on your results?

[Koen]

Thank you for the reply. I did indeed had contact with support about a major problem with the AD-synchronisation, but this appears not to be the same as this one.
This is a production server so it is not so easy to play around with the settings. We will try this when the next scheduled update of our server is planned. However, when we had the problems with the AD-synch I have applied this many times, and I have never seen any change with respect to the trusted domains behaviour: the users and groups get imported all right, but the group memberships are not. The groups I talk about are all global groups. And all our servers clocks are already synchronised using an NTP server. It looks like a fundamental problem to me. But apparently I am the only one it probably is more related to our domain trust settings. Are there any guidlines available about these trust relationships with respect to SAMBA?

All the best,

Koen

Try export UIDs and GIDs then change authentication method to Internal LDAP reconnect to ADS import UIDS and GIDs after modifying the exported csv files.

Test with users in Domain Groups not Local Groups as this will not be imported correctly for Local Groups. Also we do not have support for multiple Domains only in DSS version in new release 1.30 due in August of this year.

Also this issue could be related to trusted domains. Please try to synchronize clocks on all. The best if use NTP server for this. Then try again. If it fails, please try to disable trusted for tests.

Did you send this to support back in 6-13-07 and did you get back with them on your results?

[To-M]

Usually this is strait forward, have you tried to use Synchronize UID and GID database with NIS server in Setup > Server to test? In the manual is a description of what this option does, the only problem it is a security risk.

I had a case where the customer made these adjustments on their server to the members PasswordProp to allow groups and users to be synchronized. Not sure if this will help but give it a try.

[Koen]

We do not have a NIS server in our network (Windows only). I'll have to investigate this further, as we have no experience in this field. I'll let you know the results.

All the best,

Koen

Usually this is strait forward, have you tried to use Synchronize UID and GID database with NIS server in Setup > Server to test? In the manual is a description of what this option does, the only problem it is a security risk.

I had a case where the customer made these adjustments on their server to the members PasswordProp to allow groups and users to be synchronized. Not sure if this will help but give it a try.