Re: Errors 5790 and 5719; Domain Not Found



Hello Ace,

Thank you for the quick reply.

I have configured rpc over http following those docs :)
As my DC/GC is not on the same machine as Exchange Server, the only change i
need to do was add in the registry at
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Rpc\RpcProxy -> ValidPorts the
information neccesary to locate the GC with ports 6001, 6002 and 6004. So
the result was adding the ports for the exchange server netbios & FQDN name
and the netbios & FQDN of the DC/GC.
Then, the only change necessary on the GC was add a value at
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\NTDS\Parameters
named NSPI interface protocol sequences
with value: ncacn_http:6004 to make the GC listen on that port.

Returning to my error's 5719 and 5790 issue, we restarted the Exchange
Server and the error were not logged again and we are able to open ADU&C and
ESM. So, i really dont have a clue if the problem is related or not to
rpc/http config :)

Thanks again and if you have more comments they are very welcome :)

Daniel Abella
MCSE, MCSA, MCT



"Ace Fekay [MVP]"
<PleaseSubstituteMyActualFirstName&LastNameHere@xxxxxxxxxxx> wrote in
message news:ur1khmW9FHA.2264@xxxxxxxxxxxxxxxxxxxxxxx
> In news:u3pp4RW9FHA.2152@xxxxxxxxxxxxxxxxxxxx,
> News Microsoft <dabella@xxxxxxxxxxxxxxx> made this post, which I then
> commented about below:
>> Hello all,
>>
>> I have a single domain active directory forest (win 2003 native) with
>> a single DC.
>> Another server is an Exchange 2003.
>>
>> Today i try to open Exchange System Manager and Active Directory
>> Users and Computers and i was unable because of an error.
>> I look at the event logs and found error 5790 and 5719 stating that no
>> domain controller was found for my domain...
>>
>> Anyone has experienced this problem or have any clue about it?
>>
>> The last change we make in the servers was enable rpc proxy on the
>> Exchange Server to configure RPC over HTTP connections for Outlook...
>>
>> Thanks in advance for any comment.
>>
>> Daniel.-
>
> When opening the ESM, it doesn't talk to Exchange, but rather to AD, IIS
> and a couple of other services, most of which, AD's Configuration
> container. Not being able to open it can be contributed to DNS lookup
> issues, AD problems, or if RPC over HTTP was misconfigured, whereas it
> alters the machine's basic RPC functionality.
>
> RPC over HTTP in most cases, it designed to be on the FE server for
> outside RPC traffic to come in over HTTP. If it is on all servers, or it's
> not the FE, we can assume there will be issues, such as what you are
> experiencing, unless it is properly configured for a single server. Here's
> a few docs on how to set it up and configure it correctly:
>
> Download details Exchange 2003 RPC over HTTP Deployment Scenarios:
> http://www.microsoft.com/downloads/details.aspx?familyid=ef58395d-3710-49cf-9698-938e2bef39e8&displaylang=en
>
> How to configure RPC over HTTP on a single server in Exchange Server 2003:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;833401
>
> How to configure an RPC over HTTP topology on computers that are running
> Exchange 2003 with Service Pack 1:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;841652
>
> The Exchange Server 2003 RPC over HTTP deployment scenarios guide is
> available:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;840255
>
> Support WebCast Using Microsoft Exchange over the Internet (RPC-HTTP) with
> Microsoft Office Outlook 2003:
> http://support.microsoft.com/default.aspx?scid=kb;en-us;829134
>
> I hope they help you in your goals.
>
> --
> Ace
>
> This posting is provided "AS-IS" with no warranties or guarantees and
> confers no rights.
>
> If this post is viewed at a non-Microsoft community website, and you were
> to respond to it through that community's website, I may not see your
> reply unless that website posts replies back to the original Microsoft
> forum. Therefore, please direct all replies ONLY to the Microsoft public
> newsgroup this thread originated in so all can benefit or ensure the web
> community posts it back to the original forum.
>
> Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
> Microsoft MVP - Windows Server Directory Services
> Microsoft Certified Trainer
> Infinite Diversities in Infinite Combinations.
> =================================
>
>
>
>


.



Relevant Pages

  • RE: Outlook RPC over HTTp deosnt work
    ... try to use RPC over HTTP to connect the Exchange Server. ... What SBS is running on the problematic Server? ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC over HTTP Question
    ... allow specific traffic transfer and publish some web services to internet. ... On the Web Server Certificate page, ... The wizard automatically configures Exchange, IIS, and the RPC proxy ... >Subject: Re: RPC over HTTP Question ...
    (microsoft.public.windows.server.sbs)
  • RE: RPC over HTTP
    ... NTLM and Basic Authentication for RPC over HTTP: ... TCP port to connect Exchange server by Outlook, it is easy to go through ...
    (microsoft.public.windows.server.sbs)
  • Re: RPC Over HTTP Security
    ... With RPC over HTTP users can have security-enhanced access to their Exchange ... Server accounts from the Internet when they are working outside your ...
    (microsoft.public.exchange2000.general)
  • RE: Connecting via RPC
    ... I understand that you encountered problem when trying RPC to your Exchange ... 825763 How to configure Internet access in Windows Small Business Server ... Microsoft CSS Online Newsgroup Support ...
    (microsoft.public.windows.server.sbs)