2 site and muliple problems

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi,

I recently created 2 sites, and now I am having nothing but trouble.
Originally I had 1 network 192.168.1.0, then I created another 192.168.2.0,
joined together by a router. I then created 2 sites, one for the
192.168.1.0, and another for the 192.168.2.0. The site A (192.168.1.0) has 2
DC, 2 GC and 2 DNS servers. Site B (192.168.2.0) has 1 DC, 1 GC, and 1 DNS.
DNS is set to be active Directory integrated. Here is the list of the
problems:
The index in the forward lookup zone in site B is higher than that of Site
A.

Websites can only be access by ip address and not url.

The brigehead server in site A has the following errors in the Directory
services event log viewer. Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1265
Date: 4/24/2005
Time: 1:20:55 AM
User: N/A
Computer: DC1
Description:
The attempt to establish a replication link with parameters
Partition: CN=Schema,CN=Configuration,DC=WIND-GATE
Source DSA DN: CN=NTDS
Settings,CN=DC3,CN=Servers,CN=SITEB,CN=Sites,CN=Configuration,DC=WIND-GATE
Source DSA Address: d7af2fcb-p004-4380-b938-2658ecd210b0._msdcs.WIND-GATE
Inter-site Transport (if any): CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=WIND-GATE

failed with the following status:

The DSA operation is unable to proceed because of a DNS lookup failure.

The record data is the status code. This operation will be retried.
Data:
0000: 4c 21 00 00 L!..


Event Type: Warning
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1566
Date: 4/24/2005
Time: 1:35:56 AM
User: N/A
Computer: DC1
Description:
All servers in site CN=SITEB,CN=Sites,CN=Configuration,DC=WIND-GATE that can
replicate partition DC=WIND-GATE over transport CN=IP,CN=Inter-Site
Transports,CN=Sites,CN=Configuration,DC=WIND-GATE are currently unavailable.


Event Type: Error
Event Source: NTDS KCC
Event Category: Knowledge Consistency Checker
Event ID: 1311
Date: 4/24/2005
Time: 1:35:56 AM
User: N/A
Computer: DC1
Description:
The Directory Service consistency checker has determined that either (a)
there is not enough physical connectivity published via the Active Directory
Sites and Services Manager to create a spanning tree connecting all the sites
containing the Partition DC=WIND-GATE, or (b) replication cannot be performed
with one or more critical servers in order for changes to propagate across
all sites (most often due to the servers being unreachable).
For (a), please use the Active Directory Sites and Services Manager to do
one of the following:
1. Publish sufficient site connectivity information such that the system can
infer a route by which this Partition can reach this site. This option is
preferred.
2. Add an ntdsConnection object to a Domain Controller that contains the
Partition DC=WIND-GATE in this site from a Domain Controller that contains
the same Partition in another site.
For (b), please see previous events logged by the NTDS KCC source that
identify the servers that could not be contacted.

Any help is appreciated.

Regards,
Sam
ps I have added a registry entry that Microsoft recommends to allow client
to automatically register with DNS.
 
Sam said:
Hi,

I recently created 2 sites, and now I am having nothing but trouble.
Originally I had 1 network 192.168.1.0, then I created another
192.168.2.0,
joined together by a router. I then created 2 sites, one for the
192.168.1.0, and another for the 192.168.2.0. The site A (192.168.1.0)
has 2
DC, 2 GC and 2 DNS servers. Site B (192.168.2.0) has 1 DC, 1 GC, and 1
DNS.
DNS is set to be active Directory integrated. Here is the list of the
problems:
The index in the forward lookup zone in site B is higher than that of Site
A.

Websites can only be access by ip address and not url.
Click to expand...

Regards,
Sam
ps I have added a registry entry that Microsoft recommends to allow client
to automatically register with DNS.
Click to expand...

This is difficult to ascertain without additonal info. If you can provide:

1. An ipconfig /all from all of your DCs
2. An Ipconfig /all of a client in SiteA and a client in SiteB
3. The actual DNS domain name in AD
4. If dynamic updates are allowed.
5. If the two sites are using a VPN to connect them or the traffic is going
thru a NAT (NAT will not work unless using a VPN tunnel).

Thanks


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Paramount: What's up with taking Enterprise off the air??
Infinite Diversities in Infinite Combinations.
=================================
 
ps I have added a registry entry that Microsoft recommends to allow client
to automatically register with DNS.
Click to expand...

Why did you have to add this reg entry?

Normally this just works by default unless misconfigured. The ipconfig /alls
will help to determine this.

Ace
 
Back
Top