Slow logon when not connected to domain

[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.

 

[Robert L [MS-MVP]]

I would try to increase the MaxDgramBuffering value first.

Event ID Troubleshooting Event ID 5719 - The system cannot log you on now because the domain "name" ... Also, Event viewer shows Event ID: 5719. No Windows NT or Windows 2000 Domain ...
www.chicagotech.net/wineventid.htm


Computer Account In client, you may receive Event ID 5719: "No Windows NT or Windows 2000 Domain Controller is available for domain Domain. The following error occurred: ...
www.chicagotech.net/computeraccounterrors.htm



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
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.

 

[Guest]

To clarify, the computer will not be logging into the domain, but is using a
domain account, we don't have a VPN set up for remote users. What I want to
be able to do is to decrease the amount of time the computer looks for a DC,
because there is not going to be a DC available.

Thanks