10.3.5 client update breaks network login against 10.2.8 NetInfo server

This topic has 2 replies, 2 voices, and was last updated 19 years, 6 months ago by dragonmac.

Viewing 3 posts - 1 through 3 (of 3 total)

Author

Posts
August 11, 2004 at 6:27 am #358754

dosser
Participant

Currently, I’m 1 for 6 for trouble-free 10.3.5 client installations. This is obviously NOT good.

I have some iMacs/eMacs (including two eMacs which are identical clones) that all have network user logins authenticating over NetInfo against an OS X 10.2.8 server. This has worked very well under 10.3.4 for months now. After running the 10.3.5 combo update on one eMac and seeing no problems, I applied it to 2 other eMacs and 3 older iMacs (all running 10.3.4 and the latest of everthing else). All the other installations broke.

What happens is that the network users show up in the login window fine after a reboot, but sometimes after a minute the login window goes away. It either stays at a blue screen or goes to the console login mode (white text on black, Terminal style). The machines aren’t dead – I can ssh into them just fine using a local user account. Strange things are showing up in the system.log files on them such as:

Aug 10 23:35:35 localhost loginwindow[261]: Login authorization failed (-60008)!
Aug 10 23:35:35 localhost loginwindow[261]: AuthorizationRef doesn’t have a username (<LoginAuthRefMgr: 0x443ed0>).

I tried to research how to fix that but came up empty-handed.

Also, if I do click on a user name in the login window, it will prompt me for a password, which shouldn’t happen on the guest account (no password, plus it is a local (non-network) account). What’s more is that if I click on the "Other…" icon instead of prompting me with user/pass fields, it simply prompts with the password field. I don’t even get a chance to enter a user name. If I hit the escape key or back button on the login window, it returns to the user list but the list has become just one big white box. At this point, rebooting the machine is all I can do (through ssh).

This is happening on 5 different machines that range from a 3 week-old eMac to a 5 year-old iMac. The only machine the update didn’t ruin was another 3 week-old eMac.

I’ve tried disabling/enabling NetInfo binding in DirectoryAccess.app, zapping PRAM, trashing loginwindow.plist files… everything. I’m stuck (aside from cloning the one working eMac and hoping for the best).

Any ideas on things to try? This is the first time a point-point release has caused such a headache for me. 🙁

-Matt

August 12, 2004 at 10:06 pm #358765

dosser
Participant

My findings so far:

http://discussions.info.apple.com/[email protected]@.6898b8ab/1

The short of it: It’s a 10.3.5 client problem, NOT a server issue and it can be remedied by using the “Name and password text fields” display option for the login window in Workgroup Manager.

I’m still not happy with this setup, though, as this isn’t what I had before (and what I had before worked VERY well for my purposes).

-Matt

August 19, 2004 at 1:49 am #358844

dragonmac
Participant

Matt not a 10.3.5 Client problem the Problem is your clients MUST BE 10.3.5 for MCX to work with 10.3.5 Server. Took me many hours to figure out finally did 2 days ago. After my Server Update all my 10.3 clients list view logins broke. The only recipe to get the list view back is on Server MCX prefs for Computer List must be List ALL users (Local, Net, Local Admin, –Other can be on or off) and local users on in Access tab. This will fix the issue if you are waiting to update clients. 10.2 users seemed unaffected.
The reverse might be true here to users of MCX. If you update 10.3 client to 10.3.5 but leave server at 10.3.1-4 you may have problems with login window.
Author

Posts