DNS / FRS / AD problems

  • Thread starter Thread starter microsoft
  • Start date Start date
M

microsoft

Hello,

Thanks in advance for any help... i know this problem is specific to my
forest... but see what you think.

i have 3 locations... the operations master is located here in pittsburgh...
my wheeling wv location is fine... we have a dc there with it properly setup
in ad sites... i have the same setup in philly pa, where i have a dc and it
is setup in ad sites.

now, changes made in pittsburgh push fine to wheeling, but not philly... on
the philly end it can see all my servers, map drives and run apps from
pittsburgh... but ad will not work. i get event ids 1311, 1265, 13562,
13508... i've researched them and have found write ups on dfs replication,
ntds settings and so on.

the solution is to dcpromo the philly server and revamp it from scratch..
however, i'd like to hear opinions about the problem... anything i can do to
get the changes to push through?

the main error i get with replicating ad on the philly side is "a naming
context is incorrect" or something along those lines... regarding frs and
dfs problems... is there anything to test remotely to push changes through?

i'm thinking the main problem is DNS related... i'll be checking in on that
today... please shoot me an email with any suggestions

(e-mail address removed)

thanks - Sonny
 
microsoft said:
Hello,

Thanks in advance for any help... i know this problem is specific to my
forest... but see what you think.

i have 3 locations... the operations master is located here in pittsburgh...
my wheeling wv location is fine... we have a dc there with it properly setup
in ad sites... i have the same setup in philly pa, where i have a dc and it
is setup in ad sites.

now, changes made in pittsburgh push fine to wheeling, but not philly... on
the philly end it can see all my servers, map drives and run apps from
pittsburgh... but ad will not work. i get event ids 1311, 1265, 13562,
13508... i've researched them and have found write ups on dfs replication,
ntds settings and so on.

the solution is to dcpromo the philly server and revamp it from scratch..
however, i'd like to hear opinions about the problem... anything i can do to
get the changes to push through?

the main error i get with replicating ad on the philly side is "a naming
context is incorrect" or something along those lines... regarding frs and
dfs problems... is there anything to test remotely to push changes through?

i'm thinking the main problem is DNS related... i'll be checking in on that
today... please shoot me an email with any suggestions

(e-mail address removed)

thanks - Sonny
Click to expand...

These can be possibly related to either firewall settings and/or incorrect
DNS addresses. If we can see an ipconfig /all from a DC in both locations,
that can really be helpful.

btw- I'm actually right outside of Philly...

--
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
thanks man... why don't you take a drive into philly and give my server a
good kick?

anyway, i'm running vpn through watchgaurd firewalls... it's working
properly and my 2 remote sites are mirrored *in respect to networking* ...
it just seems that one server will not update and still gives naming context
errors...

something is corrupt, it won't pull DNS or AD changes... and when i search
my domain it returns 2 servers that i took down last week... so it's running
on cached settings...

keep the replies coming...
 
In
microsoft said:
thanks man... why don't you take a drive into philly and give my
server a good kick?

anyway, i'm running vpn through watchgaurd firewalls... it's working
properly and my 2 remote sites are mirrored *in respect to
networking* ... it just seems that one server will not update and
still gives naming context errors...

something is corrupt, it won't pull DNS or AD changes... and when i
search my domain it returns 2 servers that i took down last week...
so it's running on cached settings...

keep the replies coming...
Click to expand...

Sure, I'll kick it for you! Sometimes that actually fixes it (like an old TV
set!).

If you have references to two old servers, then the only thing I can think
of is that they didn't get demoted properly out of the domain. We'll need to
run a Metadata Cleanup in AD to remove those references:

HOW TO Remove Data in Active Directory After an Unsuccessful Domain
Controller Demotion Q216498:
http://support.microsoft.com/?id=216498

216364 - Domain Controller Server Object Not Be Removed After Demotion [ADUC
or NTDSUTIL]:
http://support.microsoft.com/?id=216364

As for the FRS issues, if they're not related to AD trying to replicate to
the missing DCs, I would look into the watchguards to insure that there is
no hinderance whatsover with the firewall rules. AD requires about 30 ports
open for replication and other communication. Check it out and see what you
come up with...



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top