unable to login to domain after restart or shutdown

I am having this problem with XP machines in one range only.
Whenever they shutdown their PC's at night or restart during the day they're unable to login to the windows 2003 domain in the morning, it tells them that their user name or passwords are incorrect even if typed correctly. If they shut down their pc's and wait for 5 minutes then it works. The errors in the Windows XP machine's system events viewer are as shown below:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 10/17/2008
Time: 9:04:31 AM
User: N/A
Computer: MACHINE01
Description:
No Domain Controller is available for domain <domain> due to the following:
There are currently no logon servers available to service the logon request. .
Make sure that the computer is connected to the network and try again. If the problem persists, please contact your domain administrator.

-----------------------------------
Event Type: Warning
Event Source: W32Time
Event Category: None
Event ID: 18
Date: 10/17/2008
Time: 9:04:31 AM
User: N/A
Computer: MACHINE01
Description:
The time provider NtpClient failed to establish a trust relationship between this computer and the <domain.com> domain in order to securely synchronize time. NtpClient will try again in 15 minutes. The error was: The trust relationship between this workstation and the primary domain failed. (0x800706FD)

-----------------------------------------

Event Type: Error
Event Source: W32Time
Event Category: None
Event ID: 29
Date: 10/17/2008
Time: 9:04:31 AM
User: N/A
Computer: MACHINE01
Description:
The time provider NtpClient is configured to acquire time from one or more time sources, however none of the sources are currently accessible. No attempt to contact a source will be made for 14 minutes. NtpClient has no source of accurate time.

------------------------------------------

Event Type: Error
Event Source: Kerberos
Event Category: None
Event ID: 7
Date: 10/17/2008
Time: 9:04:33 AM
User: N/A
Computer: MACHINE01
Description:
The kerberos subsystem encountered a PAC verification failure. This indicates that the PAC from the client MACHINE01 in realm <DOMAIN.COM> had a PAC which failed to verify or was modified. Contact your system administrator.

I have synchronized their time with the DC, re-joined them to the domain but no luck.

I would very much appreciate if someone could help me !

I'd take a good look at the network interface and the protocols bound to it.


--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"integralli" wrote:
>
> I am having this problem with XP machines in one range only.
> Whenever they shutdown their PC's at night or restart during the day
> they're unable to login to the windows 2003 domain in the morning, it
> tells them that their user name or passwords are incorrect even if typed
> correctly. If they shut down their pc's and wait for 5 minutes then it
> works. The errors in the Windows XP machine's system events viewer are
> as shown below:
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5719
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> No Domain Controller is available for domain <domain> due to the
> following:
> There are currently no logon servers available to service the logon
> request. .
> Make sure that the computer is connected to the network and try again.
> If the problem persists, please contact your domain administrator.
>
> -----------------------------------
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 18
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient failed to establish a trust relationship
> between this computer and the <domain.com> domain in order to securely
> synchronize time. NtpClient will try again in 15 minutes. The error was:
> The trust relationship between this workstation and the primary domain
> failed. (0x800706FD)
>
> -----------------------------------------
>
> Event Type: Error
> Event Source: W32Time
> Event Category: None
> Event ID: 29
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient is configured to acquire time from one or
> more time sources, however none of the sources are currently accessible.
> No attempt to contact a source will be made for 14 minutes. NtpClient
> has no source of accurate time.
>
> ------------------------------------------
>
> Event Type: Error
> Event Source: Kerberos
> Event Category: None
> Event ID: 7
> Date: 10/17/2008
> Time: 9:04:33 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The kerberos subsystem encountered a PAC verification failure. This
> indicates that the PAC from the client MACHINE01 in realm <DOMAIN.COM>
> had a PAC which failed to verify or was modified. Contact your system
> administrator.
>
> I have synchronized their time with the DC, re-joined them to the
> domain but no luck.
>
> I would very much appreciate if someone could help me !
>
>
> --
> integralli
> ------------------------------------------------------------------------
> integralli's Profile: http://forums.techarena.in/members/integralli.htm
> View this thread: http://forums.techarena.in/server-ne...ng/1058089.htm
>
> http://forums.techarena.in
>

Hello integralli,

Have you enabled the policy "Always wait for the network at computer startup
and logon" in a GPO.

Best regards

Meinolf Weber
Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.
** Please do NOT email, only reply to Newsgroups
** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm


> I am having this problem with XP machines in one range only.
> Whenever they shutdown their PC's at night or restart during the day
> they're unable to login to the windows 2003 domain in the morning, it
> tells them that their user name or passwords are incorrect even if
> typed
> correctly. If they shut down their pc's and wait for 5 minutes then it
> works. The errors in the Windows XP machine's system events viewer are
> as shown below:
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5719
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> No Domain Controller is available for domain <domain> due to the
> following:
> There are currently no logon servers available to service the logon
> request. .
> Make sure that the computer is connected to the network and try again.
> If the problem persists, please contact your domain administrator.
> -----------------------------------
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 18
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient failed to establish a trust relationship
> between this computer and the <domain.com> domain in order to securely
> synchronize time. NtpClient will try again in 15 minutes. The error
> was:
> The trust relationship between this workstation and the primary domain
> failed. (0x800706FD)
> -----------------------------------------
>
> Event Type: Error
> Event Source: W32Time
> Event Category: None
> Event ID: 29
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient is configured to acquire time from one or
> more time sources, however none of the sources are currently
> accessible.
> No attempt to contact a source will be made for 14 minutes. NtpClient
> has no source of accurate time.
> ------------------------------------------
>
> Event Type: Error
> Event Source: Kerberos
> Event Category: None
> Event ID: 7
> Date: 10/17/2008
> Time: 9:04:33 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The kerberos subsystem encountered a PAC verification failure. This
> indicates that the PAC from the client MACHINE01 in realm <DOMAIN.COM>
> had a PAC which failed to verify or was modified. Contact your system
> administrator.
> I have synchronized their time with the DC, re-joined them to the
> domain but no luck.
>
> I would very much appreciate if someone could help me !
>
> http://forums.techarena.in
>

It seems to me the client time is different from the DC or lost the time so
that you can't logon until it synchronize. Next time when you shutdown the
computer and the relogon local computer check the time first. please post
back with the result.

--
Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com
"integralli" <integralli.3hkzfb@DoNotSpam.com> wrote in message
news:integralli.3hkzfb@DoNotSpam.com...
>
> I am having this problem with XP machines in one range only.
> Whenever they shutdown their PC's at night or restart during the day
> they're unable to login to the windows 2003 domain in the morning, it
> tells them that their user name or passwords are incorrect even if typed
> correctly. If they shut down their pc's and wait for 5 minutes then it
> works. The errors in the Windows XP machine's system events viewer are
> as shown below:
>
> Event Type: Error
> Event Source: NETLOGON
> Event Category: None
> Event ID: 5719
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> No Domain Controller is available for domain <domain> due to the
> following:
> There are currently no logon servers available to service the logon
> request. .
> Make sure that the computer is connected to the network and try again.
> If the problem persists, please contact your domain administrator.
>
> -----------------------------------
> Event Type: Warning
> Event Source: W32Time
> Event Category: None
> Event ID: 18
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient failed to establish a trust relationship
> between this computer and the <domain.com> domain in order to securely
> synchronize time. NtpClient will try again in 15 minutes. The error was:
> The trust relationship between this workstation and the primary domain
> failed. (0x800706FD)
>
> -----------------------------------------
>
> Event Type: Error
> Event Source: W32Time
> Event Category: None
> Event ID: 29
> Date: 10/17/2008
> Time: 9:04:31 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The time provider NtpClient is configured to acquire time from one or
> more time sources, however none of the sources are currently accessible.
> No attempt to contact a source will be made for 14 minutes. NtpClient
> has no source of accurate time.
>
> ------------------------------------------
>
> Event Type: Error
> Event Source: Kerberos
> Event Category: None
> Event ID: 7
> Date: 10/17/2008
> Time: 9:04:33 AM
> User: N/A
> Computer: MACHINE01
> Description:
> The kerberos subsystem encountered a PAC verification failure. This
> indicates that the PAC from the client MACHINE01 in realm <DOMAIN.COM>
> had a PAC which failed to verify or was modified. Contact your system
> administrator.
>
> I have synchronized their time with the DC, re-joined them to the
> domain but no luck.
>
> I would very much appreciate if someone could help me !
>
>
> --
> integralli
> ------------------------------------------------------------------------
> integralli's Profile: http://forums.techarena.in/members/integralli.htm
> View this thread: http://forums.techarena.in/server-ne...ng/1058089.htm
>
> http://forums.techarena.in
>

The Local Are Connection Properties are as follows:

Client for Microsoft Networks, File and Printer Sharing, QoS PAcket Scheduler, and TCP/IP protocol with proper configuration.


------------------------------------


The Group Policy "Always wait for the network at computer startup
and logon" is enabled already.
-------------------------------------
I logged in locally and checked the time with the DC time and it's synchronized.

But, the problem keeps coming up again. Do you have any other solution for this problem ? thank you in advance.

This really sounds like a hardware issue since having the pc off for five
minutes sorts it.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"integralli" wrote:
>
> The Local Are Connection Properties are as follows:
>
> Client for Microsoft Networks, File and Printer Sharing, QoS PAcket
> Scheduler, and TCP/IP protocol with proper configuration.
>
> The problem keeps coming up again. Do you have any other solution for
> this problem !
>
>
> --
> integralli
> ------------------------------------------------------------------------
> integralli's Profile: http://forums.techarena.in/members/integralli.htm
> View this thread: http://forums.techarena.in/server-ne...ng/1058089.htm
>
> http://forums.techarena.in
>

I would doubt that, because now all of the users in the same subnet are affected. Maybe half of the company has the same computer brand, and nobody complaints except for these guys.

Quote:

---

Originally Posted by Dave Patrick

This really sounds like a hardware issue since having the pc off for five
minutes sorts it.



--

Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect


"integralli" wrote:
>
> The Local Are Connection Properties are as follows:
>
> Client for Microsoft Networks, File and Printer Sharing, QoS PAcket
> Scheduler, and TCP/IP protocol with proper configuration.
>
> The problem keeps coming up again. Do you have any other solution for
> this problem !
>
>
> --
> integralli
> ------------------------------------------------------------------------
> integralli's Profile: http://forums.techarena.in/members/integralli.htm
> View this thread: http://forums.techarena.in/server-ne...ng/1058089.htm
>
> http://forums.techarena.in
>

---

I found the way to fix the problem. There was another machine having the same NetBIOS name on the network and that machine was a DC as well :( . The only difference was that this machine had it's domain ending with .net instead of .com and it was shutdown and turned on from time to time. So the users having this problem where on the same subnet with that DC and when they were trying login to the domain they were probably trying to authenticate with the "fake" DC. We just turned off that machine and since then the problem is gone.

cheers !

Quote:

---

Originally Posted by integralli

I would doubt that, because now all of the users in the same subnet are affected. Maybe half of the company has the same computer brand, and nobody complaints except for these guys.

---