samba - May 2004 - Samba 3.0 timeout problems within multi-level ADS environments

Hey guys,

I'm trying to use samba 3.0 within an ADS-environment, but run into big
problems. Each time I start winbind, it tries to connect to EACH DC within
the ADS-structure (which contains at least 25 DCs worldwide) and this takes
a VERY long time. It also occurs that one of these is currently not
available (VPN-breakdown/policy settings) and at this point the whole system
is running in big timeouts, e.g. some users are unkown, file-name completion
within the bash is not working anymore, ...

Is there any way to advise winbind to use only ONE DC as proxy and not
trying to connect to each DC separately? Or solve this issue in any more
convenient way?

Right now I using a local script which parses the debugging locks and adds
automatically local REJECT rules to the firewall kernel.. But this seems a
very crazy solution <g>

Sincerely

	.\\ichael

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Michael Schoen wrote:
| Hey guys,
|
| I'm trying to use samba 3.0 within an ADS-environment,
| but run into big problems. Each time I start winbind,
| it tries to connect to EACH DC within the ADS-structure
| (which contains at least 25 DCs worldwide) and this takes
| a VERY long time.

Should be improved in 3.0.4.  Please let us know if 3.0.4
behavior better in your environment.





cheers, jerry
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFAphCdIR7qMdg1EfYRAui/AJ4jIIHpJyMYQZTSGg3XlizdosKUjACgyKbd
L5i34Aj5YdUbFqjMVgum/yE=SxxE
-----END PGP SIGNATURE-----