Web Hosting Talk







View Full Version : System Warning Question


Rivux
03-21-2007, 02:31 AM
Ive been getting the following System Warning every hour since I set the server up 5 days ago and Google hasn't been a lot of help in tracking down what it means and if I should be concerned. Im hoping someone here can point me in the right direction. Im running Windows 2003 Web Edition.


Event Type: Warning
Event Source: LSASRV
Event Category: SPNEGO (Negotiator)
Event ID: 40960
Date: 3/20/2007
Time: 7:45:33 PM
User: N/A
Computer: B02S08MR
Description:
The Security System detected an authentication error for the server DNS/ns.ufcom.com. The failure code from authentication protocol Kerberos was "There are currently no logon servers available to service the logon request.
(0xc000005e)".

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 5e 00 00 c0

plumsauce
03-21-2007, 11:22 PM
Try going to support.microsoft.com and search on the exact event id. That usually pulls something up from the KB. That's a funny looking server name though:

DNS/ns.ufcom.com.

If you are running dns in active directory mode and no active directory, that might do it :)

Rivux
03-22-2007, 12:46 PM
I did and it wasn't terribly helpful, which is why I came here.

plumsauce
03-23-2007, 04:25 AM
ok. try eventid.net

.

maxknight
03-24-2007, 05:44 AM
Hi,

Have you installed Active Directory on the server? Try removing Microsoft Client for Networks, rebooting and then readding that once again.

Also see if there is no communication block when the server tries to sync time. Try net time /set from the command prompt.

Rivux
04-02-2007, 10:03 PM
Hi,

Have you installed Active Directory on the server? Try removing Microsoft Client for Networks, rebooting and then readding that once again.

Also see if there is no communication block when the server tries to sync time. Try net time /set from the command prompt.

When I run that command I get "Could not locate a time-server".

kang
05-08-2007, 05:09 PM
it may be a bad configuration in your DNS. are you using windows DNS? and if so, it may be how your forwarders may be set.