Gpresult displays domain typ windowsnt4?

Gpresult displays domain type windowsnt4?  Should this be correct?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

James MontgomeryCommented:
Refer to this, is it applicable?

How is the health of your DCs - dcdiag, netdiag etc?
That depends ...
Was this domain upgraded from NT4?
This could be a result of incorrect DNS setting as well; in short: make sure you're *only* using your DC(s) as DNS server in the TCP/IP settings on *all* domain members. The *only* place in your network configuration where your IPS's DNS servers may be configured is the Forwarders section in the DNS properties.
For further troubleshooting, you can use dcdiag.exe and netdiag.exe (both support a /fix parameter to fix small problems on the fly) to check your system for errors in the domain setup.

Windows Server 2003 Service Pack 1 32-bit Support Tools

Windows Server 2003 Service Pack 2 32-bit Support Tools

For details about the correct DNS configuration in an AD domain, check these:

10 DNS Errors That Will Kill Your Network

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003

How to Verify the Creation of SRV Records for a Domain Controller

Note that gpresult.exe can and will only differentiate between NT4 and AD; a W2k3 AD domain will still be identified as Windows 2000.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
mkurtzhalsAuthor Commented:
Come to think of it, this server may have originally been NT4
Depending on how your did your upgrade, you should check if the "NT4Emulator" value has been deleted/set to 0 on all your DCs; it might have been manually added to the DC during the upgrade and never have been removed.
Check here for details:
How to prevent overloading on the first domain controller during domain upgrade
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Active Directory

From novice to tech pro — start learning today.