Domain Rename Problem

[Guest]

I received the following error message when running rendom /upload:
C:\DOMAIN~1>rendom /showforest
yvr.ipackets.com [ForestRoot Domain, FlatName:IPKL]
DomainDnsZones.yvr.ipackets.com [PartitionType:Application]
ForestDnsZones.yvr.ipackets.com [PartitionType:Application]

The operation completed successfully.

C:\DOMAIN~1>rendom /upload
Couldn't find a GC for the enterprise. Please ensure that there is a
contactable GC in the forest and try again..
Cannot connect and bind to the Domain Naming FSMO. Cannot Continue.: The
specified domain either does not exist or could not be contacted. :1355

C:\DOMAIN~1>

I did a search but couldn't find a specific solution for this problem, but I
found an article about testing Active Directory using dcdiag and the results
don't look good:

C:\WINDOWS\ServicePackFiles\i386>dcdiag

Domain Controller Diagnosis

Performing initial setup:
[diamond] Directory Binding Error -2146892976:
The system detected a possible attempt to compromise security. Please
ensure
that you can contact the server that authenticated you.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DIAMOND
Starting test: Connectivity
The host
143391b6-50eb-425f-bfed-22c6810dcc0._msdcs.www.ipackets.com could not be
resolved to an IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(143391b6-50eb-425f-bfed-722c6810dcc0._msdcs.www.ipackets.com)
couldn't be resolved, the server name (diamond.www.ipackets.com)
resolved to the IP address (192.168.0.10) and was pingable. Check
that the IP address is registered correctly with the DNS server.
.......................... DIAMOND failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DIAMOND
Skipping all tests, because server DIAMOND is
not responding to directory service requests

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 : www
Starting test: CrossRefValidation
.......................... www passed test CrossRefValidation
Starting test: CheckSDRefDom
.......................... www passed test CheckSDRefDom

Running enterprise tests on : www.ipackets.com
Starting test: Intersite
.......................... www.ipackets.com passed test Intersite
Starting test: FsmoCheck
[DIAMOND] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
.......................... www.ipackets.com passed test FsmoCheck

C:\WINDOWS\ServicePackFiles\i386>

Can anybody help?
Many thanks,
Norman

 

[Paul Bergson]

RPC errors seem to be the issue, the link below can help you track the
error.
http://support.microsoft.com/?id=839880

You could run dcdiag /fix This can fix minor issues, I doubt this
will help but it shouldn't hurt to try. Make sure you have a GOOD backup
before you do anything to your network.

I'm not sure what switches you had set:, so you may want to follow below as
well to help possibly further diagnose it.



Run diagnostics against your Active Directory domain.

If you don't have the tools installed, install them from your server install
disk.
d:\support\tools\setup.exe

Run dcdiag and netdiag in verbose mode.

If you download a gui script I wrote it should be simple to set and run. It
also has the option to run individual tests without having to learn all the
switch options.

The script is at http://pbbergs.dynu.com/windows/windows.htm, download it
and save it to c:\program files\support tools\

Just select both dcdiag and netdiag make sure verbose is set. (Leave the
default settings for dcdiag as set when selected)

When complete search for fail, error and warning messages.


--


Paul Bergson MCT, MCSE, MCSA, CNE, CNA, CCA

This posting is provided "AS IS" with no warranties, and confers no rights.

I received the following error message when running rendom /upload:
C:\DOMAIN~1>rendom /showforest
yvr.ipackets.com [ForestRoot Domain, FlatName:IPKL]
DomainDnsZones.yvr.ipackets.com [PartitionType:Application]
ForestDnsZones.yvr.ipackets.com [PartitionType:Application]

The operation completed successfully.

C:\DOMAIN~1>rendom /upload
Couldn't find a GC for the enterprise. Please ensure that there is a
contactable GC in the forest and try again..
Cannot connect and bind to the Domain Naming FSMO. Cannot Continue.: The
specified domain either does not exist or could not be contacted. :1355

C:\DOMAIN~1>

I did a search but couldn't find a specific solution for this problem, but
I
found an article about testing Active Directory using dcdiag and the
results
don't look good:

C:\WINDOWS\ServicePackFiles\i386>dcdiag

Domain Controller Diagnosis

Performing initial setup:
[diamond] Directory Binding Error -2146892976:
The system detected a possible attempt to compromise security. Please
ensure
that you can contact the server that authenticated you.
This may limit some of the tests that can be performed.
Done gathering initial info.

Doing initial required tests

Testing server: Default-First-Site-Name\DIAMOND
Starting test: Connectivity
The host
143391b6-50eb-425f-bfed-22c6810dcc0._msdcs.www.ipackets.com could not be
resolved to an IP address. Check the DNS server, DHCP, server name, etc
Although the Guid DNS name
(143391b6-50eb-425f-bfed-722c6810dcc0._msdcs.www.ipackets.com)
couldn't be resolved, the server name (diamond.www.ipackets.com)
resolved to the IP address (192.168.0.10) and was pingable. Check
that the IP address is registered correctly with the DNS server.
......................... DIAMOND failed test Connectivity

Doing primary tests

Testing server: Default-First-Site-Name\DIAMOND
Skipping all tests, because server DIAMOND is
not responding to directory service requests

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 : www
Starting test: CrossRefValidation
......................... www passed test CrossRefValidation
Starting test: CheckSDRefDom
......................... www passed test CheckSDRefDom

Running enterprise tests on : www.ipackets.com
Starting test: Intersite
......................... www.ipackets.com passed test Intersite
Starting test: FsmoCheck
[DIAMOND] DsBindWithSpnEx() failed with error 1722,
The RPC server is unavailable..
......................... www.ipackets.com passed test FsmoCheck

C:\WINDOWS\ServicePackFiles\i386>

Can anybody help?
Many thanks,
Norman