trouble accessing DC

[JOJO]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Windows 2000 Active Directory domain running in native mode. A forest with
a single domain. All DC are fully patched.

I am unable to access the shared folders (sysvol, etc) of domain controller
SV52 from any computer in the domain.

--- The machine is pingable by name and IP.
--- DNS looks good. (forward and reverse)
--- WINS records are good.
--- SV52, does not show in Network Places from other domain computers
--- SV52, does show in Network Places from itself
--- SV52 is not accessible over the network at all, //SV52 does not work
--- SV52 is accessible using //SV52 when logged into itself

I'm thinking the machine account is corrupted in some way, but I'm not sure
yet.

The dcdiag command /test:machineaccount gives the following return.

DC Diagnosis
Performing initial setup:
Done gathering initial info.
Doing initial non skippeable tests
Testing server: Default-First-Site-Name\SV52
Starting test: Connectivity
......................... SV52 passed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\SV52
Starting test: MachineAccount
Could not open pipe with [SV52]:failed with 67: The network name
cannot be found.
Could not get NetBIOSDomainName
Failed can not test for HOST SPN
Failed can not test for HOST SPN
* Missing SPN null)
* Missing SPN null)
......................... SV52 failed test MachineAccount
###################################################

Using the netdiag command gives the following errors.

C:\Program Files\Support Tools>netdiag /d:domain.edu
[FATAL] Failed to get system information of this machine.

C:\Program Files\Support Tools>netdiag /test:wins
[FATAL] Failed to get system information of this machine.

C:\Program Files\Support Tools>netdiag /test:dclist
[FATAL] Failed to get system information of this machine.

#############################################

I'm leaning towards using dcpromo to demote the machine, removing it from
the domain, re-adding it to the domain, and then using dcpromo to promote it.

Any ideas would be appreiciated.

 

[Guest]

Archived from groups: microsoft.public.win2000.active_directory (More info?)

Seems like demote, reinstall, promote is the easiest solution in this case.

Some things to do if you want to spend some time to troubleshooting the
current install.
Check that NetBIOS over TCP/IP is enabled.
Use nltest /DSQUERYDNS (Nltest is a part of the Windows Server Support Tools
found at your Windows Server CD.)
Verify that DNS is configured correct.

--
Regards
Christoffer Andersson
Microsoft MVP - Directory Services

No email replies please - reply in the newsgroup
------------------------------------------------
http://www.chrisse.se - Active Directory Tips

"jojo" <jojo@discussions.microsoft.com> skrev i meddelandet
news:5AE51314-A99F-4503-907D-E85D358809DD@microsoft.com...
>
> Windows 2000 Active Directory domain running in native mode. A forest
> with
> a single domain. All DC are fully patched.
>
> I am unable to access the shared folders (sysvol, etc) of domain
> controller
> SV52 from any computer in the domain.
>
> --- The machine is pingable by name and IP.
> --- DNS looks good. (forward and reverse)
> --- WINS records are good.
> --- SV52, does not show in Network Places from other domain computers
> --- SV52, does show in Network Places from itself
> --- SV52 is not accessible over the network at all, //SV52 does not work
> --- SV52 is accessible using //SV52 when logged into itself
>
> I'm thinking the machine account is corrupted in some way, but I'm not
> sure
> yet.
>
> The dcdiag command /test:machineaccount gives the following return.
>
> DC Diagnosis
> Performing initial setup:
> Done gathering initial info.
> Doing initial non skippeable tests
> Testing server: Default-First-Site-Name\SV52
> Starting test: Connectivity
> ......................... SV52 passed test Connectivity
>
> Doing primary tests
>
> Testing server: Default-First-Site-Name\SV52
> Starting test: MachineAccount
> Could not open pipe with [SV52]:failed with 67: The network name
> cannot be found.
> Could not get NetBIOSDomainName
> Failed can not test for HOST SPN
> Failed can not test for HOST SPN
> * Missing SPN null)
> * Missing SPN null)
> ......................... SV52 failed test MachineAccount
> ###################################################
>
> Using the netdiag command gives the following errors.
>
> C:\Program Files\Support Tools>netdiag /d:domain.edu
> [FATAL] Failed to get system information of this machine.
>
> C:\Program Files\Support Tools>netdiag /test:wins
> [FATAL] Failed to get system information of this machine.
>
> C:\Program Files\Support Tools>netdiag /test:dclist
> [FATAL] Failed to get system information of this machine.
>
> #############################################
>
> I'm leaning towards using dcpromo to demote the machine, removing it from
> the domain, re-adding it to the domain, and then using dcpromo to promote
> it.
>
> Any ideas would be appreiciated.
>
>
>
>
>
>
>
>
>