+ Post New Thread
Results 1 to 7 of 7
Mac Thread, Macs fail to network login on first attempt in Technical; Hello, Have a classroom of 30 imacs running a mix of snowleopard and lion. we have a macserver which copies ...
  1. #1

    Join Date
    Nov 2013
    Posts
    6
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0

    Macs fail to network login on first attempt

    Hello,

    Have a classroom of 30 imacs running a mix of snowleopard and lion. we have a macserver which copies user info from our windows active directory as we are a predominetly a windows school. however a major issue we have is that we fail to login straight away. the screen will shake indicating wrong login information however this is not the case. most time it will take 5-10 attempts before we can login properly.

    any ideas on what could be causing the issue? and a fix for it.

    happy to explain more.

  2. #2

    Join Date
    May 2014
    Location
    San Ramon
    Posts
    5
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    Why not pair the Active Directory (Windows) with Open Directory (Mac) on the server end, and then use that? Thats what we do.

  3. #3


    Join Date
    Mar 2009
    Location
    Leeds
    Posts
    6,591
    Thank Post
    228
    Thanked 856 Times in 735 Posts
    Rep Power
    296
    make sure that all the macs use a windows dc as their time server as they seem to be very fussy about time when connected to ad

  4. #4

    Join Date
    Mar 2010
    Location
    Leeds
    Posts
    418
    Thank Post
    77
    Thanked 46 Times in 41 Posts
    Rep Power
    18
    Quote Originally Posted by sted View Post
    make sure that all the macs use a windows dc as their time server as they seem to be very fussy about time when connected to ad
    I would second what @sted said. Had the same problem recently. make sure the windows server, the mac server and the clients are all pointing to the same time server. If it is out by just a couple of minutes it can cause headaches.
    Last edited by jonnykewell1; 27th May 2014 at 10:58 AM.

  5. #5

    Join Date
    Nov 2013
    Posts
    6
    Thank Post
    0
    Thanked 0 Times in 0 Posts
    Rep Power
    0
    i double checked times on all servers and clients and all are synched to the same second and to the same server.

  6. #6

    seawolf's Avatar
    Join Date
    Jan 2010
    Posts
    969
    Thank Post
    12
    Thanked 283 Times in 217 Posts
    Blog Entries
    1
    Rep Power
    175
    I suspect the user is not waiting for the red dot (indicating connection to AD server) to go away before trying to login. If you are on a .local domain it can take a couple of minutes for the Mac to be "ready" for login when coming out of sleep mode or a reboot. On a non .local Domain this only takes a few seconds.

    Otherwise, it may be that the user actually ISN'T typing the right login details the first 5 times (spaces in usernames are common cause); or, their network home location may be specified wrong in the AD profile.

    If it's neither of those things, then you have a truly unique problem I've not seen before. Might be best to open console immediately after a sequence of failed login attempts where the user finally gets on. Search for the username in console and you should see logging associated with the failed attempts and it should indicate the reason.

  7. #7

    Join Date
    Oct 2012
    Posts
    68
    Thank Post
    17
    Thanked 6 Times in 5 Posts
    Rep Power
    10
    Quote Originally Posted by seawolf View Post
    I suspect the user is not waiting for the red dot (indicating connection to AD server) to go away before trying to login. If you are on a .local domain it can take a couple of minutes for the Mac to be "ready" for login when coming out of sleep mode or a reboot. On a non .local Domain this only takes a few seconds.

    Otherwise, it may be that the user actually ISN'T typing the right login details the first 5 times (spaces in usernames are common cause); or, their network home location may be specified wrong in the AD profile.

    If it's neither of those things, then you have a truly unique problem I've not seen before. Might be best to open console immediately after a sequence of failed login attempts where the user finally gets on. Search for the username in console and you should see logging associated with the failed attempts and it should indicate the reason.
    X2 We have that same issue on our network due to a .local domain and we are not yet at a point where we can rebuild.

SHARE:
+ Post New Thread

Similar Threads

  1. Replies: 1
    Last Post: 14th November 2013, 02:23 PM
  2. Failed to re galley on Smart 10
    By Sandbox in forum Educational Software
    Replies: 1
    Last Post: 10th July 2010, 05:47 PM
  3. Login script - first attempt
    By itman in forum Windows
    Replies: 11
    Last Post: 24th October 2008, 04:08 PM
  4. Java Script fails to work on one user profile!
    By pmassingham in forum Windows
    Replies: 0
    Last Post: 29th June 2006, 07:32 AM
  5. Replies: 13
    Last Post: 7th November 2005, 10:05 AM

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •