Re: Windows 2003 server and NT server on same network

The slow login is probably related to the difference between NT and
W2k/2k3 . NT uses Netbios names to find a login server. With AD you find the
login server through SRV records in DNS.

A client machine which will log into an AD domain should have its DNS
setting pointing to the local DNS server which contains the SRV records
added to DNS by the Netlogon service.

Maurice Bishop wrote:
> I have a performance problem.
>
> I have a 50 user network on which there are four servers. Two are
> running NT4 Server with SP6a on domain OLDOMAIN and two servers
> running Windows 2003 server with NEWDOMAIN.
>
> I have set up a two way trust relationship between the two domains and
> duplicated the user names and accounts on both domains. I did this
> manually.
> DHCP server is running on the Active Directory DC. There is only one
> DHCP server on the network.
>
> The two Windows 2003 servers are running Active Directory. The second
> server is pointing to the first (DC) for it's primary DNS entry.
> Other than that, the Windows 2003 server is set up with it's default
> values. In my humble opinion, it is very easy to set up Windows 2003
> server - much of the config works out of the box.
>
> First problem:
>
> When using a Windows XP Pro client (DHCP enabled) that is logged into
> the OLDOMAIN, if I go to pick up a file from a Windows 2003 server,
> it takes a long time to scan for the file in Windows Explorer - up to
> a minute. This is an intermittent problem.
>
> Second problem.
>
> Using a Windows XP Pro client (DHCP enabled), if I login to the
> NEWDOMAIN, it takes up to two minutes to display the desktop. Having
> entered the username credentials, the screen clears and just sits
> there for anything up to two minutes.
>
> Any help on this one would be greatly appreciated.
>
> TIA
>
> Maurice


.

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: Secondary DNS and PIX
    ... Of course I updated them with the DNS ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ... Windows SBS 2003 SP1 is available. ...
    (microsoft.public.windows.server.sbs)
  • 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: Secondary DNS and PIX
    ... SBS SP1 was a very specific service pack comprising several ... Root hints for DNS means you leave the forwarders ... WINDOWS SERVER 2003 FOR SMALL BUSINESS SERVER, ...
    (microsoft.public.windows.server.sbs)
  • 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)
Loading