Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 773
  • Last Modified:

ADS errors and wierdness

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
Indyrb
Asked:
Indyrb
1 Solution
 
Sajid Shaik MSr. System AdminCommented:
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
 
IndyrbAuthor Commented:
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

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now