Hello!
I am having an issue with one out of three Win XP workstations in our office, the rest of them (about 60) are WIN2k Pro
and working fine
The problem is: everytime XP pro is booting up, logging on to a domain and receiving ip address from DHCP, 1054 and 5719 are being logged by
the event viewer, so basically GPO is not loading
I tried few things to resolve it, checked DNS and all the setting are fine, i looked at fast logon optimization on the XP workstation and turned it off by enabling policy, last thing i did i checked our switch for Spanning Tree protcol and it was not enabled
after all of that i still receiving errors if connecting using DHCP, if i use static ip i do not have a problem--- no errors
I f anybody experienced something close to this i will appreciate your input
thanks in advance
Anton
"Anton" <anonymous@discussions.microsoft.com> wrote in message
news:2630FD02-07A9-425C-B39B-4B4D05F82333@microsoft.com...
> Hello!
> I am having an issue with one out of three Win XP workstations in our
office, the rest of them (about 60) are WIN2k Pro
> and working fine
> The problem is: everytime XP pro is booting up, logging on to a domain and
receiving ip address from DHCP, 1054 and 5719 are being logged by
> the event viewer, so basically GPO is not loading
> I tried few things to resolve it, checked DNS and all the setting are
fine, i looked at fast logon optimization on the XP workstation and turned
it off by enabling policy, last thing i did i checked our switch for
Spanning Tree protcol and it was not enabled
> after all of that i still receiving errors if connecting using DHCP, if i
use static ip i do not have a problem--- no errors
> I f anybody experienced something close to this i will appreciate your
input
> thanks in advance
> Anton
>
>
Looking at the error messages, this is what I dig up:
Event ID 1054:
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.
Event ID 5719: Description: No Windows NT or Windows 2000 Domain Controller
is available for domain Domain. The following error occurred:
There are currently no logon servers available to service the logon request.
I'm 99.999999999999% sure you have DNS misconfigured.
Failure to find a domain controller is essentially a name resolution issue.
Try to ping the domain controller by IP address, NetBIOS name and FQDN:
eg:
If DNS is misconfigured, XP will spend a lot of time waiting for it to
timeout before it tries using legacy NT4 sytle NetBIOS.
( Which may or may not work. )
1) Ensure that the XP clients are all configured to point to the local
DNS server which hosts the AD domain. That will probably be the
win2k server itself.
They should NOT be pointing an an ISP's DNS server.
An 'ipconfig /all' on the XP box should reveal ONLY the domain's
DNS server.
( you should use the DHCP server to push out the local DNS server
address. )
2) Ensure DNS server on win2k is configured to permit dynamic updates.
3) Ensure the win2k server points to itself as a DNS server.
4) For external ( internet ) name resolution, specify your ISP's DNS server
not on the clients, but in the 'forwarders' tab of the local win2k DNS
server.
On the DNS server, if you cannot access the 'Forwarders' and 'Root Hints'
tabs because they are greyed out, that is because there is a root zone (".")
present on the DNS server. You MUST delete this root zone to permit the
server to forward unresolved queries to yout ISP or the root servers:
>-----Original Message-----
>"Anton" <anonymous@discussions.microsoft.com> wrote in
message
>news:2630FD02-07A9-425C-B39B-4B4D05F82333@microsoft.com...
>> Hello!
>> I am having an issue with one out of three Win XP
workstations in our
>office, the rest of them (about 60) are WIN2k Pro
>> and working fine
>> The problem is: everytime XP pro is booting up, logging
on to a domain and
>receiving ip address from DHCP, 1054 and 5719 are being
logged by
>> the event viewer, so basically GPO is not loading
>> I tried few things to resolve it, checked DNS and all
the setting are
>fine, i looked at fast logon optimization on the XP
workstation and turned
>it off by enabling policy, last thing i did i checked our
switch for
>Spanning Tree protcol and it was not enabled
>> after all of that i still receiving errors if
connecting using DHCP, if i
>use static ip i do not have a problem--- no errors
>> I f anybody experienced something close to this i will
appreciate your
>input
>> thanks in advance
>> Anton
>>
>>
>
>Looking at the error messages, this is what I dig up:
>
>Event ID 1054:
>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.
>
>Event ID 5719: Description: No Windows NT or Windows 2000
Domain Controller
>is available for domain Domain. The following error
occurred:
>There are currently no logon servers available to service
the logon request.
>
>I'm 99.999999999999% sure you have DNS misconfigured.
>Failure to find a domain controller is essentially a name
resolution issue.
>
>Try to ping the domain controller by IP address, NetBIOS
name and FQDN:
>eg:
>
> ping 192.168.0.200
> ping bigdogdc01
> ping bigdogdc01.mydomain.com
>
>( obviously using your own IP addresses, names and FQDN. )
>If the 3rd one ( FQDN ) fails, then you for sure have a
DNS problem.
>
>Here's a description of how DNS *must* be configured...
>
>XP differs from previous versions of windows in that it
uses
>DNS as it's primary name resolution method for finding
domain
>controllers:
>
>How Domain Controllers Are Located in Windows XP
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;314861
>
>If DNS is misconfigured, XP will spend a lot of time
waiting for it to
>timeout before it tries using legacy NT4 sytle NetBIOS.
>( Which may or may not work. )
>
>1) Ensure that the XP clients are all configured to point
to the local
> DNS server which hosts the AD domain. That will
probably be the
> win2k server itself.
> They should NOT be pointing an an ISP's DNS server.
> An 'ipconfig /all' on the XP box should reveal ONLY
the domain's
> DNS server.
>
> ( you should use the DHCP server to push out the local
DNS server
> address. )
>
>2) Ensure DNS server on win2k is configured to permit
dynamic updates.
>
>3) Ensure the win2k server points to itself as a DNS
server.
>
>4) For external ( internet ) name resolution, specify
your ISP's DNS server
> not on the clients, but in the 'forwarders' tab of the
local win2k DNS
>server.
>
>On the DNS server, if you cannot access the 'Forwarders'
and 'Root Hints'
>tabs because they are greyed out, that is because there
is a root zone (".")
>present on the DNS server. You MUST delete this root
zone to permit the
>server to forward unresolved queries to yout ISP or the
root servers:
>
>HOWTO: Remove the Root Zone (Dot Zone)
>http://support.microsoft.com/default.aspx?kbid=298148
>
>The following articles may assist you in setting up DNS
correctly:
>
>Setting Up the Domain Name System for Active Directory
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;237675
>HOW TO: Configure DNS for Internet Access in Windows 2000
>http://support.microsoft.com/default.aspx?scid=kb;en-
us;300202
>
>--
>Best Regards,
>Ron Lowe
>MS-MVP Windows Networking
>
>Thank you Ron for quick response!!!
>I do understand it sounds like a DNS issue and
>.I checked Dns once again according to your advise and it
looks good, besides two other WinXP workstations are
working fine i initiated ping sessions to domain
controller by ip address, Netbious name and FQDN name and
all came out fine, so it does not look like it is a DNS
issue, please let me know if we can try something
once again thanks a lot for your help
best regards
Anton
>
Windows XP PRO logon errors 1054 and 5719 
Linear Mode
