Windows 2000 domain upgrade Windows 2003

Hi there- I'm attempting to migrate a Windows 2000 domain to 2003.
forest prep/domain prep have already been run on 2000 DC. 2003 DC is
on domain and successfully logging on users accounts( as security log
shows.). Replication is confirmed between 2 DC's. All FSMO roles, as
well as GC, have been transferred to 2003 DC, though 2000 DC is still a
GC also. There are no profiles stored on 2000 DC. When I take down
2000 DC users cannot fully logon to domain. By this, I mean I see a
success logon in event viewer on 2003, however upon 'applying computer
settings' the pc hangs. Immediately when the 2000 DC is restarted, the
user logs on without issue.
DHCP server is giving out correct DNS address w/IP's for new DC.

DCdiag when run on 2003 passes everything except frsevent. It says
'There are warning or error events within the last 24 hours after the
Group Policy problems. Failing SYSVOL replication problems may cause"
-SYSVOL is shared properly on both DC's
-event log has error 13508 stating:

The File Replication Service is having trouble enabling replication
from LUGH to APOLLO for c:\windows\sysvol\domain using the DNS name
lugh.naplcpd.local. FRS will keep retrying.
Following are some of the reasons you would see this warning.

[1] FRS can not correctly resolve the DNS name lugh.naplcpd.local from
this computer.
[2] FRS is not running on lugh.naplcpd.local.
[3] The topology information in the Active Directory for this replica
has not yet replicated to all the Domain Controllers.

This event log message will appear once per connection, After the
problem is fixed you will see another event log message indicating that
the connection has been established.

-lugh can be pinged by fqdn. this error appears on both DC's. frs is
running.

LUGH is 2000, APOLLO is 2003

when netdiag is run, LDAP test passes yet says the following:
WARNING - failed to query SPN registration on DC 'apollo.abc.local'
WARNING - failed to query SPN registration on DC 'lugh.abc.local'

these errors are identical on both DC's, except 'FRSSYSVOL' test passed
on the 2000 DC. I don't know if that is the equivalent of 'frsevent'
on 2003.

Any help/suggestions would be greatly appreciated.

.

Relevant Pages

  • 2003 upgrade failure - domain prep was not run, but it was!
    ... enabling replication from TRAPPER to RADAR for ... FRS can not correctly resolve the DNS name ... This event log message will appear once per ... connection has been established. ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication problems
    ... w2k3 File Replication Service Log ... FRS will keep ... FRS can not correctly resolve the DNS name \\DELLSERVER.millennium ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Replication problems
    ... w2k File Replication Log ... FRS can not correctly resolve the DNS name MILLENNIUM-100.millennium ... This event log message will appear once per connection, ...
    (microsoft.public.windows.server.active_directory)
  • Re: replication error
    ... Consider that the vast majority of Replication ... working and only FRS is failing then usually this exonerates DNS.] ... This event log message will appear once per ...
    (microsoft.public.win2000.active_directory)
  • Re: replication error
    ... Consider that the vast majority of Replication ... working and only FRS is failing then usually this exonerates DNS.] ... This event log message will appear once per ...
    (microsoft.public.win2000.active_directory)
Loading