XP does not like Win2k Server Domain HELP!!!

  • Thread starter Thread starter BZ
  • Start date Start date
B

BZ

We have a windows 2000 server pro server set up with
domain access for all users in our network. we have two
Dell Desktop PCs that came with windows XP. These two PCs
continually have print/network issues which I believe are
just side effects of the real problem. both machines have
the following errors repeatedly, on a daily basis, and
this is ONLY the XP machines.

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 7/19/2003
Time: 6:08:47 PM
User: N/A
Computer: COMPUTER
Description:
The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible.
Data:
0000: e5 03 00 00 å...

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 7/19/2003
Time: 4:39:18 PM
User: N/A
Computer: COMPUTER
Description:
No Windows NT or Windows 2000 Domain Controller is
available for domain PULSE. The following error occurred:
There are currently no logon servers available to service
the logon request.
Data:
0000: 5e 00 00 c0 ^..À

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 7/22/2003
Time: 3:21:45 AM
User: NT AUTHORITY\SYSTEM
Computer: COMPUTER
Description:
Windows cannot determine the user or computer name. Return
value (1722).

Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 15
Date: 7/22/2003
Time: 8:36:05 AM
User: N/A
Computer: TFANTEXPN
Description:
Automatic certificate enrollment for local system failed
to contact the active directory (0x8007054b). The
specified domain either does not exist or could not be
contacted.
Enrollment will not be performed.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 7/21/2003
Time: 11:11:17 AM
User: NT AUTHORITY\SYSTEM
Computer: TFANTEXPN
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.


~~~~~~~~~~~~~~~~~~~
These four errors occur frequently, especially the last
two.

Per the microsoft knowledge base I have hard coded the DNS
(our ISP DNS) on the XP machine. I have also taken other
steps such as turning on NetBIOS over tcp/ip and
unchecking "register this address in DNS" and the issue
continues on. I have reformatted the XP Machine,
reinstalled our normal software which include acrobat
reader, MS office, and all microsoft windows updates, and
the issue continues on. ONLY with the XP machines!! =O

as i said before, any and all help would be greatly
appreciated. thanks!
 
We have a windows 2000 server pro server set up with
domain access for all users in our network. we have two
Dell Desktop PCs that came with windows XP. These two PCs
continually have print/network issues which I believe are
just side effects of the real problem. both machines have
the following errors repeatedly, on a daily basis, and
this is ONLY the XP machines.

Per the microsoft knowledge base I have hard coded the DNS
(our ISP DNS) on the XP machine.
Click to expand...

I think this is your problem right here. If these XP machines are logging
into the domain, you need to enter the IP address of your domain
controller, not of your ISP's DNS server. I'm assuming you're runing a 2000
Active Directory domain, which means you should have DNS running on the
domain controllers. Also, you have joined the computers to the domain.
 
Make SURE you set the AD server as the DNS server on the WinXP machines.

--
Mike Matheny


We have a windows 2000 server pro server set up with
domain access for all users in our network. we have two
Dell Desktop PCs that came with windows XP. These two PCs
continually have print/network issues which I believe are
just side effects of the real problem. both machines have
the following errors repeatedly, on a daily basis, and
this is ONLY the XP machines.

Event Type: Warning
Event Source: w32time
Event Category: None
Event ID: 54
Date: 7/19/2003
Time: 6:08:47 PM
User: N/A
Computer: COMPUTER
Description:
The Windows Time Service was not able to find a Domain
Controller. A time and date update was not possible.
Data:
0000: e5 03 00 00 å...

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 7/19/2003
Time: 4:39:18 PM
User: N/A
Computer: COMPUTER
Description:
No Windows NT or Windows 2000 Domain Controller is
available for domain PULSE. The following error occurred:
There are currently no logon servers available to service
the logon request.
Data:
0000: 5e 00 00 c0 ^..À

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1000
Date: 7/22/2003
Time: 3:21:45 AM
User: NT AUTHORITY\SYSTEM
Computer: COMPUTER
Description:
Windows cannot determine the user or computer name. Return
value (1722).

Event Type: Error
Event Source: AutoEnrollment
Event Category: None
Event ID: 15
Date: 7/22/2003
Time: 8:36:05 AM
User: N/A
Computer: TFANTEXPN
Description:
Automatic certificate enrollment for local system failed
to contact the active directory (0x8007054b). The
specified domain either does not exist or could not be
contacted.
Enrollment will not be performed.

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1054
Date: 7/21/2003
Time: 11:11:17 AM
User: NT AUTHORITY\SYSTEM
Computer: TFANTEXPN
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.


~~~~~~~~~~~~~~~~~~~
These four errors occur frequently, especially the last
two.

Per the microsoft knowledge base I have hard coded the DNS
(our ISP DNS) on the XP machine. I have also taken other
steps such as turning on NetBIOS over tcp/ip and
unchecking "register this address in DNS" and the issue
continues on. I have reformatted the XP Machine,
reinstalled our normal software which include acrobat
reader, MS office, and all microsoft windows updates, and
the issue continues on. ONLY with the XP machines!! =O

as i said before, any and all help would be greatly
appreciated. thanks!
 
In a nutshell, for some reason, the XP machines are
unable to reach the domain controllers. Many
possibilities. The XP boxes may not be 'locating' or
resolving the resources properly. Whatever it is, if the
2000 workstations have no trouble, it does sound related
to either the XP configs or to the physical method of
connection to the network. Here are some ideas--without
more info, its tough to say what the problem is.

BTW, There isn't a Windows 2000 Server PRO technically
speaking. If you're REALLY running Win2k PRO (the
desktop version of Win2k), You may be limited to 10
connections.

Sounds like either a DNS issue, as the other gentlemen
have pointed out. Could be a negotiations issue. Can
you resolve your domain controllers' names? There are
many tools to troubleshoot active directory participation-
-many on the XP cd in the SUPPORT tools section. Namely,
look for NETDIAG or DCDIAG. Run Netdiag /V for a fairly
thorough test of the domain. You may not have DCDIAG--
support tools for WinXP pro don't seem to include it
anymore--you can copy it the EXE from your Server Windows
2000 support tools to run.

Are these XP Pro systems? Home edition cannot
participate as domain members.

Could also be something about actual network
connectivity. Do the XP systems MAINTAIN a connection
properly to the ethernet? Perhaps a long PING test to
another device will show that the connections are
dropping--could be due to a mismatch of speed/and/or
duplex configuration. Maybe the XP machines are going
into power save/sleep/hibernation mode that deactivates
the nics, and RESUME is not waking them properly.

Another remote possibility, pertaining to the differences
of XP and 2000, XP uses a logon optimization that doesn't
REQUIRE it to speak to a domain controller before
allowing you to logon. There is a policy adjustment that
can be made to correct this. Win2000, by default
requires DC communications BEFORE you can login. If your
Domain Policy is NOT being passed onto the XP machines,
perhaps they aren't getting the 'modification' to tell
them to connect to the DC everytime.

Do you have any other protocols on the wire?

How is everything connecting to your ISP? Do you have a
router? Are you getting your IP addresses from a DHCP
server?

Bob
 
Back
Top