Re: Logging into Active Directory Domain

From: Enkidu (enkidu_at_xyzcliffpxyz.com)
Date: 09/29/04


Date: Wed, 29 Sep 2004 18:43:06 +1200

On Tue, 28 Sep 2004 09:36:43 -0700, "Greg" <gkras19@aol.com> wrote:

>All users are logging into Netware 6 Server with E
>Directory 8.7.2.
>There is a Windows 2000 Server with Active Directory setup
>that users are not logging into, but accessing resorces on
>through mapped drives.
>
>I want to eventually do away with Novell and have all
>users logon to the Windows 2000 server. I tested one
>workstation out by removing the Novell Client and joining
>the Windows 2000 domain. My problem is that when i log
>into the network now, it takes about 8 minutes to fully
>login. I rebooted and still takes about 8 minutes to Log
>on.
>Is there a way of speeding this up??
>
That is definitely not normal, and the others have pointed at the most
obvious cause - DNS. You need to have either a MS DNS or a DNS that is
compatible with it, or at least supports SRV records. Also, the
clients and services on the server must be setup to automatically
register themselves with DNS otherwise things won't go well. Consider
such elements as DHCP and WINS as well as DNS.

I think you need to do a bit of reading. There's any number of book
about Windows 200x AD domains, but probably not too many about NDS to
AD migration. There's probably a heap of stuff on the MS web site
though.

Such as:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnactdir/html/msdn_activedirvsnds.asp

http://www.microsoft.com/windowsserver2003/migrate/novell/default.mspx

There's likely to be what might be called a pro-Microsoft flavour to
the articles, which I've not looked at myself, just dredged them from
the knowledge base. It depends on how much of a fan of Novell you are
how that affects you! For myself, I did NOT like being a user of a
Novell network, but that maybe could have been due to the way it was
set up!

Cheers,

Cliff

{MVP Directory Services}



Relevant Pages

  • 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: Find AD hostname from Linux command line
    ... The Windows XP workstation gets an IP ... "Register this connection's addresses in DNS" turned ON. ... If I am on a Linux server and do "ping lancelot.ad.mydomain.com", ...
    (microsoft.public.win2000.dns)
  • Re: Two Win2k3 questions ... Roaming Profiles & Access Privileges ...
    ... >DHCP, DNS, Print Server, and File Server responsibilities. ... lookup zone on Windows NT" ... http://support.microsoft.com?kbid=229873 "Delegate Control Wizard Cannot Be Used ...
    (microsoft.public.win2000.advanced_server)
  • RE: Dynamic Update of A&PTR Records - Best Practice?
    ... The DNS server does not support the DNS dynamic update protocol; ... For Windows Server 2003-based computers, the primary full computer name is ... When one of these events triggers a DNS update, the DHCP Client service, ...
    (microsoft.public.windows.server.dns)
  • 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)