Event ID 1265.
"... The DSA operation is unable to proceed because of a
DNS lookup failure..."
I can do an nslookup and a ping from each machine to the
other.
Brett
-----Original Message-----
I'll add that I'm expecting the primary DC to replicate
from the new DC. We
have to determine why the KCC hasn't created a
connection object for the
primary DC to pull from the new DC. I'm hoping there
will be a message in
the eventlog explaining why.
Jason
--
This posting is provided "AS IS" with no warranties, and
confers no rights.
Use of included script samples are subject to the terms
specified at
http://www.microsoft.com/info/cpyright.htm
"Jason Robarts [MSFT]" <
[email protected]>
wrote in message
Do you have any other DCs? On the primary DC do you
have any errors in
the
Directory Service Eventlog?
--
This posting is provided "AS IS" with no warranties,
and confers no
rights.
Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm
message
There are no erros upon running repadmin /showreps on
either server. The primary dc shows no INBOUND
NEIGHBORS
but does show the new dc as an OUTBOUND NEIGHBOR FOR
CHANGE NOTIFICATIONS.
The new DC doesn't show any OUTBOUND NEIGHBORS FOR
CHANGE
NOTIFICATIONS but does show the primary dc as an
INBOUND
NEIGHBOR.
Brett
-----Original Message-----
When you run repadmin /showrepl (/showreps on some
versions of repadmin) on
the new DC and its replication partner do you get
any
errors? It could also
be the 3rd part - the AD replication item - in the
event
log message.
Jason
--
This posting is provided "AS IS" with no
warranties, and
confers no rights.
Use of included script samples are subject to the
terms
specified at
http://www.microsoft.com/info/cpyright.htm
in
message
Have already tried it - but went ahead and tried
again.
Didn't work.
Brett
-----Original Message-----
Hey Brett-
Try the following article:
http://support.microsoft.com/default.aspx?
scid=kb;en-
us;285923
--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000
*This posting is provided "AS IS" with no
warranties,
and confers no
rights.
"Brett" <
[email protected]>
wrote in
message
It does not.
-----Original Message-----
You mentioned you upgraded this server
(dcpromo).
By
chance does it contain
any LMHOSTS\HOSTS entries?
--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000
*This posting is provided "AS IS" with no
warranties,
and confers no
rights.
message
[email protected]...
I thought name resolution too, however - I
have
the
correct A and PTR and SRV records in DNS
and the
new DC
has the IP of the primary DC listed as it's
primary
DNS
server.
-----Original Message-----
Hi Brett-
Sounds like name resolution. You have A
and PTR
records
registered in DNS?
Does your new server have the correct DNS
server
addresses listed in it's IP
Stack?
--
Thanks,
Richard Moreno
MCSE NT4\2000, MCSA 2000
*This posting is provided "AS IS" with no
warranties,
and confers no
rights.
in
message
[email protected]...
I have a Win2000 Active Directory
Domain. I've
recently
added a second DC through dcpromo. The
promotion
worked
great. However, upon reboot the new DC
has
trouble
enabling the File Replication Service
with the
Primary
DC.
From the new DC I can ping and do an
nslookup
to
the
primary DC without a problem.
Any clues?
The event viewer shows the following
warning:
Source: NtFrs
Category: None
Type: Warning
Event ID: 13508
Description: The File Replication
Service is
having
trouble enabling replication from
DATASTOR to
PC_DCON
for
c:\winnt\sysvol\domain using the DNS name
datastor.PRODUCTION. FRS will keep
trying.
Following
are
some of the reasons you would see this
warning.
[1] FRS cannot correctly resolve the DNS
name
datastor.PRODUCTION from this computer.
[2] FRS is not running on
datastor.PRODUCTION.
[3] The toplogy information in Active
Directory
for
this
replica has not yet replicated to all the
Domain
Controllers.
.
.
.
.
.
