MAC's dropping off domain everyday

[ljones]

Hi this week we have had several problems with the same two macs, everyday the user is coming to the mac to log in and it wont allow network users. Once i remove and re-bind it to the domain it then works. Is there a simple fix for why this would be happening every day?

 

Thanks

[seawolf]

Are you on a .local domain? This can be a factor in issues like this.

 

If it's only two out of many that are doing this and the network point tests fine, you might want to re-image one of them and see if the same thing continues to occur.

[furby]

Could you be a bit more specific when you say "won't allow"?

 

Taking a guess though, do you get the below at the login screen?

[sted]

make it get its time sync from your pdc. I found even a small time discrepancy could really foul up macs with ad

[seawolf]

make it get its time sync from your pdc. I found even a small time discrepancy could really foul up macs with ad

 

Yep, that will certainly do it.

[ljones]

yes this is the screen that is shown, i have changed the time server to our local network also. Edited March 21, 2014 by ljones

[furby]

And the red light never goes away?

 

Before we get into something more complicated I'm thinking this is simply the mac going to sleep. When it goes to sleep and is woken it takes 30s or so before you can log onto a network account

[ljones]

it stays there preventing network users from logging in until i sign in with a local administrator account unbind from AD and then bind back to AD, then when i log out the red light is gone.

[Gloxxy]

What version of OS X are you running?

 

Does this happen after the Mac has been sleeping? I had this problem with a few Macs in our school. The NIC doesn't work properly after the Mac has been woken.

 

I had to enable "Prevent computer from sleeping automatically when the display is off" to stop it from doing this.

 

http://i61.tinypic.com/2kn486.png

[ljones]

it seems to be at the end of the day when the users shutdown their machine and when they come back in the morning it says network accounts unavailable. Were on 10.8 also.

[Gloxxy]

So a simple reboot didn't sort this problem out? It has for me in the past.

 

It makes it extra difficult to troubleshoot once you are running 10.9 on the Macs as the red dot has been taken out completely.

[ljones]

no it doesnt work until i do the unbind and bind back to AD

[furby]

Just to be absolutely sure, how long are you/they waiting? It's the same with all our macs for a period of time when they're switched on/rebooted

[ljones]

a decent amount of time because the job has to go onto our job log and wait for us to get over to the mac

[Brimstone]

a decent amount of time because the job has to go onto our job log and wait for us to get over to the mac

 

Are you using .local for your domain....this will cause intermittent problems such as the ones you have posted

[round2it]

Dns issue.

 

I had same problem.

 

It was our dns server that was messed up.

 

I set up dns on a vm and pointed the macs to use the new server for dns and the macs now work fine

[twin--turbo]

We put our macs on static IP's reserved in DHCP. That fixed a fair few odd occurances.

 

It means they always have the right DNS entry, they don't seem to update that correctly if on dynamic DHCP.

 

Rob

Edited March 22, 2014 by twin--turbo

[seawolf]

Sounds like some of you are describing the sorts of issues you will get if you use Macs on a .local domain...

[ste1988]

We put our macs on static IP's reserved in DHCP. That fixed a fair few odd occurances.

 

It means they always have the right DNS entry, they don't seem to update that correctly if on dynamic DHCP.

 

Rob

 

We have also had that issue!

@seawolf beat me too it, definitely a .local type issue

 

- - - Updated - - -

 

We put our macs on static IP's reserved in DHCP. That fixed a fair few odd occurances.

 

It means they always have the right DNS entry, they don't seem to update that correctly if on dynamic DHCP.

 

Rob

 

We have also had that issue!

 

@seawolf beat me too it, definitely a .local type issue

[tobiasclarity]

Have you got them attached to a mac server aswell? or are they just simple connecting to AD?

[round2it]

Mac server so we can lock down apps etc.

 

.local network

 

Setup reservations for the macs in dhcp (helps)

 

Working ok so i dont touch them much

 

Aint broke dont fix it

[ljones]

our network team seems to have resolved the issue where there was a conflict on the domain with the two macs had the same name - this was changed and problems hasnt reoccured.