Yep, they can ping each other fine. All other network activity seems to be fine. ISA is also installed on the problematic DC and I can use that fine. RPC services also seem fine. Neil > -----Original Message----- > From: windows2000-bounce@xxxxxxxxxxxxx > [mailto:windows2000-bounce@xxxxxxxxxxxxx] On Behalf Of Sorin Srbu > Sent: 08 August 2006 12:00 > To: windows2000@xxxxxxxxxxxxx > Subject: [windows2000] Re: Windows Server 2003 upgrade > > Neil Bullock <> wrote on Tuesday, August 08, 2006 12:34 PM: > > Are the DCs talking to each other? Can you ping them? > > > Hi, > > > > Yesterday, I upgraded our first domain controller to 2003 from 2000. > > Went fine. Excellent. I was surprised, as it holds all > the main FSMO > > roles and stuff. Pleased by this success, I went on to > upgrade another > > 2000 DC (a domain controller in another domain) to 2003. > > > > Copied files fine, rebooted, then blue screened. I went into the > > recovery console, and stopped some services and drivers, > and got it to > > boot, and it completed the installation. > > > > Today, I find that people logging on to that domain are randomly > > unable to access shares. Netlogon doesn't work for most > people, so no > > logon scripts run. No other shares work unless you map a drive, and > > most of the time that asks for a user/password and rejects > whatever you > > enter. > > > > Also, I can't access event viewer remotely, or services manager. > > > > Unable to find anything relevant in the event log (there > are a lot of > > errors relating to the processing of group policy, but that seems to > > have been fixed by SP1). > > > > So, any ideas where to start on this? I'm fresh out. > > > > Neil ***************************** New Site from The Kenzig Group! Windows Vista Links, list options and info are available at: http://www.VistaPop.com ***************************** To Unsubscribe, set digest or vacation mode or view archives use the below link. http://thethin.net/win2000list.cfm