Error 5719 NETLOGON - default domain

Posted on 2004-08-03
Last Modified: 2008-01-09
Hi all

Repost in correct category!

Running an NT4 server with two Windows 98 clients that log into the domain in the usual way and process login scripts, and one XP Home machine that has a compatible IP address and accesses network shares using the NET USE command.

All is seemingly fine except for random server reboots, about every 36-48 hours - apparently at night but with no discernable trigger.

I've got a strange error in event viewer on the server, that appears every 15 minutes ALL THE TIME.

User: N/A
Event ID: 5719
Type:  ERROR
Category: None
Computer: (the correct name of the server)

No Windows NT domain controller is available for domain DOMAIN.  (This event is expected and can be ignored when booting with the 'No Net' hardware profile.)  The following error occurred: There are currently no logon servers available to service the logon request.

Note that the error actually contains the domain DOMAIN - and this is not the name of our domain!

All I can think is that a machine with a default setting is doing something I don't know about.  I've physically unplugged the XP Home machine - no change.  I checked for RestrictAnonymous in registry as per a similar post but it's not there.  I think the key must be this default DOMAIN but I can't find any references to that in any machines including the server.  PCAnywhere is running for remote support but it always has been.  I notice IIS is running in the task list and I don't know why - but again, I'm not aware of this being installed recently.

Any ideas please?


Question by:SimonUK

Accepted Solution

syn_ack_fin earned 200 total points
ID: 11706913
Lots of things can cause this. See the following link for MS Articles:

Good Luck

Author Comment

ID: 11707079
Thanks - I've had a look - as you say, lots of possibilties.

Any comment on the "domain DOMAIN" bit though - that's what's giving me the biggest confusion!


Assisted Solution

shad0_cheng earned 200 total points
ID: 11712165
WARNING: If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

To resolve this problem, increase the MaxDgramBuffering value from 128 KB to 256 KB:
Start Registry Editor (Regedt32.exe).
Locate the following key in the registry:

On the Edit menu, click Add Value, and then add the following information:
Value Name: MaxDgramBuffering
Data Type: REG_DWORD
Value: 0x40000

Quit Registry Editor.
Restart the Netlogon service (you may have to restart the computer).
NOTE: If you are using Regedit instead of Regedt32 to modify the registry, either
right-click Parameters, click New, and then click REG_DWORD -or-

click New on the Edit menu, and then click REG_DWORD
and then add the new registry key information.

Extracted From KB 310339 (Original Info from
Netscaler Common Configuration How To guides

If you use NetScaler you will want to see these guides. The NetScaler How To Guides show administrators how to get NetScaler up and configured by providing instructions for common scenarios and some not so common ones.


Author Comment

ID: 11713060
I saw that solution when I was searching but it seems to relate to 2000 Server and this is NT4.

Same solution, do you think?


Expert Comment

ID: 11714995
I would say so, besides if this key is not implemented in NT4 then it would simply have no effect, doesn't hurt to try.

Assisted Solution

michaelheister earned 100 total points
ID: 11718327
I have had a similar problem in the past.  You can use a program called NetDom (from the NT Resource Kit CD) to check and reset the SID between the server and the workstations.  Also, make sure all the computers' clocks are set to within a couple of minutes of the server (check the date and the time zone as well) and then remove them from the domain and re-add them.

Author Comment

ID: 11753612
OK, thanks.

I'm away from the location for a bit so if no-one minds I'll post back with what I tried in a few weeks...


Author Comment

ID: 12109558
Awarded points as fairly as possible.  In the end we replaced the server because it was having other problems which may or may not have been connected.

When I have time I'll look over the old one again and try the suggestions and post back if there are any results.

Thanks all


Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

For many of us, the  holiday season kindles the natural urge to give back to our friends, family members and communities. While it's easy for friends to notice the impact of such deeds, understanding the contributions of businesses and enterprises i…
I had an issue with InstallShield not being able to use Computer Browser service on Windows Server 2012. Here is the solution I found.
After creating this article (, I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…
In this tutorial you'll learn about bandwidth monitoring with flows and packet sniffing with our network monitoring solution PRTG Network Monitor ( If you're interested in additional methods for monitoring bandwidt…

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question