WIN 2K DNS problem 1

[stenk]

We have upgraded a BDC that I promoted to a PDC to Windows 2000 Server.

We have only one other BDC (Was the PDC) on the network. I have installed AD.

My problem is the DNS Server on the DC does not seem to work.

When I try NSLOOKUP this is what I get

Microsoft Windows 2000 [Version 5.00.2195]
(C) Copyright 1985-2000 Microsoft Corp.

C:\>nslookup
*** Can't find server name for address 192.168.0.11: Non-existent domain
*** Default servers are not available
Default Server: UnKnown
Address: 192.168.0.11

It finds the IP address of the DC but not the DNS.

No events in the DNS event log

We are also running WINS and DHCP on the 2000 DC. All works OK, bar DNS!!!!!!!!!.

If someone could help me with this problem then that would be GREAT.

One XP box seems to loose network connection where he has to log out and log back in again to allow him to access network resources.
These are the events on his PC(notebook)

Event ID 1053, 1054 Source Usernv and 40961, 40962 LsaSRV

It seems to me that this is a problem on our main Server related to DNS. Not sure how to go about fixing these problems!!

Please help if you can

Many thanks

Sten

 

[wbg34]

*** Can't find server name for address 192.168.0.11: Non-existent domain
Try adding a host entry to your reverse lookup zone for your server. That should take care of the first part of the error message.
Make sure that you have the dc's ip listed as the primary dns server in your local area connections tcp/ip properties.


Electricity is actually made up of extremely tiny particles called electrons, that you cannot see with the naked eye unless you have been drinking.
Quote taken from Dave Barry

Bill.

 

[Jpoandl]

Can you go into the DNS console on your Windows 2000 server? Start -> Programs -> Administrative Tools -> DNS

Sometimes people run into problems when they upgrade the PDC to Windows 2000. This is because they are connected to the internet at the time they upgrade the domain. And because DNS wasn't really used (all that much) in NT 4.0, they sometimes point DNS to the ISP DNS servers. Then when you upgrade to AD, AD tries to write to the ISP DNS servers. The point here is to check to make sure your clients and servers are pointing to your internal DNS server(s).

Look at your DC's TCP/IP settings. It should be pointing to itself for DNS. Because this is the only server that is running DNS services (probably)


Once you get things running, I would in the DNS console. Create a reverse lookup zone as 192.168.0.x

-Hope this helps..







Joseph L. Poandl
MCSE 2000

If your company is in need of experts to examine technical problems/solutions, please check out

http://www.NJCOMPUTERNETWORKS.com

(Sales@njcomputernetworks.com)

 

[stenk]

Thanks wbg34,

How do I add a host entry to the reverse lookup zone? It only allows me to add another ZONE?

If you could let me know how to do this that would be great!!!

Kind regards,

Sten

 

[wbg34]

Your reverse lookup zone should look like your domains ip address in reverse (i.e. domain ip range was 10.0.1. then zone should look like Reverse lookup zone 1.0.10). If nothing like that is present, then create a new zone and enter the first three octets of your ip range when in the box that comes up. Click ok until back to the main dns window. Expand your reverse lookup zone and right click and select add host. Enter your servers ip address and name. Click ok and close dns.

Electricity is actually made up of extremely tiny particles called electrons, that you cannot see with the naked eye unless you have been drinking.
Quote taken from Dave Barry

Bill.

 

[stenk]

wbg34,

Thanks for your help mate!.

C:\>nslookup
Default Server: XXX.XX.domain.XX.XX
Address: 192.168.0.11

Cheers

Sten