DNS problem?

  • Thread starter Thread starter Dennis Capulong
  • Start date Start date
D

Dennis Capulong

Hi guys,

I have a Windows Server 2003 machine on a WORKGROUP env't.
I want it to be the child domain (CHILD.DOMAIN.COM) of our existing
domain(DOMAIN.COM).
I am doing it over our VPN network.
DNS registration support has been verified which is ok, the test for dynamic
DNS update support is successful, BUT while replicating the schema directory
partion, and all the stuffs it must perform, the result is "The remote
procedure call failed and did not execute." I checked the log and it says
"Error value 1727: The remote procedure call failed and did not execute."

Any idea on how to solve this issue? Thanks.


Regards,
Dennis Capulong
 
Dennis Capulong said:
Hi guys,

I have a Windows Server 2003 machine on a WORKGROUP env't.
I want it to be the child domain (CHILD.DOMAIN.COM) of our existing
domain(DOMAIN.COM).
I am doing it over our VPN network.
DNS registration support has been verified which is ok, the test for
dynamic DNS update support is successful, BUT while replicating the
schema directory partion, and all the stuffs it must perform, the
result is "The remote procedure call failed and did not execute." I
checked the log and it says "Error value 1727: The remote procedure
call failed and did not execute."

Any idea on how to solve this issue? Thanks.
Click to expand...

What is the exact event ID in the event log?
 
In
Dennis Capulong said:
Hi guys,

I have a Windows Server 2003 machine on a WORKGROUP env't.
I want it to be the child domain (CHILD.DOMAIN.COM) of our existing
domain(DOMAIN.COM).
I am doing it over our VPN network.
DNS registration support has been verified which is ok, the test for
dynamic DNS update support is successful, BUT while replicating the
schema directory partion, and all the stuffs it must perform, the
result is "The remote procedure call failed and did not execute." I
checked the log and it says "Error value 1727: The remote procedure
call failed and did not execute."
Any idea on how to solve this issue? Thanks.


Regards,
Dennis Capulong
Click to expand...

Sounds like to me there's either a firewall rule blocking necessary traffic.
Keep in mind there are about 30 ports for domain controller communication.

If that's not it, then it tells me the DNS infrastructure is not configured
properly. If this is the possible case, and there are no firewall rules,
please post an ipconfig /all of the server you are trying to promote and
from the server on the other end of the VPN to better assist you. We'll need
specifics, otherwise it will be guess work.

--
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
Infinite Diversities in Infinite Combinations.
=================================
 
Back
Top