Windows 2003 server and NT server on same network

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

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

Many thanks Bill

I understand - I think.

What would be your course of action?

TIA

Maurice


"Bill Grant" <not.available@online> wrote in message
news:(E-Mail Removed)...
> 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
>
>

AD clients need to use the local DNS to find AD resources. Configure
DHCP to give the clients the local DNS server IP as their DNS address. If
they need to resolve "foreign" URLs as well, configure your local DNS server
to forward to a public DNS server.

Maurice Bishop wrote:
> Many thanks Bill
>
> I understand - I think.
>
> What would be your course of action?
>
> TIA
>
> Maurice
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:(E-Mail Removed)...
>> 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

Bill

I have done this and the result is spectacular. Performance is back up to
speed.

Many thanks for your advice.

Maurice

________________________________

"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> AD clients need to use the local DNS to find AD resources. Configure
> DHCP to give the clients the local DNS server IP as their DNS address. If
> they need to resolve "foreign" URLs as well, configure your local DNS
> server to forward to a public DNS server.
>
> Maurice Bishop wrote:
>> Many thanks Bill
>>
>> I understand - I think.
>>
>> What would be your course of action?
>>
>> TIA
>>
>> Maurice
>>
>>
>> "Bill Grant" <not.available@online> wrote in message
>> news:(E-Mail Removed)...
>>> 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
>
>