Re: BDC DCDIAG Problem
- From: Paul <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Sat, 18 Nov 2006 17:35:01 -0800
Sorry for delay-had to run out of town.
This DC has one NIC and it has multiple IPs because I have a hardware
firewall, 5 external IPs, and 5 websites; 4 websites are on this BDC and 1
website is on the PDC. These websites are light usage, some for employees
and the others are lightly loaded. The firewall converts the external IPs to
the internal IPs, thus the reason for the different IPs.
"second AD SITE with the same subnet as the first site? Why?"
I just set up DNS as a backup DNS server according to the MS procedure I
located on MS site. I assumed that it was correct, and for most part appears
to be. But I do not understand your question maybe, if this is a "Backup DNS
server" shouldn't it be a second AD SITE with the same subnet as the first?
It appears correct to me, but then again, this is not my forte.
I have gone through a number of tests, as directed by Robert L, and
everything seems fine. I am still checking here and there but yet not
finding what may be the cause yet. I suppose that the additional IPs could
be an issue and I will try removing them temporarily to see if that clears
the problems up.
I will post results tomorrow.
Thanks
Paul
"kj" wrote:
Hmm. I'm a little confused here..
The BDC "main" ip address is ....
Does this DC have more than one NIC?, If so why, and if not, why the
addtional IP's bound to one NIC?
made BDC a
secondary DNS server
You configured the DC as a DNS "Secondary" (Read Only zone)? If so, you
should undo this. Just have DNS installed, no need to create "anything" at
this point. Configure this server to use the other DC for DNS until
replication is completed.
Testing server: Default-First-Site-Name\2ndryDNSserver
You have a second AD SITE with the same subnet as the first site? Why?
--
/kj
"Paul" <Paul@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:92FAEE8F-18C6-47C1-9F2D-67A835431D86@xxxxxxxxxxxxxxxx
I am setting up a BDC in an SBS2003 network and have run dcpromo, made BDC
a
secondary DNS server, and have made the BDC a GC. After restart I noticed
a
warning in the File Replication Service event log.
Source: NtFrs Event ID: 13508
The File Replication Service is having trouble enabling replication
from PDC to BDC for c:\windows\sysvol\domain using the DNS name
PDCservername.domainname.local ...
Network appears to be running fine, no blazing errors to speak of, but
something needs tweaking here. Unfortunately I am not well versed in this
area and need assistance in resolution. I have attached IPConfig /all and
DCDiag.exe results below.
Any assistance is appreciated greatly.
Paul
IPConfig /all yields the following (Note that I have some IPs setup for
websites on this server, Main IP for the BDC is 192.168.16.4, PDC is
192.168.16.2, Firewall is 192.168.16.1; 1 NIC in PDC):
Windows IP Configuration
Host Name . . . . . . . . . . . . : BDC
Primary Dns Suffix . . . . . . . : domainname.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : domainname.local
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/1000 CT Network
Connection
Physical Address. . . . . . . . . : 00-12-50-60-FD-45
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.16.8
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.16.7
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.16.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.16.5
Subnet Mask . . . . . . . . . . . : 255.255.255.0
IP Address. . . . . . . . . . . . : 192.168.16.4
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.16.1
DNS Servers . . . . . . . . . . . : 192.168.16.2
Primary WINS Server . . . . . . . : 192.168.16.2
DCDiag.exe yields the following:
Domain Controller Diagnosis
Performing initial setup:
[2ndryDNSserver] Directory Binding Error -2146892976:
The system detected a possible attempt to compromise security. Please
ensure
that you can contact the server that authenticated you.
This may limit some of the tests that can be performed.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\2ndryDNSserver
Starting test: Connectivity
The host
41df6d50-a4cf-4e8f-be9c-233c1d23dafe._msdcs.domainname.loca
l could not be resolved to an
IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(41df6d50-a4cf-4e8f-be9c-233c1d23dafe._msdcs.domainname.local)
couldn't be resolved, the server name
(2ndryDNSserver.domainname.local)
resolved to the IP address (192.168.16.4) and was pingable. Check
that the IP address is registered correctly with the DNS server.
......................... 2ndryDNSserver failed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\2ndryDNSserver
Skipping all tests, because server 2ndryDNSserver is
not responding to directory service requests
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : domainname
Starting test: CrossRefValidation
......................... domainname passed test
CrossRefValidation
Starting test: CheckSDRefDom
......................... domainname passed test CheckSDRefDom
Running enterprise tests on : domainname.local
Starting test: Intersite
......................... domainname.local passed test Intersite
Starting test: FsmoCheck
[2ndryDNSserver] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
......................... domainname.local passed test FsmoCheck
- Follow-Ups:
- Re: BDC DCDIAG Problem
- From: kj
- Re: BDC DCDIAG Problem
- From: kj
- Re: BDC DCDIAG Problem
- References:
- BDC DCDIAG Problem
- From: Paul
- Re: BDC DCDIAG Problem
- From: kj
- BDC DCDIAG Problem
- Prev by Date: Re: Two computers have same IP
- Next by Date: Re: SBS hell
- Previous by thread: Re: BDC DCDIAG Problem
- Next by thread: Re: BDC DCDIAG Problem
- Index(es):
Relevant Pages
|