Link to home
Start Free TrialLog in
Avatar of mbruton44
mbruton44

asked on

DNS PROBLEMS - UPGRADED FROM NT 4.0 to WIN 2003 - Many Different Problems

After upgrading to 2003, I'm having all kinds of problems.

Basic setup:

Most of the servers have the _ in their name

smi_pdc - primary domain controller(2003)
smi_dns- dns server/ hosted web site (NT 4.0)
smi_bdc- backup domain controller (NT 4.0)
Exchange- exchange server 5.5 (NT 4.0) will be upgrading to 2003 as soon as I can get this mess cleaned up
** and a mixture of other nt and 2000 servers**

Clients are running xp pro

The domain was sminc.net and now is sunbelt.sminc.net

THe users now are getting disconnected from exchange server, taking awhile for them to authenticate and login, getting disconnected from apps that we have running on some of the servers.

here is the netdiag results.  Any help would be greatly appreicated.  should I have kept the domain as sminc.net (or sunbelt) instead of sunbelt.sminc.net?

C:\Program Files\Support Tools>netdiag.exe

...........................................

    Computer Name: SMI_PDC
    DNS Host Name: smi_pdc.sunbelt.sminc.net
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 6 Model 7 Stepping 3, GenuineIntel
    List of installed hotfixes :
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : smi_pdc.Sunbelt
        IP Address . . . . . . . . : 10.1.1.49
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.1.1
        Primary WINS Server. . . . : 10.1.1.49
        Secondary WINS Server. . . : 10.1.1.50
        Dns Servers. . . . . . . . : 10.1.1.49
                                     4.2.2.2

        IpConfig results . . . . . : Failed
            Pinging the Secondary WINS server 10.1.1.50 - not reachable

        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

        WINS service test. . . . . : Failed
            The test failed.  We were unable to query the WINS servers.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Failed
    [WARNING] The DNS host name 'smi_pdc.sunbelt.sminc.net' valid only on Window
s 2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME]
          [WARNING] Cannot find a primary authoritative DNS server for the name
            'smi_pdc.sunbelt.sminc.net.'. [RCODE_SERVER_FAILURE]
            The name 'smi_pdc.sunbelt.sminc.net.' may not be registered in DNS.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '10.1.1.49'. Please wait for 30 minutes for DNS server replication.
    [WARNING] The DNS entries for this DC are not registered correctly on DNS se
rver '4.2.2.2'. Please wait for 30 minutes for DNS server replication.
    [FATAL] No DNS servers have the DNS records for this DC registered.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully

Avatar of oBdA
oBdA
Your first error is here:
>> Dns Servers. . . . . . . . : 10.1.1.49
>>                                4.2.2.2

Remove the 4.2.2.2 DNS server; let the DC point to itself *only* for DNS resolution. Do the same with all of your domain members; no external DNS servers.
Instead, configure forwarders in your DNS server's porperties to point to the 4.2.2.2 DNS. If you can't access the forwarders, delete the root zone (it's the single dot: ".") on your DNS in your forward lookup zones.

The next one is here:
>>DNS test . . . . . . . . . . . . . : Failed
>>   [WARNING] The DNS entries for this DC are not registered correctly on DNS server '10.1.1.49'. Please wait for 30 minutes for DNS server replication.
>>   [FATAL] No DNS servers have the DNS records for this DC registered.

It seems like Dynamic Updates aren't enabled on your domain's DNS zone. Right-click your forward and reverse lookup zones, go to Properties, and make sure that Dynamic Updates are enabled.

Once you've corrected this, open a command prompt and enter "ipconfig /registerdns", then stop and re-start the netlogon service. Check if the SRV records have been created (see link below).

10 DNS Errors That Will Kill Your Network
http://www.mstraining.com/misc/10_dns_errors_that_will_kill_you.htm

Frequently Asked Questions About Windows 2000 DNS and Windows Server 2003 DNS
http://support.microsoft.com/?kbid=291382

Best practices for DNS client settings in Windows 2000 Server and in Windows Server 2003
http://support.microsoft.com/?kbid=825036

How to Verify the Creation of SRV Records for a Domain Controller
http://support.microsoft.com/?kbid=241515

How Domain Controllers Are Located in Windows
http://support.microsoft.com/?kbid=247811

How Domain Controllers Are Located in Windows XP
http://support.microsoft.com/?kbid=314861

SRV Resource Records May Not Be Created on Domain Controller
http://support.microsoft.com/?kbid=239897

HOW TO: Configure DNS for Internet Access in Windows Server 2003
http://support.microsoft.com/?kbid=323380

HOW TO: Troubleshoot DNS Name Resolution on the Internet in Windows Server 2003
http://support.microsoft.com/?kbid=816567
Avatar of mbruton44
mbruton44

ASKER

Do i need to create a anything in the forward lookup zone?

And I only have a 10.1.1.xSubnet in the reverse lookup.  Do i need to make any changes that this?

Thanks again.
Avatar of mbruton44
mbruton44

ASKER

so does it seem as if the DNS is what is causing all of the network problems?
Avatar of mbruton44
mbruton44

ASKER

WIll the undescore in the computer name have anything to do with it smi_pdc?
Avatar of mbruton44
mbruton44

ASKER

Also, when I do a nslookup from a cliet I get the following:

C:\Documents and Settings\MikeB>nslookup
*** Can't find server name for address 10.1.1.46: Non-existent domain
Default Server:  vnsc-pri.sys.gtei.net
Address:  4.2.2.1

>
Avatar of oBdA
oBdA
Well, if you haven't done so yet, you need to create a forward lookup zone "sunbelt.sminc.net" (and allow dynamic updates in it).
Allow dynamic updates in your reverse lookup zone, too.
And, as I said above, do NOT use the 4.2.2.1 DNS on any of your domain members. Only use your DC for DNS, and configure forwarders to 4.2.2.1.

Setting Up the Domain Name System for Active Directory
http://support.microsoft.com/?kbid=237675
Avatar of mbruton44
mbruton44

ASKER

When i do an IPCONFIG /ALL on a client the dns is 10.1.1.46 and 4.2.2.1.  This is the nt dns server.  These are given out by the DHCP on the 2003 machine in question.  Should I point them to 10.1.1.49 (the 2003 machine)?
Avatar of oBdA
oBdA
Definitely. Using your ISP's DNS server for internal name resolution is big no-no. The only place in your network where your ISP's DNS server should be found is in the forwarders tab on your DNS server.
Please read the articles above (especially the FAQ and the "10 DNS errors") to understand why you need correct DNS settings for your domain to function.
Avatar of mbruton44
mbruton44

ASKER

ok i changed it and i can do a nslookup fine now.  but now our web site is down.  it is on the smi_dns server.  this is our dns server running nt 4.0
Avatar of oBdA
oBdA
What do you mean with "web site is down"? Can't you access it anymore from your intranet? If so, then it's because you seem to have the same external DNS name as your AD DNS name. Create a host entry "www" in your 2003 DNS server and let it point to your web server.
Avatar of mbruton44
mbruton44

ASKER

how do i do this?  is it because I called the forward lookup zone the same as the domain name?
Avatar of mbruton44
mbruton44

ASKER

Also, do i need to change all of the other servers and clients to the 10.1.1.49 DNS server on the 2003 machine?
Avatar of mbruton44
mbruton44

ASKER

yes the site is down only from my PC.
Avatar of oBdA
oBdA
Yes; your internal DNS is now the authoritative DNS server for your domain name and won't forward any names it can't resolve to an external DNS.
In general, you're better of naming your AD domain something like companyname.intern or .local or whatever, so that it doesn't come to these collisions (unless you're hosting your own web and email).
You'll have to enter a host name for any external server in your domain for your clients to be able to resolve it.
Anyway, just go to the forward lookup zone, right-click, choose "New host record", name it www, and give it the external address.
To retrieve external address directly from your ISP's DNS while still using your internal DNS server, you can use
nslookup www.servername.com 4.2.2.1
Avatar of mbruton44
mbruton44

ASKER

We are hosting our own email and web site.  THey are all on different servers.   Should I rename the AD domain?  ALso, I am still not able to view the web site internally.  I have put a www host record to our external IP.  The folders go Fowarders > sminc.net .  The host is in the sminc.net folder. Then i have a sunbelt folder under that.

Thanks again for all of your help.
Avatar of mbruton44
mbruton44

ASKER

also, i can ping the web site www.sminc.net
Avatar of oBdA
oBdA
Well, theoretically,  you can rename a Server 2003 domain, but it's not that easy; you can have a look at it:
Windows Server 2003 Active Directory Domain Rename Tools
http://www.microsoft.com/windowsserver2003/downloads/domainrename.mspx

Anyway, can you reach the web site when you enter the IP address instead of the name into the browser?
Avatar of mbruton44
mbruton44

ASKER

cannot reach the web site via ip address.
Avatar of oBdA
oBdA
If you can't reach it using the IP address, then it's not related to the DNS settings. If it's only your machine that's experiencing this, you might consider rebooting it. It's rather strange that you can ping it but not display the web site on it.
Avatar of mbruton44
mbruton44

ASKER

its like that on all the pcs now. The ones where the dns has changed to the 2003 machine.  the ones pointing to the old dns .46 where the site is, they can view it.
Avatar of mbruton44
mbruton44

ASKER

i just changed my computers dns to .46 and the site came up.
Avatar of mbruton44
mbruton44

ASKER

now the dns settings on the .46 (nt 4.0) are pointing to the 2003 machine .49.  The dns suffix is sminc.net.

Also the dns manager is running on this machine.  does it need to be turned off or the dns servers manager be disabled?
Avatar of oBdA
oBdA
Then you should be able to browse to the web site using the IP address returned by the 10.1.1.46 server.
Open a command prompt and enter
nslookup www.sminc.net 10.1.1.46
If it works, enter this IP address for the www host name in your .49 DNS.
It doesn't matter if the DNS manager is running on your machine.
If it's Windows 2000 or later, enter
ipconfig /flushdns
in a command prompt as well, to make sure the DNS cache isn't playing games with you.
Avatar of mbruton44
mbruton44

ASKER

This is what I got.

C:\Documents and Settings\MikeB>nslookup www.sminc.net 10.1.1.46
*** Can't find server name for address 10.1.1.46: Non-existent domain
Server:  UnKnown
Address:  10.1.1.46

Name:    www.sminc.net
Address:  65.165.71.73
Avatar of oBdA
oBdA
Then make sure the www host on your .49 DNS is pointing to 65.165.71.73 as well.
Make sure you can resolve the new name:
nslookup www.sminc.net 10.1.1.49
Then change your DNS to .49 again, run ipconfig /flushdns, and try the web site again.
Avatar of mbruton44
mbruton44

ASKER

put the .73 host into the same folder as the .46?
Avatar of mbruton44
mbruton44

ASKER

That worked!!! Thank you so much.

Now will changing the DNS on all of the servers like exchange, and our other application servers solve the connection problems?  Is that what is causing it to do that?
Avatar of oBdA
oBdA
That's pretty likely to cure most of your issues. It's imperative (at least for your clients running W2k or later) that you have a correctly configured DNS for your Active Directory to work.
For your NT4 clients, you still need WINS, of course.
Avatar of mbruton44
mbruton44

ASKER

here is the latest netdiag

and are there any other tests that i can run or look at anything to make sure that it is conifured and running properly?

C:\Program Files\Support Tools>netdiag.exe

.........................................

    Computer Name: SMI_PDC
    DNS Host Name: smi_pdc.sunbelt.sminc.net
    System info : Windows 2000 Server (Build 3790)
    Processor : x86 Family 6 Model 7 Stepping 3, GenuineIntel
    List of installed hotfixes :
        Q147222


Netcard queries test . . . . . . . : Passed



Per interface results:

    Adapter : Local Area Connection

        Netcard queries test . . . : Passed

        Host Name. . . . . . . . . : smi_pdc.Sunbelt
        IP Address . . . . . . . . : 10.1.1.49
        Subnet Mask. . . . . . . . : 255.255.255.0
        Default Gateway. . . . . . : 10.1.1.1
        Primary WINS Server. . . . : 10.1.1.49
        Secondary WINS Server. . . : 10.1.1.50
        Dns Servers. . . . . . . . : 10.1.1.49

        IpConfig results . . . . . : Failed
            Pinging the Secondary WINS server 10.1.1.50 - not reachable

        AutoConfiguration results. . . . . . : Passed

        Default gateway test . . . : Passed

        NetBT name test. . . . . . : Passed
        [WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenge
r Service', <20> 'WINS' names is missing.

        WINS service test. . . . . : Failed
            The test failed.  We were unable to query the WINS servers.


Global results:


Domain membership test . . . . . . : Passed


NetBT transports test. . . . . . . : Passed
    List of NetBt transports currently configured:
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    1 NetBt transport currently configured.


Autonet address test . . . . . . . : Passed


IP loopback ping test. . . . . . . : Passed


Default gateway test . . . . . . . : Passed


NetBT name test. . . . . . . . . . : Passed
    [WARNING] You don't have a single interface with the <00> 'WorkStation Servi
ce', <03> 'Messenger Service', <20> 'WINS' names defined.


Winsock test . . . . . . . . . . . : Passed


DNS test . . . . . . . . . . . . . : Passed
    [WARNING] The DNS host name 'smi_pdc.sunbelt.sminc.net' valid only on Window
s 2000 DNS Servers. [DNS_ERROR_NON_RFC_NAME]
    PASS - All the DNS entries for DC are registered on DNS server '10.1.1.49'.


Redir and Browser test . . . . . . : Passed
    List of NetBt transports currently bound to the Redir
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    The redir is bound to 1 NetBt transport.

    List of NetBt transports currently bound to the browser
        NetBT_Tcpip_{697392C8-6CDB-411E-9679-A40F4C671110}
    The browser is bound to 1 NetBt transport.


DC discovery test. . . . . . . . . : Passed


DC list test . . . . . . . . . . . : Passed


Trust relationship test. . . . . . : Skipped


Kerberos test. . . . . . . . . . . : Passed


LDAP test. . . . . . . . . . . . . : Passed


Bindings test. . . . . . . . . . . : Passed


WAN configuration test . . . . . . : Skipped
    No active remote access connections.


Modem diagnostics test . . . . . . : Passed

IP Security test . . . . . . . . . : Skipped

    Note: run "netsh ipsec dynamic show /?" for more detailed information


The command completed successfully
Avatar of oBdA
oBdA
Looks a lot better.
One more thing I just noticed:
>> Primary WINS Server. . . . : 10.1.1.49
>> Secondary WINS Server. . . : 10.1.1.50
Since this is a WINS server, let it only point to itself.

Setting Primary and Secondary WINS Server Options
http://support.microsoft.com/?kbid=150737

Another tool you can use is dcdiag (support tools as well):
DCDiag and NetDiag in Windows 2000 Facilitate Domain Join and DC Creation
http://support.microsoft.com/?kbid=265706
Avatar of mbruton44
mbruton44

ASKER

Thanks again for all of your help.

Another quick question.  I am still having some connectivity issues with the NT servers.  Do I need to take them out of the domain and reconnect them?  Also, do you think it would be best to go back to the original domain sminc.net instead of the sunbelt.sminc.net?
Avatar of oBdA
oBdA
The connectivity problems might be due to the fact that the WINS entries on your WINS server weren't pointing to itselves (only). Try to reboot the WINS servers, which should re-register any missing entries, then the NT4 servers having problems.
Rejoining them to the domain probably won't help much, as long as you don't get events like"the primary account for this machine is missing" or "the trust relationship has been broken" in your event log.
As I said, renaming a domain is not for the weak of heart and certainly nothing you should try unless you've done it in a test environment first.
If you decide to rename, it's probably best to do that before you introduce the Exchange 2003, as this introduces additional problems.
Avatar of mbruton44
mbruton44

ASKER

I've gone to the wins server in 2003 and there were none listed.  I added the 2003 machine and it says, cannot find wins server.  How do I go about getting that to run.
Avatar of oBdA
oBdA
Have you installed WINS at all?
HOW TO: Install WINS in Windows Server 2003
http://support.microsoft.com/?kbid=323429
Avatar of mbruton44
mbruton44

ASKER

wins hasn't been installed.  the article didn't come up.
Avatar of oBdA
oBdA
Don't you just love it when Microsoft withdraws their KB articles? It's still referenced here:
The Windows Components Wizard finish page stops responding during installation of DNS, DHCP, or WINS in Windows Server 2003
http://support.microsoft.com/?id=838425
Anyway, install it through Control Panel, Add/Remove Software, Add/Remove Windows Components, and then it's someplace under Network Services; can't tell exactly at the moment.
Avatar of mbruton44
mbruton44

ASKER

The WINS server component has already been installed.  Do I need to create a WINS database?  
ASKER CERTIFIED SOLUTION
Avatar of oBdA
oBdA
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial