agarabaghi Posted June 17, 2013 Posted June 17, 2013 We have a pretty big mac pro lab. 24 machines + 1 instructor machine... All of them have the same image deployed by mac server and then each machine is manually binded to AD. When the machines turn on, it takes abour 1 - 1:30min for the red dot to go away. If it goes away everything is working. The problem is after several reboots the red dot remains. The only solution is to unbind and rebind the machines. It pretty inconsistent but they will all eventually red dot at some point of another. Im lost as to an approach, as I am not the AD admin or even sure where the issue is coming from ...
marekbrad Posted June 17, 2013 Posted June 17, 2013 usual suspects in no particular order... DNS .. can the macs do both forward and reverse dns lookups to your AD and time .. do your macs use the same time server as you DC .. or even point to DC for time, does DHCP push out search domain? You may need to talk to your AD admin
Ephelyon Posted June 17, 2013 Posted June 17, 2013 This is something I posted years ago to fix a similar issue that might help: http://www.edugeek.net/forums/mac/43879-snow-leopard-ad-integration-woes.html#post549033
agarabaghi Posted June 17, 2013 Author Posted June 17, 2013 usual suspects in no particular order... DNS .. can the macs do both forward and reverse dns lookups to your AD and time .. do your macs use the same time server as you DC .. or even point to DC for time, does DHCP push out search domain? You may need to talk to your AD admin Well we tried a different method of binding the machines and as of right now it only takes 5-10sec for the red dot to go away...so something is def different... Will keep updating
seawolf Posted June 17, 2013 Posted June 17, 2013 We have a pretty big mac pro lab. 24 machines + 1 instructor machine... All of them have the same image deployed by mac server and then each machine is manually binded to AD. When the machines turn on, it takes abour 1 - 1:30min for the red dot to go away. If it goes away everything is working. The problem is after several reboots the red dot remains. The only solution is to unbind and rebind the machines. It pretty inconsistent but they will all eventually red dot at some point of another. Im lost as to an approach, as I am not the AD admin or even sure where the issue is coming from ... Does your AD domain end with .local? If so, there is the sum of your problems. Renaming the domain is the only fix. If you DON'T have a .local domain then double check your DNS is correct. 10.6 also was much worse about this than 10.7 or 10.8 - if you haven't upgraded yet you need to be thinking about it very soon as it will likely help overall performance.
psydii Posted June 18, 2013 Posted June 18, 2013 (edited) First thing I would check is the time, and the mac clocks in sync with the DC clocks? (See other recent mac thread) Edited June 18, 2013 by psydii
agarabaghi Posted June 18, 2013 Author Posted June 18, 2013 Update 24 hours in... Red Dots appear for only 5-10 seconds on shutdown / power up and reboots (which is different from the previous 1min time it took). No red dots have remained, yet. Changes made: 1) Enabled Port Fast on Olin switch 2) Enabled IPv6 on network card settings on server 3) Re-binded all machines to AD using the Advanced bind settings from Directory Utility. Keep our fingers crossed.
mgs Posted February 22, 2018 Posted February 22, 2018 Hi All, I know this is an old thread, but we are having the red dot issue with most of our Macs on AD. They are OS 10.11 and had been joined to AD (.edu domain) for a while but we were using local logins until recently. Within a few days of having students login with their AD credentials we started getting the red dots here and there and now mostly everywhere. So, since I don't see recent posts about this, is there an accepted solution to this issue that we're missing? We've tried all the basic things and are getting ready to try extending the mdns timeout, then the script after that.
Boon72 Posted February 22, 2018 Posted February 22, 2018 it's been a while but i'd start with the time check
agarabaghi Posted February 22, 2018 Author Posted February 22, 2018 Hi All, I know this is an old thread, but we are having the red dot issue with most of our Macs on AD. They are OS 10.11 and had been joined to AD (.edu domain) for a while but we were using local logins until recently. Within a few days of having students login with their AD credentials we started getting the red dots here and there and now mostly everywhere. So, since I don't see recent posts about this, is there an accepted solution to this issue that we're missing? We've tried all the basic things and are getting ready to try extending the mdns timeout, then the script after that. sudo dsconfigad -show check what the passinterval is set to, if anything but 0 sudo dsconfigad -passinterval 0
mgs Posted March 5, 2018 Posted March 5, 2018 Thanks for the suggestions. Things that have worked. Unbind and Rebind works 100% of the time …Will last unknown amount of time. Things that looked promising at one time Change order of DNS severs listed under the network tab. Worked on one computer but never again Change the sync time to the domain controller worked once then never again Things never worked Hostname=computer name= network name Change sync time to DNS server Wake on LAN settings and make sure they are enabled
XiJ Posted March 5, 2018 Posted March 5, 2018 Issues we’ve had with AD bound macs recently have related to FileVault. If it’s on you need to enable for all users.
Zoatibix Posted May 1, 2018 Posted May 1, 2018 We had a similar issue at our place. To be frank I think there's a problem with our network setup but I've never managed to get a decent answer as to what that might be. However, after several months of trial and error I got a dim understanding of the problem from the Mac's point of view and managed to come up with a fix. I orginally thought that time was the big issue, so set the time to update from time.ourdomain.ac.uk. That improved things a bit. Unfortunately, Macs were still randomly losing the ability to see the domain. If I logged in locally I could see they were getting an IP address but the domain name was now displaying as 'MYDOMAIN' rather than 'mydomain.ac.uk'. I believe this is a symptom rather than a cause. I stopped using the Directory Utility, or entering the FQDN when trying to bind the Macs. Instead I used the IP address of the nearest DC, or the PDC in the 'Server' box under Users & Groups. This made a significant improvement but I honestly don't know why. I suspect a DNS/DHCP issue but an outside consultant that looked into the problem couldn't pinpoint any causes. Still, things got a lot better but machines still went AWOL with annoying regularity. Blind luck one day I stumbled upon Keychain access > preferences > and ticked "Search Directory services for certificates." That seemed to be the clincher. When I used all three of those steps the problem pretty much went away. The macs don't 'fall off' the domain anymore frequently than the Windows machines we have.
2097 Posted May 8, 2018 Posted May 8, 2018 Update 24 hours in... Red Dots appear for only 5-10 seconds on shutdown / power up and reboots (which is different from the previous 1min time it took). No red dots have remained, yet. Changes made: 1) Enabled Port Fast on Olin switch 2) Enabled IPv6 on network card settings on server 3) Re-binded all machines to AD using the Advanced bind settings from Directory Utility. Keep our fingers crossed. Do the macs have IPV6 enabled ? are you using it ? I would disable IPv6 on the client's nic and server, i would also disable the WIFI card if you are using Ethernet .
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now