Re: Upgrading from a Windows 2000 domain

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

This tells me the ip address you have specified is not properly registered
in dns.

Please post the results from running the following command at a command
prompt on the dc in question

ipconfig /all

--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

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.

"Bruce" <Bruce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A86C5F75-4BC4-4D30-B934-0ED430F40D4A@xxxxxxxxxxxxxxxx
Paul,

Here are the results of dnslint your requested me to run:


Microsoft Windows [Version 5.2.3790]
(C) Copyright 1985-2003 Microsoft Corp.

C:\Documents and Settings\admin>cd c:\

C:\>dnslint /ad /s 10.80.10.3

DNSLint will attempt to verify the
DNS entries used in AD replication

Using 127.0.0.1 for LDAP
Starting with 10.80.10.3 for DNS

This process may take several minutes to complete.........
LDAP query to speficied LDAP server on TCP port 389 failed
Server Down


LDAP query to speficied LDAP server on TCP port 389 failed
LDAP server specified appears to be down

Specify a different LDAP server and run the command again


C:\>

Bruce
--
Bruce


"Paul Bergson [MVP-DS]" wrote:

Get a good backup first off

Make sure you are logged on as an administrator and that your account is
in
the schema admins group

If this doesn't help then

Run diagnostics against your Active Directory domain.

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

Run dcdiag, netdiag and repadmin in verbose mode.
-> DCDIAG /V /C /D /E /s:yourdcname > c:\dcdiag.log
-> netdiag.exe /v > c:\netdiag.log (On each dc)
-> repadmin.exe /showrepl dc* /verbose /all /intersite > c:\repl.txt
-> dnslint /ad /s "ip address of your dc"

**Note: Using the /E switch in dcdiag will run diagnostics against ALL
dc's
in the forest. If you have significant numbers of DC's this test could
generate significant detail and take a long time. You also want to take
into account slow links to dc's will also add to the testing time.

If you download a gui script I wrote it should be simple to set and run
(DCDiag and NetDiag). It also has the option to run individual tests
without having to learn all the switch options. The details will be
output
in notepad text files that pop up automagically.

The script is located on my website at
http://www.pbbergs.com/windows/downloads.htm

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.

Description and download for dnslint
http://support.microsoft.com/kb/321045



--
Paul Bergson
MVP - Directory Services
MCTS, MCT, MCSE, MCSA, Security+, BS CSci
2008, 2003, 2000 (Early Achiever), NT4

http://www.pbbergs.com

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.

"Bruce" <Bruce@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:EFF5B2CE-8CD1-4553-B133-8913F9446FDC@xxxxxxxxxxxxxxxx
I lost one of my Servers (Windows 2000) which was a BDC for Fleet. The
new
server is running Windows Server 2003 standard edition (32 bit). I
wanted
to
add a role to this server so it could act as a BDC ( I know they no
longer
use that term) as a backup. When I run Adprep /forestprep it is not
completing and I am at a loss as to how to remedy the situation (dont
do
too
much Active Directory work at this end). I have included the adprep log
which
list detail as to the failed portion. Any and all help would be most
appreciated.

I have included the two failed lines from the ADPrep.log:


Adprep was unable to complete because the call back function (null)
failed.

[Status/Consequence]

Error message: Property msDS-FilterContainers was not found in csv file
C:\WINNT\system32\debug\adprep\data\dcpromo.csv. (0x80004005).

[User Action]

Check the log file Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20080905131647 directory for more
information.



Adprep was unable to update forest-wide information.

[Status/Consequence]

Adprep requires access to existing forest-wide information from the
schema
master in order to complete this operation.

[User Action]

Check the log file, Adprep.log, in the
C:\WINNT\system32\debug\adprep\logs\20080905131647 directory for more
information.
--
Bruce





.

Relevant Pages

  • Re: Upgrading from a Windows 2000 domain
    ... Here are the results of dnslint your requested me to run: ... LDAP query to speficied LDAP server on TCP port 389 failed ... When I run Adprep /forestprep it is not ...
    (microsoft.public.windows.server.active_directory)
  • Re: Add W2K8 Standard member Server to W2k3 Standard Domain
    ... one other thought here....i used the adprep command from the w2k8 server cd. ... I was planning to make it a dns server. ...
    (microsoft.public.windows.server.general)
  • Re: windows 2003 oem server
    ... To prepare the forest for running Windows Server 2003 DCs, run the adprep ... command on the schema operations master, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Issues in joining Windows 2003 Server R2 as DC to Windows 2003 SBS Sp1
    ... Log in to the SBS server with the Administrator account. ... The command has completed successfully ... Adprep successfully updated the forest-wide information. ...
    (microsoft.public.windows.server.sbs)
  • Re: Server upgrade.
    ... Is the new server R2 version? ... The run the adprep command from the second R2 disk. ... On the exisiting one run "schupgr" in a command window to check the actual version. ...
    (microsoft.public.windows.server.migration)