Re: Windows 2003 member server with Windows 2000 Domain Controller

From: Ace Fekay [MVP] (PleaseSubstituteMyActualFirstName&LastNameHere_at_hotmail.com)
Date: 01/04/04 

Date: Sun, 4 Jan 2004 14:46:07 -0500

In news:3ff75dfc$1@news.starhub.net.sg,
Citimouse <citimousemeow@hotmail.com> posted their thoughts, then I offered
mine
> 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.

Wow, this got around to many unnecessary news groups. Wonder why the
multiple crosspost, such as the applications, registry or security groups?

My thing on this is pretty much agreeing with the other posters. Follow
whatever means you need to get the machine updated to the latest SP and
hotfixes for your own benefit. 

-- 
Regards,
Ace
Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.
Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
-- 
=================================

Relevant Pages

  • RE: HELP: Exchange is losing connectivity with PDC and DNS
    ... EMAIL and PDC1, BDC1 and WINS server. ... Event Type: Error ... Event Source: MSExchangeAL ... If this computer is a domain controller for the specified domain, ...
    (microsoft.public.windows.server.dns)
  • Re: Please help refresh my memory on AD DC
    ... Also when I promoted this Server 2008 box it did somthing that was not normal. ... DC would the only logon be a Domain logon or would the option to logon ... to Logon locally I would use the admin account of the Server 2003 machine. ... If you promote a server to Domain controller, there is no renaming of the ...
    (microsoft.public.windows.server.active_directory)
  • Re: Windows 2003 member server with Windows 2000 Domain Controller
    ... If anyone is having a Windows 2003 member server with a Windows 2000 ... Windows cannot obtain the domain controller name for your computer ... There are currently no logon servers available to service the logon ...
    (microsoft.public.win2000.security)
  • Re: Windows 2003 member server with Windows 2000 Domain Controller
    ... > Windows 2003 server, both registered the same event as mentioned below. ... > Event Source: NETLOGON ... > There are currently no logon servers available to service the logon ... > If this computer is a domain controller for the specified domain, ...
    (microsoft.public.win2000.security)
  • Re: SBS and TS
    ... we noticed that we were getting problems where the NIC on the SBS server was showing no IP address even in DOS and yet we could pint the server. ... Event Source: NTDS Replication ... Active Directory could not use DNS to resolve the IP address of the source domain controller listed below. ...
    (microsoft.public.windows.server.sbs)