G
Guest
I have a laptop (running XP Pro SP2 fully patched) that takes about 2-3 mins
every time it boots when they are not connected to the domain (windows 2000
native domain, with main dc being 2003 std.). I notice there is a system
event error 5719 from netlogon saying "No domain controller is available for
domain <domain> due to the following. There are currently no logon servers
available to service the logon request." which occurs 2.5 mins after eventlog
has started. This makes me believe it is trying to find a domain controller
for 2.5 minutes. Is there a way to shorten the timeout for not finding a
domain controller. If there is, I'd prefer an answer that I could apply
through group policy.
every time it boots when they are not connected to the domain (windows 2000
native domain, with main dc being 2003 std.). I notice there is a system
event error 5719 from netlogon saying "No domain controller is available for
domain <domain> due to the following. There are currently no logon servers
available to service the logon request." which occurs 2.5 mins after eventlog
has started. This makes me believe it is trying to find a domain controller
for 2.5 minutes. Is there a way to shorten the timeout for not finding a
domain controller. If there is, I'd prefer an answer that I could apply
through group policy.