2003 DC's mixed with 2000 DC Not working

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Is there anyway to tell if 2 2003 DC's were introduced to a 2000 domain with
2 2000 DC's properly? When the '03's are on things quit working. The person
that set this up has been let go and I'm trying to figure out what he did. A
nightmare? Would it be best to log a support call with MS? Thanks
 
Apparently when the 2003 servers are up and running they prevent the users
from being able to navigate or get to things. I turned on the servers last
week since they were already listed as DC's then left them on. The site
contact called me the next day and said they couldn't get the right rights to
the rest of their files so he shut down the '03 servers and things seemed to
work just fine again.

I have no documentation of what the previous person did and don't know if he
prepped the Domain and the Schema before introducing them. It maybe a simple
process of promoting the 2003 to the PDC and getting all of the stuff
transfered over to them. At this point I'm in learning mode to see what all
is going on. I don't know if introducing the 03's were done wrong and if
there is a way to back out or straighten out what has been done. Thanks.
 
The error message I get is the following. Whenever I try to navigate the
network or try to join the domain.

"DomainName" is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions.

Windows cannot find the network path. Verify that the network path is
correct and the destination computer is not busy or turned off. If windows
still cannot find the network path, contact your network administrator.
 
You might want to make sure the domain functional level is not set to Windows 2003.

--
Tony Eversole
MCSE, MCSA, Net+, A+
The error message I get is the following. Whenever I try to navigate the
network or try to join the domain.

"DomainName" is not accessible. You might not have permission to use this
network resource. Contact the administrator of this server to find out if
you have access permissions.

Windows cannot find the network path. Verify that the network path is
correct and the destination computer is not busy or turned off. If windows
still cannot find the network path, contact your network administrator.
 
This might be an SMB signing issue also. By default 2003 Domain Controllers
apply a more strick SMB signing policy then we did in 2000.

Check out Q article 823659.
Set all policies that are "REQUIRED" to DISABLED.
Set all policies that are "IF ABLE" to ENABLED.

Then reboot.



Thanks,
Christopher Ransom, MCSE 2000/2003, MCSA 2000/2003, CCNA
Microsoft Enterprise Platforms Support
Windows NT/Windows 2000 Directory Services
 
I know this is a problem when you run old clients like win98. but for
2000/xp there should be no problems.
 
Back
Top