- This topic is empty.
-
Posts
-
I got my mac working good with active directory, except for one small thing. Users can’t login AT the Mac. If someone tries to log in it just exits to console and the gets stuck on a blue screen (unless fast user switching is enabled, at which point it goes back to the login window).
The error I get in the system log is
Mar 19 14:00:31 localhost loginwindow[4886]: getpwnam() lookup of test1 failed Mar 19 14:00:31 localhost loginwindow[4886]: exiting to console Mar 19 14:00:32 localhost loginwindow[4897]: DSGetParentsConfigInfo(): DSGetRecordList() == -14130
The thing that is frustrating is that I had it working on 1 account. I just don’t remember what I changed, or if I even changed anything, to get it to work.
However SSH works great, it even points me correctly to the shared home directory.
ssh test1@localhost test1@localhost's password: Welcome to Darwin! pesc-mac:~ test1$ pwd /Network/Servers/pesc-server2/homes/test98/
I think it has something to do with my uid. It isn’t matching what is being created when I touch something.
pesc-mac:~ test1$ touch test pesc-mac:~ test1$ ls -lh test -rwxr-xr-x 1 1757211261 staff 0B 19 Mar 14:18 test pesc-mac:~ test1$ id uid=4294967294(test1) gid=20(staff) groups=20(staff)
I think I had the same problem (although the uids of created files matched the output of id, but I think you should have been using ls -ln to check that).
Anyway, my account had exactly the same uid as yours, which made me twig to the fact that it’s actually the uid of user nobody. Ie for some reason OS X is not retrieving your uid correctly even though it is authenticating ok, and so it’s defaulting to uid nobody.
I found a fix by trial and error mostly. In the Advanced config options for AD in Directory Access, I had Map UID to attribute set to UniqueID and enabled (as per my organisations’s AD/OS X howto). I disabled this seting and suddenly the problem went away. This may not work for anyone else but at least the uid nobody thing should give you an idea as to what’s going wrong …
- You must be logged in to reply to this topic.