Event viewer errors, roaming profile problems XPsp2, W2k domain


G

GW

I am running a Windows 2000 Domain and using roaming profiles. After joining
an XP_SP2 client machine to the network, I noticed some event viewer System
log errors on the XP client machine. The errors pertain to Net Logon Service
and W32Time. The net logon error states: 5719 No domain controller is
available for domain due to the following error-There are currently no logon
servers to service the log on request. The W32Time error states: 29 The
time provider NTPClient is configured to aquire time from one or more time
sources, however one or more sources are not currently accessible. No
attempt to contact a source will be attempted for 15 minutes. NTPClient has
not source of accurate time. One thing I notice is after the computer boots
up to the welcome screen, if I immediately log on, the roaming profile will
not load from the server. But, if I wait a minute or so to log on, then the
roaming profile will load. While waiting that minute, the 'hour glass' will
come up for a second, likes it through loading the OS or maybe loading
services? And, if I wait for the hour glass to show then log on, I have no
trouble loading the roaming profile, consistently. If I log off and log back
on, then it will load the roaming profile. It's only after restarts or
shutdowns and startups do I have the errors and have to wait to log on to
load the profile. After about 15 minutes after logging on, and if the
roaming profile loaded correctly, the event viewer System Log will show the
the W32Time has synchronized with the domain controller. Also, I'm using
Group Policies as well, and two logon scripts that execute at logon but not
startup. I'm not sure if this a domain controller issue or WinXP client
issue. My Win2k clients do not display these events when they log on to the
domain.
 
Ad

Advertisements

L

Lanwench [MVP - Exchange]

GW said:
I am running a Windows 2000 Domain and using roaming profiles. After
joining an XP_SP2 client machine to the network, I noticed some event
viewer System log errors on the XP client machine. The errors
pertain to Net Logon Service and W32Time. The net logon error
states: 5719 No domain controller is available for domain due to the
following error-There are currently no logon servers to service the
log on request. The W32Time error states: 29 The time provider
NTPClient is configured to aquire time from one or more time sources,
however one or more sources are not currently accessible. No attempt
to contact a source will be attempted for 15 minutes. NTPClient has
not source of accurate time. One thing I notice is after the computer
boots up to the welcome screen, if I immediately log on, the roaming
profile will not load from the server. But, if I wait a minute or so
to log on, then the roaming profile will load. While waiting that
minute, the 'hour glass' will come up for a second, likes it through
loading the OS or maybe loading services? And, if I wait for the
hour glass to show then log on, I have no trouble loading the roaming
profile, consistently. If I log off and log back on, then it will
load the roaming profile. It's only after restarts or shutdowns and
startups do I have the errors and have to wait to log on to load the
profile. After about 15 minutes after logging on, and if the roaming
profile loaded correctly, the event viewer System Log will show the
the W32Time has synchronized with the domain controller. Also, I'm
using Group Policies as well, and two logon scripts that execute at
logon but not startup. I'm not sure if this a domain controller
issue or WinXP client issue. My Win2k clients do not display these
events when they log on to the domain.

Yep. This is a known issue. Enable "always wait for network at computer
startup and logon" via group policy.
 
G

GW

I tried the Enable "always wait for network at computer
startup and logon" via group policy and it worked, the roaming profile now
works if the user logs in right away. But, I still see the 5719 Netlogon
Event and the 29 W32Time event in the event viewer system log. Is this just
part of the "known issue" that isn't resolved or do I need to enable
something else or can this be resolved? Thanks for your help.
 
Ad

Advertisements

L

Lanwench [MVP - Exchange]

GW said:
I tried the Enable "always wait for network at computer
startup and logon" via group policy and it worked, the roaming
profile now works if the user logs in right away. But, I still see
the 5719 Netlogon Event and the 29 W32Time event in the event viewer
system log. Is this just part of the "known issue" that isn't
resolved or do I need to enable something else or can this be
resolved? Thanks for your help.

Hmmm - I'd run an rsop.msc and see what you find.
Microsoft.public.windows.group_policy might be a good place to post this
bit. Also check out www.eventid.net.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top