does Authentication have a time limit?

Discussion in 'Active Directory' started by Bryan, Jun 9, 2004.

  1. Bryan

    Bryan Guest

    We have a relatively new Windows 2003 server running here - the only server
    on
    our small lan with 3 or 4 pc's in addition to the server.

    We all can log on, and see and copy files between our PC's, but have to
    reboot
    each morning or we get "The system detected a possible attempt to
    compromise security. Please ensure that you can contact the server that
    authenticated you."

    We swapped from dynamically assigned IP's to static IP's in hopes that that
    would help,
    but it doesn't.

    Any ideas? Our clients are Windows XP Pro, btw.

    Thanks!

    Bryan
     
    Bryan, Jun 9, 2004
    #1
    1. Advertisements

  2. Do you stop any services on a night for a backup or anything like that?
     
    MadCrazyNewbie, Jun 10, 2004
    #2
    1. Advertisements

  3. Bryan

    ptwilliams Guest

    This is a DNS problem

    Ensure your server has a static IP address and that it is registered in DNS! Point the DC to itself, or the internal DNS server, for DNS and run the following from the command prompt to do this

    C:\>ipconfig /flushdn
    C:\>net stop netlogo
    C:\>net start netlogo
    C:\>ipconfig /registerdn

    And ensure that all of your internal clients are pointing to the internal DNS server

    Paul
    ___________________________
    ----- Bryan wrote: ----

    We have a relatively new Windows 2003 server running here - the only serve
    o
    our small lan with 3 or 4 pc's in addition to the server

    We all can log on, and see and copy files between our PC's, but have t
    reboo
    each morning or we get "The system detected a possible attempt t
    compromise security. Please ensure that you can contact the server tha
    authenticated you.

    We swapped from dynamically assigned IP's to static IP's in hopes that tha
    would help
    but it doesn't

    Any ideas? Our clients are Windows XP Pro, btw

    Thanks

    Brya
     
    ptwilliams, Jun 10, 2004
    #3
  4. Bryan

    Bryan Guest

    Thank you, Paul - I've just completed those steps but I want to make sure I
    am doing this correctly.

    I changed the primary DNS server in my IP Connections to point to itself.
    In other
    words, our one-and-only server has an internal IP of 192.168.1.100, so I
    made the primary
    DNS that value in the network connections.

    Then I ran the series of instructions you gave below.

    Now I need to have my clients use 192.168.1.100 as the primary DNS?

    Thanks again for the help!

    Bryan

    DNS! Point the DC to itself, or the internal DNS server, for DNS and run
    the following from the command prompt to do this:
     
    Bryan, Jun 10, 2004
    #4
  5. Bryan

    ptwilliams Guest

    Yes, all internal clients should point to the internal DNS server.

    It is very important that all point to the internal server. It is also
    recommended that you enable Dynamic updates on the DNS server.

    External name resolution will happen, depending on your setup, but by
    default in a recursive manner via the root hints on the DNS server. Another
    option is to enable a forwarder.

    Post back if you need more info.


    Paul.
    ____________________________
     
    ptwilliams, Jun 10, 2004
    #5
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.