Solved

ADS errors and wierdness

Posted on 2011-09-16
2
751 Views
Last Modified: 2012-05-12
I need help answering all these questions / warning / errors reported below
Thank you in advance

We have two separate forest.
(1) Forest named Domain.local
(2) Other forest named Resource.local
There is a one way trust for this domain

Domain.local
Domains trusted by this domain (outgoing trust)
      Blank
Domains that trust this domain (incoming trust)
      Resource.local

We are getting a lot of 40961 errors on member servers that are in the resource.local domain
The errors on the servers report that

The Security System could not establish a secured connection with the server LDAP/DC-A.domain.LOCAL/domain.LOCAL@domain.LOCAL. No authentication protocol was available.

When running best practice analyzer it reports

On resource.local domain

Error: The DC-Resource-C.resource.LOCAL DNS server is referencing the invalid 172.16.1.10 DNS server on the vmxnet3 Ethernet Adapter (MAC: 00:50:FS:B9:10:H0) network adapter.

Error: The DC-Resource-E.resource.LOCAL DNS server is referencing the invalid 172.16.1.10 DNS server on the Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) (MAC: 28:1B:hB:92:De:84) network adapter.


Error: Dynamic DNS registration is enabled on the vmxnet3 Ethernet Adapter (MAC: 00:50:FS:B9:10:H0)  external network adapter on DC-Resource-C.resource.LOCAL server.

Error: Dynamic DNS registration is enabled on the Broadcom BCM5716C NetXtreme II GigE (NDIS VBD Client) (MAC: 28:1B:hB:92:De:84) external network adapter on the DC-Resource-E.resource.LOCAL server.

See also: KB 816592

Warning: The DC-Resource-C.resource.LOCAL server is not connected to any of the specified subnets.

Warning: The DC-Resource-E.resource.LOCAL server is not connected to any of the specified subnets.


On domain.local domain

Error: A subnet was not defined in this wizard for the 172.16.4.0/24 subnet found in the Office Active Directory site.

Error: A subnet was not defined in this wizard for the 172.16.5.0/24 subnet found in the Office Active Directory site.

Error: A subnet was not defined in this wizard for the 172.16.6.0/24 subnet found in the Office Active Directory site.

Error: A subnet was not defined in this wizard for the 172.16.7.0/24 subnet found in the Office Active Directory site.

Error: A subnet was not defined in this wizard for the 172.16.8.0/24 subnet found in the Office Active Directory site.



The Start of Authority resource record could not be found for the resource.local zone on the DC-A.domain.LOCAL DNS server.

The Start of Authority resource record could not be found for the resource.local zone on the DC-B.domain.LOCAL DNS server.

The Start of Authority resource record could not be found for the resource.local zone on the DC-C.domain.LOCAL DNS server.

The Start of Authority resource record could not be found for the resource.local zone on the DC-D.domain.LOCAL DNS server.



Error: Dynamic DNS registration is enabled on the Broadcom NetXtreme Gigabit Ethernet (MAC address: 04:62:99:h2:26:21) external network adapter on the DC-C.domain.LOCAL server.

Error: Dynamic DNS registration is enabled on the Broadcom NetXtreme Gigabit Ethernet (MAC address: 04:62:99:h2:26:21) external network adapter on the DC-D.domain.LOCAL server.

Error: Dynamic DNS registration is enabled on the Broadcom NetXtreme Gigabit Ethernet (MAC address: 04:62:99:h2:26:21) external network adapter on the DC-E.domain.LOCAL server.

Error: Dynamic DNS registration is enabled on the Broadcom NetXtreme Gigabit Ethernet (MAC address: 04:62:99:h2:26:21) external network adapter on the DC-F.domain.LOCAL server.


Warning: The DC-C.domain.LOCAL server is not connected to any of the specified subnets.

Warning: The DC-D.domain.LOCAL server is not connected to any of the specified subnets.

Warning: The DC-E.domain.LOCAL server is not connected to any of the specified subnets.

Warning: The DC-F.domain.LOCAL server is not connected to any of the specified subnets.

Warning: The DC-G.domain.LOCAL server is not connected to any of the specified subnets.




0
Comment
Question by:Indyrb
2 Comments
 
LVL 16

Accepted Solution

by:
Shaik M. Sajid earned 500 total points
ID: 36553308
this is the issue of DNS forwarders....

firstly create DNS forwarders in bothe servers as forwarders to each other.....


i.e rightclick DNS- Properties-forwarders-put the other server DNS- and finish....


in tcp ip properties put both DNS on each site primery and secondery....


ping both IP's and DNS...

then created trust relation ship....


all the best
0
 

Author Comment

by:Indyrb
ID: 36561619
So we have 6 ADS/DNS servers in each of the domains.
domain.local and resource.local

How should each server be forwarded in DNS

On each DNS server should it have itself as primary dns, then what as secondary dns
should others be added?

Should dynamic updates be enabled
Where is this configured?

What about use DNS suffix for this connection
0

Join & Write a Comment

Synchronize a new Active Directory domain with an existing Office 365 tenant
Is your Office 365 signature not working the way you want it to? Are signature updates taking up too much of your time? Let's run through the most common problems that an IT administrator can encounter when dealing with Office 365 email signatures.
This tutorial will show how to push an installation of Backup Exec to an additional server in both 2012 and 2014 versions of the software. Click on the Backup Exec button in the upper left corner. From here, select Installation and Licensing, then I…
This tutorial will walk an individual through locating and launching the BEUtility application to properly change the service account username and\or password in situation where it may be necessary or where the password has been inadvertently change…

744 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question

Need Help in Real-Time?

Connect with top rated Experts

12 Experts available now in Live!

Get 1:1 Help Now