Re: Windows 2003 member server with Windows 2000 Domain Controller
From: Marina Roos (marina_at_roos.nodontwantspam.nl.com)
Date: 01/04/04
- Next message: John Loch: "Need help; NAV 2000 stopped launching; NAV 2004 can't finish install"
- Previous message: Joe Richards [MVP]: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- In reply to: Citimouse: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- Next in thread: Ace Fekay [MVP]: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Date: Sun, 04 Jan 2004 15:42:20 GMT
Just make sure you stop all third party services before you install SP4. At
least install SP3 and the ms03-039.
Regards,
Marina
"Citimouse" <citimousemeow@hotmail.com> schreef in bericht
news:3ff7cb91$1@news.starhub.net.sg...
> Yes. I knew that. But no matter how I try it, after the installaiton of
SP4,
> it just hang at the Windows 2000 screen. I would like to reinstall the
whole
> server but I do not have any spare hardware for it. I am just crossing my
> fingers now.
>
>
>
> "Marina Roos" <marina@roos.nodontwantspam.nl.com> wrote in message
> news:%cVJb.38128$Ax3.13060@typhoon.bart.nl...
> > You really should have your W2K DC on SP4 with the ms03-039 patch
> installed.
> > Right now you're very vunerable for the Blast worm (if you're not
already
> > infected!).
> >
> > Regards,
> >
> > Marina
> >
> > "Citimouse" <citimousemeow@hotmail.com> schreef in bericht
> > news:3ff75dfc$1@news.starhub.net.sg...
> > > Hi All,
> > >
> > > If anyone is having a Windows 2003 member server with a Windows 2000
> > Domain
> > > Controller, will you please help me?
> > >
> > > I have 2 Windows 2003 servers with a Windows 2000 Domain Controller.
In
> > both
> > > Windows 2003 server, both registered the same event as mentioned
below.
> > >
> > > Application Log
> > >
> > > Event Type: Error
> > > Event Source: Userenv
> > > Event Category: None
> > > Event ID: 1054
> > > Date: 12/30/2003
> > > Time: 10:09:31 AM
> > > User: NT AUTHORITY\SYSTEM
> > > Computer: AVIANO
> > > Description:
> > > Windows cannot obtain the domain controller name for your computer
> > network.
> > > (The specified domain either does not exist or could not be
> contacted. ).
> > > Group Policy processing aborted.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > >
> > >
> > > System Log
> > >
> > > Event Type: Error
> > > Event Source: NETLOGON
> > > Event Category: None
> > > Event ID: 5719
> > > Date: 1/4/2004
> > > Time: 5:33:15 AM
> > > User: N/A
> > > Computer: AVIANO
> > > Description:
> > > This computer was not able to set up a secure session with a domain
> > > controller in domain AAF due to the following:
> > > There are currently no logon servers available to service the logon
> > request.
> > > This may lead to authentication problems. Make sure that this computer
> is
> > > connected to the network. If the problem persists, please contact your
> > > domain administrator.
> > >
> > > ADDITIONAL INFO
> > > If this computer is a domain controller for the specified domain, it
> sets
> > up
> > > the secure session to the primary domain controller emulator in the
> > > specified domain. Otherwise, this computer sets up the secure session
to
> > any
> > > domain controller in the specified domain.
> > >
> > > For more information, see Help and Support Center at
> > > http://go.microsoft.com/fwlink/events.asp.
> > > Data:
> > > 0000: 5e 00 00 c0
> > > ^..À
> > >
> > > It seems like the servers got dropped out of the domain and it cannot
> get
> > > authenticated. We have an in-house application and when the server got
> > > "disjoin" and when we tried to login to our application, it says
access
> is
> > > denied and an event is recorded as below,
> > >
> > > Event Type: Failure Audit
> > > Event Source: Security
> > > Event Category: Logon/Logoff
> > > Event ID: 537
> > > Date: 30-Dec-03
> > > Time: 2:58:53 PM
> > > User: NT AUTHORITY\SYSTEM
> > > Computer: OSAN
> > > Description:
> > > Logon Failure:
> > > Reason: An error occurred during logon
> > > User Name: xxx
> > > Domain: yyy
> > > Logon Type: 3
> > > Logon Process: NtLmSsp
> > > Authentication Package: NTLM
> > > Workstation Name: HELP
> > > Status code: 0xC000005E
> > > Substatus code: 0x0
> > > Caller User Name: -
> > > Caller Domain: -
> > > Caller Logon ID: -
> > > Caller Process ID: -
> > > Transited Services: -
> > > Source Network Address: xx.xxx.xxx.xx
> > > Source Port: 1496
> > >
> > > I have done some research on the Internet and I have tried to follow
> some
> > of
> > > the suggestions like using the updated network driver, disable media
> > > sensing, set the speed of the NIC to match the switch, install
MS02-001
> > and
> > > others but still of no help. I wonder does this has to do with the
> Domain
> > > Controller. I have to rejoin the server to the domain at least twice a
> > day.
> > >
> > > My DC is still in SP2 for some reasons it cannot be upgraded beyond
SP2.
> > > Thank you very much in advance.
> > >
> > >
> > >
> > >
> >
> >
>
>
- Next message: John Loch: "Need help; NAV 2000 stopped launching; NAV 2004 can't finish install"
- Previous message: Joe Richards [MVP]: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- In reply to: Citimouse: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- Next in thread: Ace Fekay [MVP]: "Re: Windows 2003 member server with Windows 2000 Domain Controller"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|
