ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Login Error (there is a time and or date difference between the client)

    IT Discussion
    3
    8
    962
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • S
      shybrsky
      last edited by

      this morning ..some of user tried to login on their computer with domain user and got this message ..

      anyone know this issue ?? or how to solve this ..

      Regards
      Shyb

      1 Reply Last reply Reply Quote 0
      • scottalanmillerS
        scottalanmiller
        last edited by

        Did you check the time on the server and on the clients? It has to be very close, like within five minutes or Kerberos (AD) will fail.

        S 1 Reply Last reply Reply Quote 0
        • S
          shybrsky @scottalanmiller
          last edited by

          @scottalanmiller i did ... make changes .. and same problem ... tolerance only 5 minutes right ??

          scottalanmillerS 1 Reply Last reply Reply Quote 0
          • scottalanmillerS
            scottalanmiller @shybrsky
            last edited by

            @shybrsky said:

            @scottalanmiller i did ... make changes .. and same problem ... tolerance only 5 minutes right ??

            At most. You want it within a few seconds, though. If it is more than say fifteen seconds off, something is wrong.

            1 Reply Last reply Reply Quote 0
            • nadnerBN
              nadnerB
              last edited by nadnerB

              Well, just to make sure it's not the time, you can try this so long as you can actually log into the machine... a local account will do fine.
               
              From an elevated command prompt:

              net time /domain:<insert domain here> /set /y
              
              1 Reply Last reply Reply Quote 0
              • nadnerBN
                nadnerB
                last edited by nadnerB

                Also, have a go at these things here before going on with the steps below :

                Personally, I haven't ever had any of them work (even though I try them first) so I always have to fall back to:

                1. disconnect PC from domain (reboot etc)
                2. remove entry from AD
                3. Connect PC to domain
                4. move to correct OU
                5. gpupdate /force
                  
                1 Reply Last reply Reply Quote 0
                • S
                  shybrsky
                  last edited by

                  thankx any feeedback ... solved

                  1 Reply Last reply Reply Quote 0
                  • scottalanmillerS
                    scottalanmiller
                    last edited by

                    Great! Another case closed by the late night ML team.

                    1 Reply Last reply Reply Quote 0
                    • 1 / 1
                    • First post
                      Last post