Dns experts please

Event Type: Error
Event Source: DNS
Event Category: None
Event ID: 6702
Date: 8/28/2002
Time: 7:43:53 AM
User: N/A
Computer: TERMINAL
Description:
DNS Server has updated its own host (A) records. In order to insure that its DS-integrated peer DNS servers are able to replicate with this server, an attempt was made to update them with the new records through dynamic update. An error was encountered during this update, the record data is the error code.

If this DNS server does not have any DS-integrated peers, then this error
should be ignored.

If this DNS server's ActiveDirectory replication partners do not have the correct IP address(es) for this server, they will be unable to replicate with it.

To insure proper replication:
1) Find this server's ActiveDirectory replication partners that run the DNS server.
2) Open DnsManager and connect in turn to each of the replication partners.
3) On each server, check the host (A record) registration for THIS server.
4) Delete any A records that do NOT correspond to IP addresses of this server.
5) If there are no A records for this server, add at least one A record corresponding to an address on this server, that the replication partner can contact. (In other words, if there multiple IP addresses for this DNS server, add at least one that is on the same network as the ActiveDirectory DNS server you are updating.)
6) Note, that is not necessary to update EVERY replication partner. It is only necessary that the records are fixed up on enough replication partners so that every server that replicates with this server will receive (through replication) the new data.
Data:
0000: 2a 23 00 00

Hi,

I don't think this is a DNS issue. All your clients, except the w2k client, are able to join the domain and access network resources.

The error message you posted from the event viewer has to do with DNS replication partners. That might be a different problem.

The problem here is that the w2k client is not able to join the domain. I don't think it's a configuration setting, because you did reinstall the O/S. However, I would still test to see if you can ping the DNS server byIP address.

If you can't, then try pinging other clients. If you can't ping anyone else by IP, I would try using a different network card, or try another cable.

This info came straight from microsoft:

Cause:
This behavior can occur when the Transmission Control Protocol/Internet Protocol (TCP/IP) configuration is using the incorrect IP address for the Domain Name Service (DNS) or WINS server on your network, or when no name server IP addresses are specified.
Resolution:
To resolve this behavior, make sure that the IP addresses of the DNS and WINS servers on your network are specified correctly in your TCP/IP settings.
More Information:
To verify that the relevant IP addresses are correct, follow these steps:

1.On the desktop, right-click My Network Places, and then click Properties.
2.Right-click the appropriate connection object, and then click Properties.
3.Click Internet Protocol(TCP/IP), and then click Properties.
4.Click Advanced.
5.Click DNS, and then click Add. In the DNS Server box, type the IP address of the DNS server to use to resolve DNS fully qualified domain names (FQDN), and then click Add.
6.Repeat this procedure to add the IP addresses of each DNS server on your network. After adding all DNS server IP addresses, click the arrow buttons to arrange the list of IP addresses in the preferred order of use.
7.Click WINS, and then click Add. In the WINS Server box, type the IP address of the WINS server to use to resolve NetBIOS names, and then click Add.
8.Repeat this procedure to add the IP addresses of each WINS server on your network. After adding all WINS server IP addresses, click the arrow buttons to arrange the list of IP addresses in the preferred order of use.
9.Click OK in the open dialog boxes to close them and to save the new settings.

The WINS portion may not apply in your exact situation. However 1 other related article said to check the same thing basicly. Make sure the IP address are correctly pointing to the right DNS server. Check your advanced TCP/IP properties in DNS tab.

Hope this helps
Jason

I suspect it is a NIC card problem. I've had this problem before (and I think the error message was the same), whereby a laptop could not pick up a clean/full signal from a switch. It was on the borderline of 300feet. However, when I put in a PCMCIA card, which has a little more power, in this case, the laptop worked fine. It appeared to authenticate on the original NIC port, then came up with that message.
I would swap out the NIC cards, one by one, and replace with new ones. Guess you could swap the cable at the same time.
I don't think it is a DNS/WINS issue. I guess you have all these entered correctly? But the fact the other OS's work fine, seems strange. On the internal NIC, I don't think you need to put in DNS and WINS...maybe try it without?
Good Luck.

I would say the prob is DNS related. Your win2k server is obviously the DNS server as well, correct? If this is the case, your win2k server is most likely set as ROOT. Open the DNS MMC and delete the root entry. Here is the Techrepublic article thatI followed for a solution....
https://www.techrepublic.com/article.jhtml?id=r00220020613joh01.htm&fromtm=e102-2
(please remove any spaces)
Good luck!

Mike