Duplicate name conflict, but not shown using Nbtstat -n

I'm running Windows 2000, SP4. DNS is integrated with AD, which was
running fine for sometime. I am also running WINS as a backup.
However, recently started having problems opening up AD with error:
"Naming information cannot be located because the network path was not
found". And I started getting a NSLOOKUP error: "Can't find server
name for address 192.x.x.x: No response from server". This problem
clears up when I reboot, and runs fine for some hours before becoming
non-functional again. Sometimes, I can get stop these errors by
clearing out the Security log, and restarting the following services:
NT LM Security Support Provider, DNS, and WINS - but this doesn't work
all the time. Only rebooting works consistently.

In an attempt to solve this original problem, I added a static record
into WINS. That's when I started getting the duplicate name error,
and the WINS snap-in stopped working. When I ran nbtstat -n, I did
see the conflict. I was able to delete that conflicting static record
in WINS, deleted all the files in the WINS directory (allowing the
WINS database to be dynamically rebuilt from DHCP server) but now I'm
still getting the duplicate name error (Event id: 4319). Yet, now
when I run nbtstat -n, it confirms that there isn't a conflicting name
on the network. So, I don't understand why I am still getting this
duplicate name error, which prohibits browsing and connecting to other
servers using UNC.

The original DNS/AD problem continues.

I would appreciate any ideas, suggestions, or solutions!

Regards,
Naitauba