Re: AD management snap in cannot find DC

Hello Tony,

Did you check that the time zone and time on the DC and the client are the same?

Also run ipconfig /flushdns on the client and try again to open the console.

The domain machines should all have the imageproc.imageproc.com in the "Primary DNS suffix of this computer" field.

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


Hi Meinolf,
I tried your suggestion but problem still exists.
ipconfig /all on workstation now reports
C:\Program Files\Support Tools>ipconfig /all
Windows IP Configuration
Host Name . . . . . . . . . . . . : tonyb-pc
Primary Dns Suffix . . . . . . . : imageproc.imageproc.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : imageproc.imageproc.com
Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : imageproc.imageproc.com
Description . . . . . . . . . . . : NVIDIA nForce Networking
Controller
Physical Address. . . . . . . . . : 00-05-5D-06-DB-6A
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.92.109.141
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.92.109.4
DHCP Server . . . . . . . . . . . : 192.92.109.6
DNS Servers . . . . . . . . . . . : 192.92.109.6
Primary WINS Server . . . . . . . : 192.92.109.6
Lease Obtained. . . . . . . . . . : 10 March 2009 14:41:04
Lease Expires . . . . . . . . . . : 18 March 2009 14:41:04
ping 192.92.109.6 ok (dc ip)
ping orac ok (dc name)
ping orac.imageproc.imageproc.com ok (fqdn)
ping imageproc.imageproc.com ok (domain)
192.92.109.6 looked up for all pings above.
But AD UC still reports "Naming information cannot be located
because:........"
Regards
Tony
"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb661c74a8cb6faa5768aeef@xxxxxxxxxxxxxxxxxxxxxxx

Hello Tony,

On the client machine check under system properties, computer name,
change button, more button, the "Primary DNS suffix of this
computer", it should be imageproc.imageproc.com, if not change it
there, reboot verify that you can ping with ip address, computername
and FQDN and try to open the AD UC.

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
Hi Meinolf,
The netbios domain name (under computer/properties/computer name ?)
is
Imageproc except on the DC where the name is
orac.imageproc.imageproc.com,
and domain is imageproc.imageproc.com
The AD and DNS domain name is imageproc.imageproc.com
So there is one difference. The workstations see the domain as
imageproc,
not imageproc.imageproc.com (The domain used to be called imageproc
on
an NT
machine, but when we migrated to 2003 server, the domain was changed
to
imageproc.imageproc.com but if we add new machines we still use the
domain
name imageproc, which works seems to work fine for user
authentication
or
joining the domain.
Regards
Tony
"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb661c7148cb6f99aed5b9ef@xxxxxxxxxxxxxxxxxxxxxxx
Hello Tony,

Please post your Netbios domain name, the DNS domain name and the
AD domain name under AD UC.

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
My DHCP settings set the DNS servers for all machines to use the
internal
DNS server (which is also the DC).
ipconfig /all on the machines confirm that the internal DNS server
is
set in
tcp/ip properties. The dns suffix is the domain name. I can ping
the
DNS
machine by name, or by qualified name name.our.domain.com.
I installed the complete support tools pack.
Thanks
Tony
"Meinolf Weber [MVP-DS]" <meiweb(nospam)@gmx.de> wrote in message
news:ff16fb661c2048cb6f284b4433a2@xxxxxxxxxxxxxxxxxxxxxxx
Hello Tony,

Make sure to use only domain internal DNS servers on the client
NIC configuration to prevent connection problems. Did you install
the complete adminpak on the client or only extract a part of it?

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
When I run AD management snap in on the DC it runs fine. If I
install the snap in on another machine in the domain, when I run
it an error appears, stating "Naming information cannot be
located because: The specified domain either does not exist or
cannot be contacted. Contact your ...." If I OK, the snap in
opens, but has no entries. If I right click Active Users and
Computers item, and select Connect to domain controller, and
manually enter the DC name, I get a dialog Domain Controller
ourDC is in domain our.domain.com. You are currently
administering domain . Do you want to administer domain
our.domain.com by using domain controller ourDC ? If I click
yes, then it shows the domain correctly, and shows me the
users/compauters etc as it would if I ran it on the DC ?

If I right click Active Directory Sites and Services, and right
click Connect to Domain Controller, and then click Browse domain
I get an error Unable to browse domain because: Configuration
infomration cannot be read from the domain controller, either
because the machine is unavailable or access has been denied.

Is this correct behaviour ? Should the snap in find domains
advertised ?



.