We have verified it is NOT time sync which is the issue, the time is completely identical on both clientr machine and DC. Often this will cause AD domain requests to time out. Macs will always try mDNS first when they see. Sudo defaults write /System/Library/SystemConfiguration/IPMonitor.bundle/Contents/Info mdns_timeout -int 1 This changes the Multicast DNS (aka mDNS, Bonjour, RFC 6762) to 1 ms instead of the default of 5. Lastly, since you are dealing with a domain ending in. This makes me suspect some kind of timing issue, so we are in the process of testing below config (copied from a different post): network users not available, it is simply just the login-screen that is missing the 'other' account. Worth noting, we never get an error here i.e. But after we restart, then the 'other' account disappears completely. However, if we wait a 20-30 seconds after logging out with the local account, then the 'other' (AD) account will disappear on sometimes reappear. After I log out the first time (with local user), then the 'other' user is available and and we can log in using our AD credentials.ĭC is on domain.local, and the bind works flawlessly every time. I have tested the binding to AD with two mac 10.14.
0 Comments
Leave a Reply. |