Re: AD management snap in cannot find DC
- From: "Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx>
- Date: Wed, 11 Mar 2009 14:58:31 -0000
Ok, sounds correct.
Try the following:
On the client and server flush dns configuration, you can rightclick in the NIC card and choose repair or you can do it from cmd "ipconfig /flushdns". Do that in Client and server.
After that go to cmd and type (assuming admin tools installed on the client):
dsa.msc /Domain=imageproc.imageproc.com
What happens?
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MVP Directory Services
"Tony B" <tonyb@xxxxxxxxxxxxx> wrote in message news:uQlrBDjoJHA.5420@xxxxxxxxxxxxxxxxxxxxxxx
Hi Jorge,
dcdiag output on DC.
Domain Controller Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\ORAC
Starting test: Connectivity
......................... ORAC passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\ORAC
Starting test: Replications
......................... ORAC passed test Replications
Starting test: NCSecDesc
......................... ORAC passed test NCSecDesc
Starting test: NetLogons
......................... ORAC passed test NetLogons
Starting test: Advertising
......................... ORAC passed test Advertising
Starting test: KnowsOfRoleHolders
......................... ORAC passed test KnowsOfRoleHolders
Starting test: RidManager
......................... ORAC passed test RidManager
Starting test: MachineAccount
......................... ORAC passed test MachineAccount
Starting test: Services
......................... ORAC passed test Services
Starting test: ObjectsReplicated
......................... ORAC passed test ObjectsReplicated
Starting test: frssysvol
......................... ORAC passed test frssysvol
Starting test: frsevent
......................... ORAC passed test frsevent
Starting test: kccevent
......................... ORAC passed test kccevent
Starting test: systemlog
......................... ORAC passed test systemlog
Starting test: VerifyReferences
......................... ORAC passed test VerifyReferences
Running partition tests on : ForestDnsZones
Starting test: CrossRefValidation
......................... ForestDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... ForestDnsZones passed test CheckSDRefDom
Running partition tests on : DomainDnsZones
Starting test: CrossRefValidation
......................... DomainDnsZones passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... DomainDnsZones passed test CheckSDRefDom
Running partition tests on : Schema
Starting test: CrossRefValidation
......................... Schema passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Schema passed test CheckSDRefDom
Running partition tests on : Configuration
Starting test: CrossRefValidation
......................... Configuration passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... Configuration passed test CheckSDRefDom
Running partition tests on : imageproc
Starting test: CrossRefValidation
......................... imageproc passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... imageproc passed test CheckSDRefDom
Running enterprise tests on : imageproc.imageproc.com
Starting test: Intersite
......................... imageproc.imageproc.com passed test Intersite
Starting test: FsmoCheck
......................... imageproc.imageproc.com passed test FsmoCheck
ipconfig /all on DC
Windows IP Configuration
Host Name . . . . . . . . . . . . : ORAC
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 . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
Physical Address. . . . . . . . . : 00-13-72-34-BF-A4
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.92.109.6
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.92.109.4
DNS Servers . . . . . . . . . . . : 192.92.109.6
Primary WINS Server . . . . . . . : 192.92.109.6
ipconfig /all on a workstation
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
Regards
Tony
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message news:916C852C-E566-4F7C-B6E5-F94FF2C9AF29@xxxxxxxxxxxxxxxxOk,
Please post here the results for dcdiag "run dcdiag in the DC" and ipconfig for the DC and workstation.
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MVP Directory Services
"Tony B" <tonyb@xxxxxxxxxxxxx> wrote in message news:O2XFtXWoJHA.3984@xxxxxxxxxxxxxxxxxxxxxxxIf I select Active Directory Users and Computers and right click Connect to domain controller as below, and manually select the DC it connects to the domain and DC. If I then right click AD U & C -> Connect to Domain so I can check Save this domain setting , I get message "The domain ourdomain could not be found because: The specified domain either does not exist or could not be contacted." So only connecting to DC works, but I cannot connect to the domain itself.
Tony
"Jorge Silva" <jorgesilva_pt@xxxxxxxxxxx> wrote in message news:B33A1C30-9B63-491B-9F79-2280E0F744B6@xxxxxxxxxxxxxxxxHi,
Check if helps:
When you choose the option "Connect to Domain", after selecting the correct domain, choose the option "Save this domain setting for the current console".
--
I hope that the information above helps you.
Have a Nice day.
Jorge Silva
MVP Directory Services
"Tony B" <tonyb@xxxxxxxxxxxxx> wrote in message news:%23PHFuqOoJHA.5832@xxxxxxxxxxxxxxxxxxxxxxxWhen 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 ?
.
- Follow-Ups:
- Re: AD management snap in cannot find DC
- From: Tony B
- Re: AD management snap in cannot find DC
- References:
- AD management snap in cannot find DC
- From: Tony B
- Re: AD management snap in cannot find DC
- From: Jorge Silva
- Re: AD management snap in cannot find DC
- From: Tony B
- Re: AD management snap in cannot find DC
- From: Jorge Silva
- Re: AD management snap in cannot find DC
- From: Tony B
- AD management snap in cannot find DC
- Prev by Date: Re: Password Policy/Server 2008
- Next by Date: Re: Password Policy/Server 2008
- Previous by thread: Re: AD management snap in cannot find DC
- Next by thread: Re: AD management snap in cannot find DC
- Index(es):
Relevant Pages
|
Loading