One server can't see the other server


P

prmolina

I have two W2K servers acting as domain controllers and DNS servers for the
domain. When I open the DNS .msc on DC1, I can view and manage DNS on both
DC1 and DC2. However, when I do the same on DC2 I can only manage DNS on
DC2: DC1 appears with a red X. I've tried deleting and re-connecting, the A
record for DC1 is correct on DC2. I can nslookup and choose DC1 as the DNS
server and resolve names. I can even right click on the red X, choose
properties and do a simple DNS query against the DC1 and get a PASS result.
If I add a record on DC1, it is not being replicated to DC2. The management
console works fine from DC1 to DC2, haven't tested replication. Will do that
next just to see.

A little worried, I have two Win 2008 servers on the network and I want to
add them in as domain controllers then migrate all DC functions to them on
Sunday. I'm really afraid of what will happen if I try this while DNS is
busted.
 
Ad

Advertisements

M

Meinolf Weber [MVP-DS]

Hello prmolina,

Please post an unedited ipconfig /all from both servers. Additional run dcdiag
/v, netdiag /v and repadmin /showreps to check for errors. If some exist
please post the complete output here. If you have problems to get the complete
outputs use this:

dcdiag /v >c:\dcdiag.log

So you have the complete output in the textfile and can copy it here. This
will also work with the other commands.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
P

prmolina

Thanks for the offer to help, I'm running these and cleaning them for inet
posting. Already see some problems but not sure what to do about them.

You will notice:
This network was set up a long time ago using routable ip addresses. I know
its a problem and am in the process of changing all of these to
non-routable, along with some major other overhauls.
 
P

prmolina

Here is the information from the first server, DC1, that you requested. I
tried to bring it down to just the relevant entries for you. Also, I did
scrub it of names for posting.

DC2:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : dc2
Primary DNS Suffix . . . . . . . : domname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domname.com

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 Gigabit Server
Adapter
Physical Address. . . . . . . . . : 00-30-48-77-7E-D4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.100.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.9.200.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.9.200.203
DNS Servers . . . . . . . . . . . : 192.9.200.107
192.9.200.112
Primary WINS Server . . . . . . . : 192.9.200.107
DC1:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : DC1
Primary DNS Suffix . . . . . . . : domname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domname.com

Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD PCNet
Adapter

Physical Address. . . . . . . . . : 00-0C-29-62-48-F3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.9.200.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.9.200.203
DNS Servers . . . . . . . . . . . : 192.9.200.107
192.9.200.112

PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.9.200.156
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1

DC1 dcdiag /v errors
Starting test: Replications
* Replications Check
[Replications Check,DC1] Inbound replication is disabled.
To correct, run "repadmin /options DC1 -DISABLE_INBOUND_REPL"
[Replications Check,DC1] Outbound replication is disabled.
To correct, run "repadmin /options DC1 -DISABLE_OUTBOUND_REPL"
......................... DC1 failed test Replications

Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
TrkWks Service is stopped on [DC1]
* Checking Service: TrkSvr
TrkSvr Service is stopped on [DC1]
* Checking Service: NETLOGON
NETLOGON Service is paused on [DC1]
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... DC1 failed test Services

Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... DC1 passed test frssysvol

DC1 dcdiag Ommited test:
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels

DC1 Netdiag errors:

Local Area Connection 3
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
{DDC8BD2F-3ECD-4899-BCEF-EB073AD0D455}
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
Testing DNS
[FATAL]: The DNS registration for 'DC1.domname.com' is incorrect
on all DNS servers.
[WARNING] The DNS entries for this DC are not registered correctly on DNS
server '192.9.200.112'. Please wait for 30

minutes for DNS server replication.
NetBT name test. . . . . . : Passed
(BUT HAD THIS):
[WARNING] At least one of the <00> 'WorkStation Service', <03> 'Messenger
Service', <20> 'WINS' names is missing
WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this adapter.
There are no WINS servers configured for this interface.
DNS test . . . . . . . . . . . . . : Failed
Interface {9CAB2EDC-B3B2-46BD-9BEF-A81A2BA6C811}
DNS Domain:
DNS Servers: 192.9.200.107 192.9.200.112
IP Address: 192.9.200.107
Expected registration with PDN (primary DNS domain name):
Hostname: DC1.domname.com.
Authoritative zone: domname.com.
Primary DNS server: DC1.domname.com 192.9.200.156
Authoritative NS:192.9.200.156 192.9.200.107 192.9.200.112
Interface {DDC8BD2F-3ECD-4899-BCEF-EB073AD0D455}
DNS Domain:
DNS Servers: 127.0.0.1
IP Address: 192.9.200.156
The DNS registration is disabled for this interface
Verify DNS registration:
Name: DC1.domname.com
Expected IP: 192.9.200.107
Server 192.9.200.156: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
Server 192.9.200.107: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
Server 192.9.200.112: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
[FATAL]: The DNS registration for 'DC1.domname.com' is
incorrect on all DNS servers.
Check the DNS registration for DCs entries on DNS server '192.9.200.107'
The Record is different on DNS server '192.9.200.107'.
DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.9.200.107', no need to
re-register.
The record on your DC is:
DNS NAME = gc._msdcs.domname.com.
DNS DATA =
A 192.9.200.156

The record on DNS server 192.9.200.112 is:
DNS NAME = gc._msdcs.domname.com
DNS DATA =
A 192.9.200.112
A 192.9.200.107
A 192.9.200.130
A 192.168.100.11
A 192.168.10.5
A 192.168.20.20
+------------------------------------------------------+

[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.9.200.112'. Please wait

for 30 minutes for DNS server replication.
Check the DNS registration for DCs entries on DNS server '127.0.0.1'
The Record is different on DNS server '127.0.0.1'.
DNS server has more than one entries for this name, usually this means there
are multiple DCs for this domain.
Your DC entry is one of them on DNS server '127.0.0.1', no need to
re-register.

Trust relationship test. . . . . . : Skipped

REPADMIN:
Default-First-Site-Name\DC1
DSA Options : IS_GC DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL
objectGuid : 62007dff-1014-40a1-a0d7-69eeea27a56b
invocationID: 62007dff-1014-40a1-a0d7-69eeea27a56b

==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:49.20 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 00:47.52.
271 consecutive failure(s).

CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:52.21 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 01:06.08.
1345 consecutive failure(s).

DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:59.23 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 01:16.58.
2374 consecutive failure(s).

==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a

CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a

DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
 
P

prmolina

From the info you got me to pull, it looks like this started on 5/31. No
surprise, that was the day I virtualized DC1 (DC2 still on its hardware).
When it first booted, it gave itself a DHCP address. I removed that and
replaced it with the addresses it had previously. Looks like the process
killed replication as well.
 
M

Meinolf Weber [MVP-DS]

Hello prmolina,

The biggest problem are the multiple ip addresses on DC1, why is this?

Next problem on DC2, it is configured a RRAS server. Both of this configurations,
multihoming and RRAS, create lots of problems in a domain.

See here about, even it is a long article:
-----------------------------------------------------------------------
1. Domain Controllers should not be multi-homed
2. Being a VPN Server and even simply running RRAS makes it multi-homed.
3. DNS,..even just all by itself, is better on a single homed machine.
4. Domain Controllers with the PDF Role are automatically Domain Master
Browser. Master Browsers should not be multi-homed

272294 - Active Directory Communication Fails on Multihomed Domain Controllers
http://support.microsoft.com/default.aspx?scid=kb;en-us;272294

191611 - Symptoms of Multihomed Browsers
http://support.microsoft.com/default.aspx?scid=kb;EN-US;191611

Phillip Windell
www.wandtv.com

The views expressed, are my own and not those of my employer, or Microsoft,
or anyone else associated with me, including my cats. -----------------------------------------------------


See also:

Multihomed DCs, DNS, RRAS servers.
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++
Below are the manual steps in more detail, which I had outlined in the above
paragraph:

Honestly, multi-homed DCs are not recommended because of the associated issues
that can occur, as you've encountered. We usually recommend purchasing an
inexpensive Linksys, DLink, etc, Cable/DSL router to perform NAT for you,
take out the extra NIC off the DC, but still let the DC handle DHCP (and
not the router).

Little background on AD and DNS:
First, just to get this out of the way, if you have your ISP's DNS addresses
in your IP configuration (DCs and clients), they need to be REMOVED.

If the ISP's DNS is in there, this will cause additional problems.

Also, AD registers certain records in DNS in the form of SRV records that
signify AD's resource and service locations. When there are multiple NICs,
each NIC registers. IF a client, or another DC queries DNS for this DC, it
may get the wrong record. One factor controlling this is Round Robin. If
a DC or client on another subnet that the DC is not configured on queries
for it, Round Robin will kick in offering one or the other. If the wrong
one gets offered, it may not have a route to it. On the other hand, Subnetmask
Priortization will ensure a querying client will get an IP that corresponds
to the subnet it's on, which will work. To insure everything works, stick
with one NIC.

Since this DC is multi-homed, it requires additional configuration to prevent
the public interface addresses from being registered in DNS. This creates
a problem for internal clients locating AD to authenticate and find other
services and resources such as the Global Catalog, file sharing and the SYSVOL
DFS share and can cause GPO errors with Userenv 1000 events to be logged,
authenticating to shares and printers, logging on takes forever, among numerous
other issues.

But if you like, there are some registry changes to eliminate the registration
of the external NIC. Here's the whole list of manual steps to follow.

But believe me, it's much easier to just get a separate NAT device or multihome
a non-DC then having to alter the DC. - Good luck!

1. Insure that all the NICS only point to your internal DNS server(s) only
and none others, such as your ISP's DNS servers' IP addresses.

2. In Network & Dialup properties, Advanced Menu item, Advanced Settings,
move the internal NIC (the network that AD is on) to the top of the binding
order (top of the list).

3. Disable the ability for the outer NIC to register. The procedure, as
mentioned, involves identifying the outer NIC's GUID number. This link will
show you how:
246804 - How to Enable-Disable Windows 2000 Dynamic DNS Registrations (per
NIC too):
http://support.microsoft.com/?id=246804

4. Disable NetBIOS on the outside NIC. That is performed by choosing to
disable NetBIOS in IP Properties, Advanced, and you will find that under the
"WINS" tab. You may want to look at step #3 in the article to show you how
to disable NetBIOS on the RRAS interfaces if this is a RRAS server.
296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Note: A standard Windows service, called the "Browser service", provides
the list of machines, workgroup and domain names that you see in "My Network
Places" (or the legacy term "Network Neighborhood"). The Browser service
relies on the NetBIOS service. One major requirement of NetBIOS service is
a machine can only have one name to one IP address. It's sort of a fingerprint.
You can't have two brothers named Darrell. A multihomed machine will cause
duplicate name errors on itself because Windows sees itself with the same
name in the Browse List (My Network Places), but with different IPs. You
can only have one, hence the error generated.

5. Disable the "File and Print Service" and disable the "MS Client Service"
on the outer NIC. That is done in NIC properties by unchecking the respective
service under the general properties page. If you need these services on
the outside NIC (which is unlikely), which allow other machines to connect
to your machine for accessing resource on your machine (shared folders, printers,
etc.), then you will probably need to keep them enabled.

6. Uncheck "Register this connection" under IP properties, Advanced settings,
"DNS" tab.

7. Delete the outer NIC IP address, disable Netlogon registration, and manually
create the required records

a. In DNS under the zone name, (your DNS domain name), delete the outer NIC's
IP references for the "LdapIpAddress". If this is a GC, you will need to
delete the GC IP record as well (the "GcIpAddress"). To do that, in the DNS
console, under the zone name, you will see the _msdcs folder. Under that,
you will see the _gc folder. To the right, you will see the IP address referencing
the GC address. That is called the GcIpAddress. Delete the IP addresses referencing
the outer NIC.

i. To stop these two records from registering that information,
use the steps provided in the links below:
Private Network Interfaces on a Domain Controller Are Registered in
DNShttp://support.microsoft.com/?id=295328

ii. The one section of the article that disables these records is done with
this registry entry:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters
(Create this Multi-String Value under it):
Registry value: DnsAvoidRegisterRecords
Data type: REG_MULTI_SZ
Values: LdapIpAddress
GcIpAddress

iii. Here is more information on these and other Netlogon Service records:

Restrict the DNS SRV resource records updated by the Netlogon service

[including GC]:

http://www.microsoft.com/technet/tr...proddocs/standard/sag_dns_pro_no_rr_in_ad.asp

b. Then you will need to manually create these two records in DNS with the
IP addresses that you need for the DC. To create the

LdapIpAddress, create a new host under the domain, but leave the "hostname"
field blank, and provide the internal IP of the DC, which results in a
record that looks like:
(same as parent) A 192.168.5.200 (192.168.5.200 is used for illustrative
purposes)

i. You need to also manually create the GcIpAddress as well, if this is a
GC. That would be under the _msdcs._gc SRV record under the zone. It is created
in the same fashion as the LdapIpAddress mentioned above.

8. In the DNS console, right click the server name, choose properties, then
under the "Interfaces" tab, force it only to listen to the internal NIC's
IP address, and not the IP address of the outer NIC.

9. Since this is also a DNS server, the IPs from all NICs will register,
even if you tell it not to in the NIC properties. See this to show you how
to stop that behavior (this procedure is for Windows 2000, but will also
work for Windows 2003):
275554 - The Host's A Record Is Registered in DNS After You Choose Not to
Register the Connection's Address:
http://support.microsoft.com/?id=275554

10. If you haven't done so, configure a forwarder. You can use 4.2.2.2 if
not sure which DNS to forward to until you've got the DNS address of your
ISP.
How to set a forwarder? Good question. Depending on your operating
system,choose one of the following articles:

300202 - HOW TO: Configure DNS for Internet Access in Windows 2000 http://support.microsoft.com/?id=300202&FR=1

323380 - HOW TO: Configure DNS for Internet Access in Windows Server 2003
(How to configure a forwarder):
http://support.microsoft.com/d/id?=323380

Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

<==*** Some additional reading ***==>
More links to read up and understand what is going on:

292822 - Name Resolution and Connectivity Issues on Windows 2000 Domain
Controller with Routing and Remote Access and DNS Insta {DNS and RRAS and
unwanted IPs registering]:
http://support.microsoft.com/?id=292822

Active Directory communication fails on multihomed domain controllers http://support.microsoft.com/kb/272294

246804 - How to enable or disable DNS updates in Windows 2000 and in Windows
Server 2003
http://support.microsoft.com/?id=246804

295328 - Private Network Interfaces on a Domain Controller Are Registered in
DNS
[also shows DnsAvoidRegisterRecords LdapIpAddress to avoid reg sameasparent
private IP]:
http://support.microsoft.com/?id=295328

306602 - How to Optimize the Location of a DC or GC That Resides Outside of
a Client's
Site [Includes info LdapIpAddress and GcIpAddress information and the SRV
mnemonic values]:
http://support.microsoft.com/?id=306602

825036 - Best practices for DNS client settings in Windows 2000 Server and
in Windows Server 2003 (including how-to configure a forwarder): http://support.microsoft.com/default.aspx?scid=kb;en-us;825036

291382 - Frequently asked questions about Windows 2000 DNS and Windows
Server 2003 DNS
http://support.microsoft.com/?id=291382

296379 - How to Disable NetBIOS on an Incoming Remote Access Interface
[Registry Entry]:
http://support.microsoft.com/?id=296379

Rid Pool Errors and other mutlhomed DC errors, and how to configure a multihomed
DC, Ace Fekay, 24 Feb 2006 http://www.ureader.com/message/3244572.aspx

_________________________ +++++++++++++++++++++++++++++++++++++++++++++++++++++++
+++++++++++++++++++++++++++++++++++++++++++++++++++++++ +++++++++++++++++++++++++++++++++++++++++++++++++++++++

--
Regards,
Ace


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 MVP - Directory Services
Microsoft Certified Trainer

Infinite Diversities in Infinite Combinations

Having difficulty reading or finding responses to your post?
Instead of the website you're using, try using OEx (Outlook Express
or any other newsreader), and configure a news account, pointing to
news.microsoft.com. Anonymous access. It's free - no username or password
required nor do you need a Newsgroup Usenet account with your ISP. It
connects directly to the Microsoft Public Newsgroups. OEx allows you
o easily find, track threads, cross-post, sort by date, poster's name,
watched threads or subject. It's easy:

How to Configure OEx for Internet News
http://support.microsoft.com/?id=171164


Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm

Here is the information from the first server, DC1, that you
requested. I tried to bring it down to just the relevant entries for
you. Also, I did scrub it of names for posting.

DC2:
Windows 2000 IP Configuration
Host Name . . . . . . . . . . . . : dc2
Primary DNS Suffix . . . . . . . : domname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domname.com
Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 Gigabit
Server
Adapter
Physical Address. . . . . . . . . : 00-30-48-77-7E-D4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.10.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.100.11
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.9.200.112
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.9.200.203
DNS Servers . . . . . . . . . . . : 192.9.200.107
192.9.200.112
Primary WINS Server . . . . . . . : 192.9.200.107
DC1:
Windows 2000 IP Configuration

Host Name . . . . . . . . . . . . : DC1
Primary DNS Suffix . . . . . . . : domname.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domname.com
Ethernet adapter Local Area Connection 3:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : VMware Accelerated AMD
PCNet
Adapter
Physical Address. . . . . . . . . : 00-0C-29-62-48-F3
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.9.200.107
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.9.200.203
DNS Servers . . . . . . . . . . . : 192.9.200.107
192.9.200.112
PPP adapter RAS Server (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.9.200.156
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 127.0.0.1
DC1 dcdiag /v errors
Starting test: Replications
* Replications Check
[Replications Check,DC1] Inbound replication is disabled.
To correct, run "repadmin /options DC1 -DISABLE_INBOUND_REPL"
[Replications Check,DC1] Outbound replication is disabled.
To correct, run "repadmin /options DC1 -DISABLE_OUTBOUND_REPL"
......................... DC1 failed test Replications
Starting test: Services
* Checking Service: Dnscache
* Checking Service: NtFrs
* Checking Service: IsmServ
* Checking Service: kdc
* Checking Service: SamSs
* Checking Service: LanmanServer
* Checking Service: LanmanWorkstation
* Checking Service: RpcSs
* Checking Service: RPCLOCATOR
* Checking Service: w32time
* Checking Service: TrkWks
TrkWks Service is stopped on [DC1]
* Checking Service: TrkSvr
TrkSvr Service is stopped on [DC1]
* Checking Service: NETLOGON
NETLOGON Service is paused on [DC1]
* Checking Service: Dnscache
* Checking Service: NtFrs
......................... DC1 failed test Services
Starting test: frssysvol
* The File Replication Service Event log test
Error: No record of File Replication System, SYSVOL started.
The Active Directory may be prevented from starting.
......................... DC1 passed test frssysvol
DC1 dcdiag Ommited test:
Test omitted by user request: Topology
Test omitted by user request: CutoffServers
Test omitted by user request: OutboundSecureChannels
DC1 Netdiag errors:

Local Area Connection 3
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this
adapter.
{DDC8BD2F-3ECD-4899-BCEF-EB073AD0D455}
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this
adapter.
Testing DNS
[FATAL]: The DNS registration for 'DC1.domname.com' is
incorrect
on all DNS servers.
[WARNING] The DNS entries for this DC are not registered correctly on
DNS server '192.9.200.112'. Please wait for 30

minutes for DNS server replication.
NetBT name test. . . . . . : Passed
(BUT HAD THIS):
[WARNING] At least one of the <00> 'WorkStation Service', <03>
'Messenger
Service', <20> 'WINS' names is missing
WINS service test. . . . . : Skipped
There is no primary WINS server defined for this adapter.
There is no secondary WINS server defined for this
adapter.
There are no WINS servers configured for this interface.
DNS test . . . . . . . . . . . . . : Failed
Interface {9CAB2EDC-B3B2-46BD-9BEF-A81A2BA6C811}
DNS Domain:
DNS Servers: 192.9.200.107 192.9.200.112
IP Address: 192.9.200.107
Expected registration with PDN (primary DNS domain name):
Hostname: DC1.domname.com.
Authoritative zone: domname.com.
Primary DNS server: DC1.domname.com 192.9.200.156
Authoritative NS:192.9.200.156 192.9.200.107 192.9.200.112
Interface {DDC8BD2F-3ECD-4899-BCEF-EB073AD0D455}
DNS Domain:
DNS Servers: 127.0.0.1
IP Address: 192.9.200.156
The DNS registration is disabled for this interface
Verify DNS registration:
Name: DC1.domname.com
Expected IP: 192.9.200.107
Server 192.9.200.156: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
Server 192.9.200.107: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
Server 192.9.200.112: ERROR_NO_MATCH
Wrong IP in DNS: 192.9.200.156
[FATAL]: The DNS registration for 'DC1.domname.com' is
incorrect on all DNS servers.
Check the DNS registration for DCs entries on DNS server
'192.9.200.107'
The Record is different on DNS server '192.9.200.107'.
DNS server has more than one entries for this name, usually this means
there
are multiple DCs for this domain.
Your DC entry is one of them on DNS server '192.9.200.107', no need to
re-register.
The record on your DC is:
DNS NAME = gc._msdcs.domname.com.
DNS DATA =
A 192.9.200.156
The record on DNS server 192.9.200.112 is:
DNS NAME = gc._msdcs.domname.com
DNS DATA =
A 192.9.200.112
A 192.9.200.107
A 192.9.200.130
A 192.168.100.11
A 192.168.10.5
A 192.168.20.20
+------------------------------------------------------+
[WARNING] The DNS entries for this DC are not registered correctly
on DNS server '192.9.200.112'. Please wait

for 30 minutes for DNS server replication.
Check the DNS registration for DCs entries on DNS server '127.0.0.1'
The Record is different on DNS server '127.0.0.1'.
DNS server has more than one entries for this name, usually this means
there
are multiple DCs for this domain.
Your DC entry is one of them on DNS server '127.0.0.1', no need to
re-register.
Trust relationship test. . . . . . : Skipped

REPADMIN:
Default-First-Site-Name\DC1
DSA Options : IS_GC DISABLE_INBOUND_REPL DISABLE_OUTBOUND_REPL
objectGuid : 62007dff-1014-40a1-a0d7-69eeea27a56b
invocationID: 62007dff-1014-40a1-a0d7-69eeea27a56b
==== INBOUND NEIGHBORS ======================================

CN=Schema,CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:49.20 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 00:47.52.
271 consecutive failure(s).
CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:52.21 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 01:06.08.
1345 consecutive failure(s).
DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
Last attempt @ 2009-06-11 15:59.23 failed, result 8457:
The destination server is currently rejecting replication
requests.
Last success @ 2009-05-31 01:16.58.
2374 consecutive failure(s).
==== OUTBOUND NEIGHBORS FOR CHANGE NOTIFICATIONS ============

CN=Schema,CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
CN=Configuration,DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
DC=domname,DC=com
Default-First-Site-Name\DC2 via RPC
objectGuid: 6b2f2ce8-47bd-425f-919c-2adb3d539a0a
 
Ad

Advertisements

M

Meinolf Weber [MVP-DS]

Hello prmolina,

Virtualizing a running DC is not the best solution, if you think about virtualize
them, you should better demote the server, virtualize it and promote it again.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 
P

prmolina

The Windows 2008 servers will be single homed, one physical one virtual,
purpose built to just be Domain Controllers. They are in place now, one is
joined to the domain the other will be tomorrow. Howver, I'm afraid to run
adprep on a domain that has replication broken. Do you think I can run
repadmin /options -DISABLE_OUTBOUND_REPL without running the whole train off
the tracks, then continue on to get this domain moved?

RRAS was on DC1; but that can be dumped very soon: I just finished putting
in vpn to the firewall on the edge of the network, so that is all done as
soon as the local admin gets everyone moved to the client.
I think they put in the .156 address when they put in the RRAS. I'm not
sure why, but it worked for a long time and I was afraid to touch it until I
had the green light to completely rebuild the network.
DC1 and DC2 also have other roles jammed onto them which will limit my
ability to just yank them off the network. However, I'm hoping I will at
least be able to demote them after I get the two new servers in there as
W2K domain compatible DCs.
 
A

Ace Fekay [Microsoft Certified Trainer]

prmolina said:
The Windows 2008 servers will be single homed, one physical one virtual,
purpose built to just be Domain Controllers. They are in place now, one
is joined to the domain the other will be tomorrow. Howver, I'm afraid to
run adprep on a domain that has replication broken. Do you think I can
run repadmin /options -DISABLE_OUTBOUND_REPL without running the whole
train off the tracks, then continue on to get this domain moved?

RRAS was on DC1; but that can be dumped very soon: I just finished
putting in vpn to the firewall on the edge of the network, so that is all
done as soon as the local admin gets everyone moved to the client.
I think they put in the .156 address when they put in the RRAS. I'm not
sure why, but it worked for a long time and I was afraid to touch it until
I had the green light to completely rebuild the network.
DC1 and DC2 also have other roles jammed onto them which will limit my
ability to just yank them off the network. However, I'm hoping I will at
least be able to demote them after I get the two new servers in there as
W2K domain compatible DCs.


I wouldn't run adprep or introduce any new DCs into this network until this
is cleaned up.

Why does DC1 have all those IP addresses? Can you eliminate all but one?

Also, good thing you can remove RRAS off of DC2. Between mutiple IPs and
RRAS, they are surely to cause problems with AD.

--
Ace

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

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSA Messaging, MCT
Microsoft Certified Trainer
(e-mail address removed)

For urgent issues, you may want to contact Microsoft PSS directly. Please
check http://support.microsoft.com for regional support phone numbers.

"Efficiency is doing things right; effectiveness is doing the right
things." - Peter F. Drucker
http://twitter.com/acefekay
 
P

prmolina

Wow, alot of helpful information here. Let me go through it a little and
try and get this straight and apply it to my situation here.....

And by the way, again, thanks for the help!



Meinolf Weber said:
Hello prmolina,

The biggest problem are the multiple ip addresses on DC1, why is this?

You got this front to back - DC2 has the multiple addrsses. No bother,
point well taken, I don't think these serve a real purpose anymore and I
will delete them after recording them just in case.
Next problem on DC2, it is configured a RRAS server. Both of this
configurations, multihoming and RRAS, create lots of problems in a domain.

Physically, only one network card in DC1 now, and the second card in DC2 has
been disabled for a while now. RRAS can be disabled very soon, and will be.
the second .156 address should go away at that point.

Once that is done will have these with a single ip and they will be inside
facing only.
Little background on AD and DNS:
First, just to get this out of the way, if you have your ISP's DNS
addresses in your IP configuration (DCs and clients), they need to be
REMOVED.

None of that, all dns pointed to the two DCs.

Since this DC is multi-homed, it requires additional configuration to
prevent the public interface addresses from being registered in DNS. This
creates a problem for internal clients locating AD to authenticate and
find other services and resources such as the Global Catalog, file sharing
and the SYSVOL DFS share and can cause GPO errors with Userenv 1000 events
to be logged, authenticating to shares and printers, logging on takes
forever, among numerous other issues.

So far, haven't noticed a problem with clients; when I delete all extra ip's
should take care of confusion. I'll re-run repadmin to make sure
registrations work ok.
But believe me, it's much easier to just get a separate NAT device or
multihome a non-DC then having to alter the DC. - Good luck!
We are using a NAT device. Were using the RRAS to terminate VPNs but thats
it, not route to the internet.
a. In DNS under the zone name, (your DNS domain name), delete the outer
NIC's IP references for the "LdapIpAddress". If this is a GC, you will
need to delete the GC IP record as well (the "GcIpAddress"). To do that,
in the DNS console, under the zone name, you will see the _msdcs folder.
Under that, you will see the _gc folder. To the right, you will see the IP
address referencing the GC address. That is called the GcIpAddress. Delete
the IP addresses referencing the outer NIC.
I'll make sure this is straight.

to your post?
Best regards

Meinolf Weber

Thanks, Meinolf. This will help.
 
P

prmolina

I wouldn't run adprep or introduce any new DCs into this network until
this is cleaned up.
I think you are (darn) right about that!
Why does DC1 have all those IP addresses? Can you eliminate all but one?
Somebody was doing something at some time. The network has alot of history.
I will be dumping the extras.
Also, good thing you can remove RRAS off of DC2. Between mutiple IPs and
RRAS, they are surely to cause problems with AD.
Yep, but implementation is mostly out of my hands; I requested they hurry
along on that.One thing, to get replication back running I was going to run Q321153:
repadmin /options -DISABLE_OUTBOUND_REPL
This was also suggested in the repadnmin /showreps output. Do you have any
experience with that, think it will help out?Thanks Ace!
 
Ad

Advertisements

A

Ace Fekay [Microsoft Certified Trainer]

prmolina said:
I think you are (darn) right about that!
Somebody was doing something at some time. The network has alot of
history. I will be dumping the extras.
Yep, but implementation is mostly out of my hands; I requested they hurry
along on that.One thing, to get replication back running I was going to run Q321153:
repadmin /options -DISABLE_OUTBOUND_REPL
This was also suggested in the repadnmin /showreps output. Do you have
any experience with that, think it will help out?Thanks Ace!


The sooner those IPs are out, and RRAS is disabled, the sooner you can get
this back up and running. In it's current state, it may continue to not be
able to replicate or AD to communicate using RPC, hence why you're seeing
the red X. This is because there are multiple entries for both DCs in DNS,
including the RRAS interfaces, which make it worse, because if another
machine resolves DC1 to one of the RRAS IPs, or if DC2 resolves DC1 to
192.168.10.5, it won;t have a route to it. Therefor, it can;t connect to it,
which are the LdapIpAddress and the GcIpAddress records.

And disabling replication ain't gonna help. Both DC's config did a good job
of that already!

Curious, what is in the event viewers of both machines?

After removing RRAS and the additional IPs, perform the following on each
DC:
Set DNS to itself as the first entry, then the other as the second.
Delete system32\config\netlogon.dns and netlogon.bak files
In a cmd:
ipconfig /registerdns
net stop netlogon
net start netlogon

Ace
 
Ad

Advertisements

M

Meinolf Weber [MVP-DS]

Hello prmolina,

As Ace already stated, before doing anything with new machines/OS get the
running environment clean and replicating again. So follow Ace's advice first
and then we can go on to the new OS, not earlier.

Also the article can help but fix the basic network and DC configuration
first before trying to fix replication problems.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top