rickjames Posted September 18, 2015 Posted September 18, 2015 (edited) Afternoon, Our sole iMac (10.10.5) in the school is playing up all of a sudden. It's binded to AD and connected to our WiFi absolutely fine (full strength), but it's giving me the 'Network accounts are unavailable' popup when booting up. I've unbinded and rebinded it to AD again to no avail. For the record I've also done the same with an ethernet cable to no avail. Any idea?! Stumped... Edited September 18, 2015 by rickjames
3s-gtech Posted September 18, 2015 Posted September 18, 2015 Can network accounts actually log on though? Ours have always done this, since back on 10.5, it's just a quirk and it goes away very quickly.
Sagima Posted September 18, 2015 Posted September 18, 2015 I'll make a stab at time. It was always that when they didn't work for me. Point it at your DC (or whatever you use) 1
round2it Posted September 18, 2015 Posted September 18, 2015 Check the dns settings also if they use dhcp try reserving the ip address in dhcp. This fixed our issues.
andyturpie Posted September 21, 2015 Posted September 21, 2015 I'll make a stab at time. It was always that when they didn't work for me. Point it at your DC (or whatever you use) I would say this is more likely. Our iMacs were off over the summer as the room was getting refurbished. Some of the machines times were completely out of line with the rest of the network. Logged in with local admin user, adjusted date and time and restarted. All was well again.
mmi Posted November 19, 2015 Posted November 19, 2015 Also check that it is getting the correct IP in the correct VLAN (if applicable).
slancaster Posted November 19, 2015 Posted November 19, 2015 ensure your clients are time synced with your DC
ehg Posted November 23, 2015 Posted November 23, 2015 Check your search domain in DNS, you need to put your xxxx.local in there if your domain is .local rather than anything else. We also found that setting the speed of the NIC helped out as well
rwickberg Posted March 4, 2016 Posted March 4, 2016 Our wireless uses 802.1x authentication against Microsoft's RADIUS implementation in NPS. Macs don't connect to the network until someone's logged into them, so I got this error message until I plugged in. Does mean you can't really use domain accounts on a Mac laptop, though, unless we set up an SSID that uses a static key, which I don't really want to do, or someone can tell me how to make the mac use the AD computer account info when no one's logged into it.
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