On Fri, Nov 02, 2001 at 12:22:13AM -0000, Darrell May <[EMAIL PROTECTED]> wrote: > [...] > All I'm pointing out is that an active netlogon, printer, or profile > share has been thoroughly tested and up until this recent decision to > change it, I thought it worked just fine.
It's not a recent decision to change it - [netlogon] has been thus protected for quite some time - ever since we changed it to be so after reports of the share taking over when existing NT servers also provided the same resource. > If the only negative is the one you mentioned above, then I've provided > the answer. Fix the client, don't disable the feature at the e-smith > server :) Many thanks for the explanation (maybe my feeble flu-addled brain just didn't get it before). It sounds like a HOWTO for client setup may solve the problem and make it reasonable to remove the guards. Do I have this right: - If you don't set %LOGONSERVER% you will access the first available logon/profile server in your workgroup/domain, but setting it resolves the race condition by tieing you to a particular server. Gordon -- Gordon Rowell [EMAIL PROTECTED] VP Engineering Network Server Solutions Group http://www.e-smith.com Mitel Networks Corporation http://www.mitel.com -- Please report bugs to [EMAIL PROTECTED] Please mail [EMAIL PROTECTED] (only) to discuss security issues Support for registered customers and partners to [EMAIL PROTECTED] To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Archives by mail and http://www.mail-archive.com/devinfo%40lists.e-smith.org
