I am having problems with computers not being able to find the domain controller during bootup. If I wait 1 minute or so after the computer has boot up then I'm able to login to my roaming profile but this is not always the case. Sometimes I have to wait longer. While waiting for a couple of minutes may work for users trying to login to their profile, this delay causes problem for services that need authentication from the DC. All our client workstation is Windows XP and this particular server is Windows 2003 server. At first I thought it was the DC server that is not responding fast enough for the request of the client but I installed ethereal network monitor to the DC and captured the traffic. I found that the client computer is not even showing up in the traffic that ethereal has captured. I'm guessing that this means the computer already have a problem before it even tries to contact the DC server. My question is, is there a way to capture the traffic in the computer that is having this problem during bootup so I can better diagnoze what the problem is?

Here's the application event log:

Event Type: Error
Event Source: Userenv
Event Category: None
Event ID: 1053
Date: 11/25/2005
Time: 10:41:25 AM
User: NT AUTHORITY\SYSTEM
Computer: myComputer
Description:
Windows cannot determine the user or computer name. (The specified domain either does not exist or could not be contacted. ). Group Policy processing aborted.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

Here's the security event log:

Event Type: Failure Audit
Event Source: Security
Event Category: Policy Change
Event ID: 615
Date: 11/25/2005
Time: 10:41:26 AM
User: NT AUTHORITY\NETWORK SERVICE
Computer: myComputer
Description:
IPSec Services: IPSec Services failed to get the complete list of network interfaces on the machine. This can be a potential security hazard to the machine since some of the network interfaces may not get the protection as desired by the applied IPSec filters. Please run IPSec monitor snap-in to further diagnose the problem.


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


Here is the system event log:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 5719
Date: 11/25/2005
Time: 10:41:23 AM
User: N/A
Computer: myComputer
Description:
This computer was not able to set up a secure session with a domain controller in domain myDCName due to the following:
There are currently no logon servers available to service the logon request.
This may lead to authentication problems. Make sure that this computer is connected to the network. If the problem persists, please contact your domain administrator.

ADDITIONAL INFO
If this computer is a domain controller for the specified domain, it sets up the secure session to the primary domain controller emulator in the specified domain. Otherwise, this computer sets up the secure session to any domain controller in the specified domain.

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

Hi ljCharlie,

QUOTE

I installed ethereal network monitor to the DC and captured the traffic

You did it right... note that ethereal must be installed and running on the server, I guess. This handy tool has pointed a lot of problems on my home network (and I was able to solve them).

Sorry if I can not give you more clues on this, but I am not so skilled in Windows Server... (my home network is XP and 98SE based).

Maybe some other members can add something here ?

Chris

Is the computer part of the correct domain?

is the computer in active directory?

Am i right in saying that you cannot even logon to the domain,