SimonUK
asked on
Error 5719 NETLOGON - default domain
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
Source: NETLOGON
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?
Thanks
Simon
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
Source: NETLOGON
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?
Thanks
Simon
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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?
Simon
Same solution, do you think?
Simon
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.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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...
Simon
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...
Simon
ASKER
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
Simon
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
Simon
ASKER
Any comment on the "domain DOMAIN" bit though - that's what's giving me the biggest confusion!
Simon