Re: Contacting a domain controller

Do you have any TCP/IP filtering or firewalls set up between the two DCs?
Make sure that the two DCs can communicate on TCP 389.

http://www.windowsitpro.com/Article/ArticleID/27455/27455.html?Ad=1

--
Laura E. Hunter
Microsoft MVP - Windows Server Networking
Author: _Active Directory Consultant's Field Guide_
(http://tinyurl.com/7f8ll)

All information provided "AS-IS", no warranties expressed or implied.
Replies to newsgroup only.


"Alan258" <Alan258@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:4AB20A69-0B7D-4C6A-A2C1-06DBF8A52E86@xxxxxxxxxxxxxxxx
>I am trying to connect 2 domains (both use Windows 2003 Server). When I
>right
> click on "Active domains and trusts" and then click on "Connect to domain
> controller", I get the following error message:
>
> "The configuration information describing this enterprise is not
> available.
> Logon attempt failed" -
>
> Can anybody help?
> --
> Alan B


.

Relevant Pages

  • Re: Floating Computer between domains
    ... Windows itself is generally weak in this area but with DCs it can get especially bad with DNS registrations and other issues. ... can I simply put a second network card into the domain ... communicate with eachother, all other machines in the respective ... networks would have to talk to the domain controller that is connected ...
    (microsoft.public.windows.server.active_directory)
  • RE: migration prolems from NT 4.0 to W2k
    ... the out new Win2K server cannot communicate with the other DCs in ... DCs in Headquarter and the Windows 2k DC? ... This posting is provided "AS IS" with no warranties, ...
    (microsoft.public.windows.server.migration)
  • Re: NTFRSUTIL error 1753
    ... Yes DC2 did not complete initialzation of sysvol ... AD communication between DCs requires 29 ports opened and free and clear, including the dynamic ephemeral response ports. ... This will insure DCs can communicate with each other, as well as clients can communicate with the DCs. ...
    (microsoft.public.windows.server.active_directory)
  • Re: the protocols&ports required for win2000 DCs synchronize
    ... By the time you'd do that, there isn't much point in having the firewall. ... > We will setup some win2000 DCs in our network environment,> but the firewall separate those DCs. ... > UDP/TCP 88 ... > TCP 123 ...
    (microsoft.public.win2000.networking)
  • the protocols&ports required for win2000 DCs synchronize
    ... We will setup some win2000 DCs in our network environment, ... Which ports should be allowed to let the DCs can ... TCP 123 ...
    (microsoft.public.win2000.networking)