Forum Search:
Forum.Brain-Cluster.com: Brain Cluster Technical Forum
Ultimate forum for Technical Discussions

Home » Microsoft » Windows Server » Active Directory » did you have any luck in resolving this issue?
did you have any luck in resolving this issue? [message #162019] Tue, 13 October 2009 10:26 Go to next message
brent crighton  is currently offline brent crighton  United States
Messages: 1
Registered: October 2009
Junior Member
i have the exact same circumstances, the onset of such was a couple of days ago

just wondering how this matter .. ended ?

regards

brent



Tony B wrote:

Re: AD management snap in cannot find DC
12-Mar-09

"Jorge Silva" <jorgesilva_pt@hotmail.com> wrote in message
news:OX4hevooJHA.3896@TK2MSFTNGP04.phx.gbl...

Yes as I said in my original post the AD snapins only work when I manually
connect to the DC by name. If I run the AD management snapin it reports that
"Naming information cannot be located because: The specified domain either
does not exist or could not be contacted. contact your system admin........"
and then opens with red cross on AD UC and AD SS. If I right click AD UC,
and click connect to domain, and then click browse I get dialog Unable to
browse the domain because: configuration information could not be read from
the domain controller, either because the mchine is unavailable or access
has been denied. If I right click AD UC "Connect to domain controller" none
are listed under "Or Select an available domain controller" If I explicitly
specify the name of my DC it will then connect.

Regards
Tony

EggHeadCafe - Software Developer Portal of Choice
Book Review: ASP.NET 2.0 Web Programming with VB 2005 [Murach]
http://www.eggheadcafe.com/tutorials/aspnet/5ce13132-519c-48 6e-908d-b006d6c94b35/book-review-aspnet-20.aspx
Re: did you have any luck in resolving this issue? [message #162026 is a reply to message #162019] Tue, 13 October 2009 14:35 Go to previous messageGo to next message
meiweb  is currently offline meiweb  Germany
Messages: 2225
Registered: September 2009
Senior Member
Hello brent,

Please do not use an older incomplete posting.

Please give some infos about YOUR domain, how many DCs and how are they located,
is AD sites and services configured accordingly.

Additional post an unedited ipconfig /all from all DC/DNS servers so we can
exclude DNS as a problem.

Additional give some information about your OS version with SP/patch level.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> i have the exact same circumstances, the onset of such was a couple of
> days ago
>
> just wondering how this matter .. ended ?
>
> regards
>
> brent
>
> Tony B wrote:
>
> Re: AD management snap in cannot find DC
> 12-Mar-09
> "Jorge Silva" <jorgesilva_pt@hotmail.com> wrote in message
> news:OX4hevooJHA.3896@TK2MSFTNGP04.phx.gbl...
>
> Yes as I said in my original post the AD snapins only work when I
> manually connect to the DC by name. If I run the AD management snapin
> it reports that "Naming information cannot be located because: The
> specified domain either does not exist or could not be contacted.
> contact your system admin........" and then opens with red cross on AD
> UC and AD SS. If I right click AD UC, and click connect to domain, and
> then click browse I get dialog Unable to browse the domain because:
> configuration information could not be read from the domain
> controller, either because the mchine is unavailable or access has
> been denied. If I right click AD UC "Connect to domain controller"
> none are listed under "Or Select an available domain controller" If I
> explicitly specify the name of my DC it will then connect.
>
> Regards
> Tony
> EggHeadCafe - Software Developer Portal of Choice
>
> Book Review: ASP.NET 2.0 Web Programming with VB 2005 [Murach]
>
> http://www.eggheadcafe.com/tutorials/aspnet/5ce13132-519c-48 6e-908d-b0
> 06d6c94b35/book-review-aspnet-20.aspx
>
Re: did you have any luck in resolving this issue? [message #162033 is a reply to message #162019] Tue, 13 October 2009 17:28 Go to previous messageGo to next message
Jorge Silva  is currently offline Jorge Silva  Portugal
Messages: 398
Registered: July 2009
Senior Member
Hi
That matter ended with
dsa.msc /Server:dcfqdn
Then using the dsa.msc, choose the option in the snap-in "save the current
domain controller to this console, or something similar..."
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MVP Directory Services

Please no e-mails, any questions should be posted in the NewsGroup
This posting is provided "AS IS" with no warranties, and confers no rights.



"brent crighton" wrote in message
news:2009101312268birdshillbilly@live.ca...
> i have the exact same circumstances, the onset of such was a couple of
> days ago
>
> just wondering how this matter .. ended ?
>
> regards
>
> brent
>
>
>
> Tony B wrote:
>
> Re: AD management snap in cannot find DC
> 12-Mar-09
>
> "Jorge Silva" <jorgesilva_pt@hotmail.com> wrote in message
> news:OX4hevooJHA.3896@TK2MSFTNGP04.phx.gbl...
>
> Yes as I said in my original post the AD snapins only work when I manually
> connect to the DC by name. If I run the AD management snapin it reports
> that
> "Naming information cannot be located because: The specified domain either
> does not exist or could not be contacted. contact your system
> admin........"
> and then opens with red cross on AD UC and AD SS. If I right click AD UC,
> and click connect to domain, and then click browse I get dialog Unable to
> browse the domain because: configuration information could not be read
> from
> the domain controller, either because the mchine is unavailable or access
> has been denied. If I right click AD UC "Connect to domain controller"
> none
> are listed under "Or Select an available domain controller" If I
> explicitly
> specify the name of my DC it will then connect.
>
> Regards
> Tony
>
> EggHeadCafe - Software Developer Portal of Choice
> Book Review: ASP.NET 2.0 Web Programming with VB 2005 [Murach]
> http://www.eggheadcafe.com/tutorials/aspnet/5ce13132-519c-48 6e-908d-b006d6c94b35/book-review-aspnet-20.aspx
Re: did you have any luck in resolving this issue? [message #162114 is a reply to message #162019] Thu, 15 October 2009 03:51 Go to previous message
tonyb61  is currently offline tonyb61  United Kingdom
Messages: 9
Registered: September 2009
Junior Member
I did.
In spite of lots of suggestions from this group, I couldn't resolve it. In
the end I had to involve Microsoft support, and they eventually solved it,
after escalating it through several levels of support. It happened because
of the way we migrated a NT server via svr2000 to svr2003. I cannot remember
the precise details, but in the end it was a registry setting that was
migrated that shouldn't have been.

HKLM\System\CurrentControlSet\Services\Netlogon\Parameters - Removed the
NT4Emulator Key from DC
Microsoft also referred me to this KB article.
http://support.microsoft.com/kb/284937

HTH
Tony

<brent crighton> wrote in message
news:2009101312268birdshillbilly@live.ca...
>i have the exact same circumstances, the onset of such was a couple of days
>ago
>
> just wondering how this matter .. ended ?
>
> regards
>
> brent
>
>
>
> Tony B wrote:
>
> Re: AD management snap in cannot find DC
> 12-Mar-09
>
> "Jorge Silva" <jorgesilva_pt@hotmail.com> wrote in message
> news:OX4hevooJHA.3896@TK2MSFTNGP04.phx.gbl...
>
> Yes as I said in my original post the AD snapins only work when I manually
> connect to the DC by name. If I run the AD management snapin it reports
> that
> "Naming information cannot be located because: The specified domain either
> does not exist or could not be contacted. contact your system
> admin........"
> and then opens with red cross on AD UC and AD SS. If I right click AD UC,
> and click connect to domain, and then click browse I get dialog Unable to
> browse the domain because: configuration information could not be read
> from
> the domain controller, either because the mchine is unavailable or access
> has been denied. If I right click AD UC "Connect to domain controller"
> none
> are listed under "Or Select an available domain controller" If I
> explicitly
> specify the name of my DC it will then connect.
>
> Regards
> Tony
>
> EggHeadCafe - Software Developer Portal of Choice
> Book Review: ASP.NET 2.0 Web Programming with VB 2005 [Murach]
> http://www.eggheadcafe.com/tutorials/aspnet/5ce13132-519c-48 6e-908d-b006d6c94b35/book-review-aspnet-20.aspx
Previous Topic:Authentication traffic leaving sites
Next Topic:Firewall Ports
Goto Forum:
  


Current Time: Wed Jan 17 04:12:45 MST 2018

Total time taken to generate the page: 0.04526 seconds
.:: Contact :: Home ::Sitemap::.

Powered by: FUDforum 3.0.0RC2.
Copyright ©2001-2009 FUDforum Bulletin Board Software