Sign in with
Sign up | Sign in
Your question

server 2003 logon issues NT 4.0 domain

Tags:
  • Domain
  • Computers
  • Windows
Last response: in Windows 2000/NT
Share
Anonymous
March 28, 2005 5:38:12 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

When trying to logon to NT 4.0 domain I receive the following message:


Windows cannot connect to the domain, either because the domain
controller is down or otherwise unavailable, or because your computer
account was not found.

The event log gives me this error:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3210
Date: 3/28/2005
Time: 4:05:56 PM
User: N/A
Computer: OPSVR

Description:
This computer could not authenticate with \\OPDC, a Windows domain
controller for domain opcenter, and therefore this computer might deny
logon requests. This inability to authenticate might be caused by
another computer on the same network using the same name or the
password for this computer account is not recognized. If this message
appears again, contact your system administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0 "..À

My domain controllers are up but it looks like this server has been
bumped off the domain. I've tried to remove the computer account in
server manager and rejoin the domain but still no luck. Thanks for any
help.

More about : server 2003 logon issues domain

Anonymous
March 28, 2005 8:45:33 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

By default W2k3 encrypts secure channel data which isn't
supported by NT. Open the local security policy and disable
the member secure digitally encrypt or sign secure data always.

<rsl315@gmail.com> wrote in message news:
When trying to logon to NT 4.0 domain I receive the following message:


Windows cannot connect to the domain, either because the domain
controller is down or otherwise unavailable, or because your computer
account was not found.

The event log gives me this error:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3210
Date: 3/28/2005
Time: 4:05:56 PM
User: N/A
Computer: OPSVR

Description:
This computer could not authenticate with \\OPDC, a Windows domain
controller for domain opcenter, and therefore this computer might deny
logon requests. This inability to authenticate might be caused by
another computer on the same network using the same name or the
password for this computer account is not recognized. If this message
appears again, contact your system administrator.

For more information, see Help and Support Center at
http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 22 00 00 c0 "..À

My domain controllers are up but it looks like this server has been
bumped off the domain. I've tried to remove the computer account in
server manager and rejoin the domain but still no luck. Thanks for any
help.
Anonymous
March 29, 2005 9:34:06 AM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

This setting was already set to disabled. Thanks anyway.
Related resources
Anonymous
March 29, 2005 1:28:18 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Then it's one of the following:


Make sure that the following settings are configured as shown.

RestrictAnonymous and RestrictAnonymousSam:
Network access: Allow anonymous SID/Name translation ENABLED
Network access: Do not allow anonymous enumeration of SAM accounts
DISABLED
Network access: Do not allow anonymous enumeration of SAM accounts and
shares DISABLED
Network access: Let Everyone permissions apply to anonymous users
ENABLED
Network access: Named pipes can be accessed anonymously ENABLED
Network access: Restrict anonymous access to Named Pipes and shares
DISABLED


LM Compatibility:
Network security: LAN Manager authentication level "LM & NTLM
responses" or "Send LM & NTLM - use NTLMV2 session security if negotiated"

SMB Signing, SMB Encrypting, or both:
Microsoft network client: Digitally sign communications (always)
DISABLED
Microsoft network client: Digitally sign communications (if server
agrees) ENABLED
Microsoft network server: Digitally sign communications (always)
DISABLED
Microsoft network server: Digitally sign communications (if client
agrees) ENABLED
Domain member: Digitally encrypt or sign secure channel data (always)
DISABLED
Domain member: Digitally encrypt secure channel data (when it is
possible) ENABLED
Domain member: Digitally sign secure channel data (when it is
possible) ENABLED
Domain member: Require strong (Windows 2000 or later) session key
DISABLED


Reference:
http://support.microsoft.com/default.aspx?scid=kb;en-us;889030


<rsl315@gmail.com> wrote in message news:
> This setting was already set to disabled. Thanks anyway.
>
Anonymous
March 29, 2005 2:53:37 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

It turned out to be the last one. Thanks for all your help.
Anonymous
March 29, 2005 6:48:20 PM

Archived from groups: microsoft.public.windowsnt.domain (More info?)

Your welcome.. Thank you for the update..

<rsl315@gmail.com> wrote in message news:
> It turned out to be the last one. Thanks for all your help.
>
!