Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations SkipVought on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

AD and DNS not talking, strange error

Status
Not open for further replies.

igaff

IS-IT--Management
Mar 10, 2003
6
0
0
GB
Hi, this is a post I just made to the ms news groups, was wondering if anyone here had any idea?

Thanks,
________________________________________________________

Forgot to add, when you attempt to browse the network on the domain
controller machine, i get the following error pop up:

\\share not accessible
the name limit for the local computer network adapter was exceded

"Stephen Gaffney" wrote:

> Hi,
>
> I'm having some problems with active directory and DNS - seems the DNS
> server isn't talking to AD anymore, most likely because AD isn't responding
> correctly.
>
> I've got a number of warnings and errors here, hopefully someone will be
> able to shed some light on it for me, before I go wading in an breaking it!
>
> This is from a win2k domain controller (the FSMO), running the w2k3 scheme
> updates, and the primary DNS. There is also a w2k3 domain controller in the
> domain.
>
> This is what I get when I run DCDIAG
> C:\>dcdiag
>
> Domain Controller Diagnosis
>
> Performing initial setup:
> [saville] LDAP connection failed with error 58,
> The specified server cannot perform the requested operation..
> ***Error: The machine, saville could not be contacted, because of a bad net
> response. Check to make sure that this machine is a Domain Controller.
>
> These logs are from the system logs:
> Event Type: Error
> Event Source: MRxSmb
> Event Category: None
> Event ID: 8003
> Date: 06/12/2004
> Time: 16:36:52
> User: N/A
> Computer: SAVILLE
> Description:
> The master browser has received a server announcement from the computer
> BRIAN2 that believes that it is the master browser for the domain on
> transport NetBT_Tcpip_{6EBE32B0-C9C3-48D9-AC. The master browser is stopping
> or an election is being forced.
>
> Event Type: Error
> Event Source: Userenv
> Event Category: None
> Event ID: 1000
> Date: 07/12/2004
> Time: 16:04:26
> User: NT AUTHORITY\SYSTEM
> Computer: SAVILLE
> Description:
> Windows cannot determine the user or computer name. Return value (14).
>
> ------------------------------
> And these are from the DNS logs....
>
> Event Type: Error
> Event Source: DNS
> Event Category: None
> Event ID: 4000
> Date: 05/12/2004
> Time: 22:56:11
> User: N/A
> Computer: SAVILLE
> Description:
> The DNS server was unable to open Active Directory. This DNS server is
> configured to obtain and use information from the directory for this zone and
> is unable to load the zone without it. Check that the Active Directory is
> functioning properly and reload the zone. The event data is the error code.
>
> Event Type: Warning
> Event Source: DNS
> Event Category: None
> Event ID: 9999
> Date: 06/12/2004
> Time: 00:31:11
> User: N/A
> Computer: SAVILLE
> Description:
> The DNS server has encountered numerous run-time events. These are usually
> caused by the reception of bad or unexpected packets, or from problems with
> or excessive replication traffic. The data is the number of suppressed
> events encountered in the last 15 minute interval.
>
>
> I'd be very grateful if someone knowledgable could shed some light....
>
> Thanks,
 
Do you have a netdiag output? Is the server pointing to itself for DNS?
 
First check the server ip configurations ie it should point to itself for dns and reboot the server and let us know what happens.
Is the brain 2 computer a dc or a workstation? if you have two or more dcs make sure you check the ip configurations and reboot all the dcs
 
You can save yourself from reboots by running these two commands after making any IP changes:

ipconfig /flushdns
net stop netlogon & net start netlogon
 
Hi,

Thanks for your input - I'd gone ahead an rebooted the server last night before waiting for replies, and the problem has dissapeared.

I still have no idea what caused it tho. I'm guessing the it's to do with the network adpater getting all crossed up rather than a DNS/AD issue.

Brian2 is a workstation; workstations winning elections is something that actually happens quite a lot - is this not right? Any idea what I can do to stop this happening?

-steve
 
Sounds like you have XP Pro workstations. If that is the case, you need to disable the "Computer Browser" service on your XP workstations. This will prevent them from calling for an election.

Help! I've fallen and I can't reach my beer.
cheers.gif
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top