Re: user logon

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Todd J Heron (todd_heron_no_spam_at_hotmail.com)
Date: 09/28/04

Next message: Todd J Heron: "Re: AD replication?"
Previous message: anoni: "page/sec"
In reply to: Scott Micale: "Re: user logon"
Next in thread: Scott Micale: "Re: user logon"
Reply: Scott Micale: "Re: user logon"
Messages sorted by: [ date ] [ thread ]

Date: Tue, 28 Sep 2004 12:59:22 -0400

The dcdiag results tell me that the DNS forward lookup zone on the server is
either not set to allow dynamic updates, or that the DNS server is not set
to register itself in the zone under it's NIC properties, or something else
is wrong. Run an ipconfig /all and post the results. Check you event
viewer as well.

-- 
Todd J Heron, MCSE
Windows 2003/2000/NT
"Scott Micale" <hrm_admin@news.postalalias> wrote in message
news:%23wmpfWXpEHA.3424@TK2MSFTNGP11.phx.gbl...
> I tried a DCDIAG just to see what it came back with and I wonder if this
has
> anything to do with my problem.
>
> DC Diagnosis
>
> Performing initial setup:
>    Done gathering initial info.
>
> Doing initial non skippeable tests
>
>    Testing server: Default-First-Site-Name\HARTTOOL
>       Starting test: Connectivity
>          ......................... HARTTOOL passed test Connectivity
>
> Doing primary tests
>
>    Testing server: Default-First-Site-Name\HARTTOOL
>       Starting test: Replications
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From SKYNET to HARTTOOL
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 10:49.44.
>             The last success occurred at 2004-08-18 19:48.31.
>             986 failures have occurred since the last success.
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [SKYNET] DsBind() failed with error 1722,
>          The RPC server is unavailable..
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From NT_SERVER to HARTTOOL
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 10:59.36.
>             The last success occurred at 2004-08-19 13:48.39.
>             2472 failures have occurred since the last success.
>             The guid-based DNS name
> 1eecced9-7b86-4b50-a815-5c26414f350c._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [NT_SERVER] DsBind() failed with error 1722,
>          The RPC server is unavailable..
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From BRAIN to HARTTOOL
>             Naming Context: CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 11:41.49.
>             The last success occurred at 2004-08-19 13:48.39.
>             5156 failures have occurred since the last success.
>             The guid-based DNS name
> 0b692c1e-6566-436a-be49-0d02669e5135._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [BRAIN] DsBind() failed with error 1722,
>          The RPC server is unavailable..
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From BRAIN to HARTTOOL
>             Naming Context: CN=Schema,CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 10:49.44.
>             The last success occurred at 2004-08-19 13:48.39.
>             968 failures have occurred since the last success.
>             The guid-based DNS name
> 0b692c1e-6566-436a-be49-0d02669e5135._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From NT_SERVER to HARTTOOL
>             Naming Context: CN=Schema,CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 10:49.44.
>             The last success occurred at 2004-08-19 13:48.39.
>             968 failures have occurred since the last success.
>             The guid-based DNS name
> 1eecced9-7b86-4b50-a815-5c26414f350c._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From SKYNET to HARTTOOL
>             Naming Context: CN=Schema,CN=Configuration,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 10:49.44.
>             The last success occurred at 2004-08-18 19:48.31.
>             986 failures have occurred since the last success.
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From SKYNET to HARTTOOL
>             Naming Context: DC=ForestDnsZones,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 09:21.58.
>             The last success occurred at 2004-08-18 19:48.31.
>             12 failures have occurred since the last success.
>             The guid-based DNS name
> 177f2bc1-7971-47e6-8cfb-1b36a2f1f4d5._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          [Replications Check,HARTTOOL] A recent replication attempt
failed:
>             From NT_SERVER to HARTTOOL
>             Naming Context: DC=ForestDnsZones,DC=hrm,DC=lan
>             The replication generated an error (8524):
>             The DSA operation is unable to proceed because of a DNS lookup
> failu
> re.
>             The failure occurred at 2004-09-28 11:45.02.
>             The last success occurred at 2004-08-19 13:48.39.
>             2360 failures have occurred since the last success.
>             The guid-based DNS name
> 1eecced9-7b86-4b50-a815-5c26414f350c._msdcs.
> hrm.lan
>             is not registered on one or more DNS servers.
>          ......................... HARTTOOL passed test Replications
>       Starting test: NCSecDesc
>          ......................... HARTTOOL passed test NCSecDesc
>       Starting test: NetLogons
>          ......................... HARTTOOL passed test NetLogons
>       Starting test: Advertising
>          ......................... HARTTOOL passed test Advertising
>       Starting test: KnowsOfRoleHolders
>          Warning: NT_SERVER is the Schema Owner, but is not responding to
DS
> RPC
>  Bind.
>          [NT_SERVER] LDAP connection failed with error 58,
>          The specified server cannot perform the requested operation..
>          Warning: NT_SERVER is the Schema Owner, but is not responding to
> LDAP B
> ind.
>          Warning: NT_SERVER is the Domain Owner, but is not responding to
DS
> RPC
>  Bind.
>          Warning: NT_SERVER is the Domain Owner, but is not responding to
> LDAP B
> ind.
>          ......................... HARTTOOL failed test KnowsOfRoleHolders
>       Starting test: RidManager
>          ......................... HARTTOOL passed test RidManager
>       Starting test: MachineAccount
>          ......................... HARTTOOL passed test MachineAccount
>       Starting test: Services
>             RPCLOCATOR Service is stopped on [HARTTOOL]
>          ......................... HARTTOOL failed test Services
>       Starting test: ObjectsReplicated
>          ......................... HARTTOOL passed test ObjectsReplicated
>       Starting test: frssysvol
>          ......................... HARTTOOL passed test frssysvol
>       Starting test: kccevent
>          An Error Event occured.  EventID: 0xC0000466
>             Time Generated: 09/28/2004   11:40:28
>             (Event String could not be retrieved)
>          ......................... HARTTOOL failed test kccevent
>       Starting test: systemlog
>          ......................... HARTTOOL passed test systemlog
>
>    Running enterprise tests on : hrm.lan
>       Starting test: Intersite
>          ......................... hrm.lan passed test Intersite
>       Starting test: FsmoCheck
>          Warning: DcGetDcName(GC_SERVER_REQUIRED) call failed, error 1355
>          A Global Catalog Server could not be located - All GC's are down.
>          ......................... hrm.lan failed test FsmoCheck
>
> Hope this sheds some light for anyone.
>
>
> "Scott Micale" <hrm_admin@news.postalalias> wrote in message
> news:O9edCjWpEHA.3244@tk2msftngp13.phx.gbl...
> >I have a 2003 server that is really doing something weird.  I can only
log
> >on to my server as the admin user that was originally setup.  If I try
and
> >log in as a different user I get a message saying, "The system could not
> >log you on.  Make sure your username and domain are correct, then type
your
> >password again.  Letters in password must be typed using the correct
case."
> >I can add a new machine to the domain fine, but as soon as I try and log
> >into the domain I get the message, "The system cannot log you on now
> >because the domain HT is not available."  I can ping the DC fine from
that
> >machine if I log in as a local user, so I know the communication is
> >working.  I have tried 2 XP Pro machines and both are doing the same
thing.
> >Is there something misconfigured on my server?
> >
> > -- 
> > Scott Micale
> > Director of IT
> > 330-877-3631
> >
> >
>
>

Next message: Todd J Heron: "Re: AD replication?"
Previous message: anoni: "page/sec"
In reply to: Scott Micale: "Re: user logon"
Next in thread: Scott Micale: "Re: user logon"
Reply: Scott Micale: "Re: user logon"
Messages sorted by: [ date ] [ thread ]

Relevant Pages

Re: Backup domain controller issues...
... Should the forward lookup zone type on the backup DC actually be set as ... and your remaining problem is DHCP. ... > I don't think it's a bug, but you could try restarting the DHCP Server ... >> well or will just the DNS server names suffice??? ...
(microsoft.public.backoffice.smallbiz2000)
Re: Domain Setup Question
... I can setup the AD intergrated DNS server and use DHCP to setup all my ... AD intergrated DNS server cannot resolve. ... > server would have a forward lookup zone of allfurpetgrooming.com. ...
(microsoft.public.windowsxp.network_web)
Re: Domain Setup Question
... ALLFURPETGROOMING.COM and that the server will be named OFFICE. ... people connecting from the Internet will not access your DNS server. ... >> server would have a forward lookup zone of allfurpetgrooming.com. ...
(microsoft.public.windowsxp.network_web)
Re: Event ID 40960 and 40961.
... Sounds to me like this DNS server is set to query external DNS servers ... > name, can do dynamic update, even in the Reverse Lookup Zone. ...
(microsoft.public.windows.server.networking)
Re: About nslookup
... Success for the previous query. ... is there any way for me to cache the query in my own DNS server so ... >> I have set the IP address in the Forward lookup zone and reverse ...
(microsoft.public.win2000.dns)