Re: Too long time durring Logon!!!!?Too Urgent!!!!

From: Miha Pihler (mihap-news_at_atlantis.si)
Date: 09/11/04

  • Next message: Die: "Re: spamming solution for small networks"
    Date: Sat, 11 Sep 2004 09:23:00 +0200
    
    

    Hi,

    There are few things you need to check:
    * First check DNS settings on the clients. Clients DNS needs to be
    configured to point to Active Directory DNS (probably your active directory
    server). If client's DNS point somewhere else this they won't be able to
    find your domain controllers and clients won't be able to logon. If you are
    in process or replacing active directory server, make sure that client's
    will know where to look for DNS on new server (make sure that they have DNS
    pointing to new AD server).
    * On AD server itself, make sure that DNS setting under TCP/IP points to
    itself or another active directory DNS server
    * Make sure your new AD server is also a global catalog (GC)
    * Make sure your new AD server is also a DNS server (e.g. configure your DNS
    zone to be Active Directory Integrated. This way DNS will replicate between
    domain controllers).

    Mike

    "Mahnaz" <Mahnaz@discussions.microsoft.com> wrote in message
    news:8AB49E08-F2A7-481F-ADA4-34E21CC21467@microsoft.com...
    > Hi,
    > It takes too long durring "Applying your personal setting" after
    logon,Why?
    > I have 2 DC win2k server that last week I moved all roles from master DC
    to
    > additional DC from that time I have this problem!!
    > Now I can't remove AD from old DC(because I want to format it) because of
    > this error:"The DSA operation is unable to proceed because of a DNS lookup
    > failure."
    > How can I troubleshooting this problem?
    > Thank you.
    > ----------
    > Regards Mahnaz


  • Next message: Die: "Re: spamming solution for small networks"

    Relevant Pages

    • Re: NT to W2K3 Migration
      ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
      (microsoft.public.windows.server.active_directory)
    • Re: Migrating NT4 to Windows 2003
      ... Migrating from Windows NT Server 4.0 to Windows Server 2003 ... How to Upgrade from Windows NT Server 4.0 ... Best Practice Active Directory Design for Managing Windows Networks ... ensure that you have designed a DNS ...
      (microsoft.public.windows.server.active_directory)
    • RE: VPN Clients Not Registering in AD DNS
      ... via VPN, the DNS records of the VPN clients are unable to be registered. ... Windows 2003 server? ... please let me know whether the clients get the IP ...
      (microsoft.public.windows.server.sbs)
    • Re: NT Domain to AD migration
      ... Windows 2000/XP always prefer Kerberos authentication, ... Server 2003 Active Directory service, ensure that you have designed a DNS ...
      (microsoft.public.windows.server.active_directory)
    • Re: 2003 Migration
      ... Best Practice Active Directory Design for Managing Windows Networks ... Windows Server 2003 Tools ... ensure that you have designed a DNS and Active ...
      (microsoft.public.windows.server.active_directory)

    Loading