DNS problem?

Tech-Archive recommends: Fix windows errors by optimizing your registry



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


.



Relevant Pages

  • Child Domain
    ... I want it to be the child domain of our existing ... DNS registration support has been verified which is ok, ... The remote procedure call failed and did not execute." ...
    (microsoft.public.windows.server.active_directory)
  • Child Domain
    ... I want it to be the child domain of our existing ... DNS registration support has been verified which is ok, ... The remote procedure call failed and did not execute." ...
    (microsoft.public.win2000.active_directory)
  • RE: "The remote procedure call failed and did not execute"
    ... "The remote procedure call failed and did not execute" ... when I try to enlist an ochestration (which I've successfully evelopped ... someting similarto this hapned when confuguring the biztalk server. ...
    (microsoft.public.biztalk.server)
  • Re: DNS problem?
    ... > result is "The remote procedure call failed and did not execute." ... > checked the log and it says "Error value 1727: The remote procedure ... What is the exact event ID in the event log? ...
    (microsoft.public.win2000.dns)