bmiller79
asked on
Windows 2003 Server SBS stops accepting logins overnight, have to restart to log back in.
Please help! I have a client who has Windows 2003 Server SBS with SP2. Starting last thursday morning, no one could login to Exchange, so I restarted the server and then everyone could log back in. The same thing happened again Friday morning. A restart fixed it again. Guess what, this morning, the server was locked out again. This time I couldn't even log on as Administrator.
I checked the event viewer and there are loads of errors.
This error comes up far more than any of the others:
10/13/2008 8:40:44 AM KDC Error None 7 N/A SERVER The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was "username" and lookup type 0x0.
I can't figure out what the problem is to save my life. There are other errors as well, such as this one:
10/13/2008 5:20:47 AM W32Time Warning None 22 N/A SERVER The time provider NtpServer encountered an error while digitally signing the NTP response for peer 192.168.1.3:123. NtpServer cannot provide secure (signed) time to the client and will ignore the request. The error was: A device attached to the system is not functioning. (0x8007001F)
If anyone has any idea what could be causing these problems, please let me know. I have tried netdiag and everything passes.
Regards,
Brock
I checked the event viewer and there are loads of errors.
This error comes up far more than any of the others:
10/13/2008 8:40:44 AM KDC Error None 7 N/A SERVER The Security Account Manager failed a KDC request in an unexpected way. The error is in the data field. The account name was "username" and lookup type 0x0.
I can't figure out what the problem is to save my life. There are other errors as well, such as this one:
10/13/2008 5:20:47 AM W32Time Warning None 22 N/A SERVER The time provider NtpServer encountered an error while digitally signing the NTP response for peer 192.168.1.3:123. NtpServer cannot provide secure (signed) time to the client and will ignore the request. The error was: A device attached to the system is not functioning. (0x8007001F)
If anyone has any idea what could be causing these problems, please let me know. I have tried netdiag and everything passes.
Regards,
Brock
ASKER
That is not quite the error I am getting in the event log... Why would this have started all of a sudden? There were no changes to the network or PC's or any names...
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
ChiefIT,
Thank you for your detailed response! I will work on these items right away.
I am not sure that they are using group polcies at all??? But I'll check...
The only question I have is how would this start happening suddenly out of nowhere?? Is this possible? Or is something else going on to cause this? Again, I will try what you have recommended, but I wish I understood why it would happen in the first place. Do you know?
Also, since this is a small office, this is the only server, so of course it is the PDC, and it has about 11 clients. Its a pretty simple setup. I just don't see why all of a sudden it would start doing this?
I will let you know as soon as I have tried what you talked about it. If it works, I will GLADLY give you the points!
Thank you,
Brock
Thank you for your detailed response! I will work on these items right away.
I am not sure that they are using group polcies at all??? But I'll check...
The only question I have is how would this start happening suddenly out of nowhere?? Is this possible? Or is something else going on to cause this? Again, I will try what you have recommended, but I wish I understood why it would happen in the first place. Do you know?
Also, since this is a small office, this is the only server, so of course it is the PDC, and it has about 11 clients. Its a pretty simple setup. I just don't see why all of a sudden it would start doing this?
I will let you know as soon as I have tried what you talked about it. If it works, I will GLADLY give you the points!
Thank you,
Brock
ASKER
I am not able to find the snap-in to cehck on the Windows Time service group policies??
ASKER
I setup and installed symmtime and LMcheck. Everything is good there.
It is telling me I should install domain time. I have about half of the machines which are at least 1 minute out of sync. I have no idea how to install "domain time". I do see that they offer a product, but I really wanted to do this with out paying money, if possible.
I still can't find the snap-in for windows time group policy control.
Brock
It is telling me I should install domain time. I have about half of the machines which are at least 1 minute out of sync. I have no idea how to install "domain time". I do see that they offer a product, but I really wanted to do this with out paying money, if possible.
I still can't find the snap-in for windows time group policy control.
Brock
In my opinion, it is easiest to use GPMC (Group Policy Management Console) to administer Group policy.
Once downloaded, you can install the snapin to the MMC console or run it from administrative tools.
http://www.microsoft.com/downloads/details.aspx?familyid=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&displaylang=en
In GPMC, you will find the default domain policy that I think will be the one you have to edit for the group policy changes. IP 192.168.1.3:123 is the IP address that your PDCe is trying to synch with. If that is the IP of your server, the server is trying to synch with itself. This is what is telling me there is a Group policy, as the default domain policy, pointing your clients and servers to the PDCe for time synchronization. The PDCe can't synch with itself for time or you will recieve errors.
Once downloaded, you can install the snapin to the MMC console or run it from administrative tools.
http://www.microsoft.com/downloads/details.aspx?familyid=0a6d4c24-8cbd-4b35-9272-dd3cbfc81887&displaylang=en
In GPMC, you will find the default domain policy that I think will be the one you have to edit for the group policy changes. IP 192.168.1.3:123 is the IP address that your PDCe is trying to synch with. If that is the IP of your server, the server is trying to synch with itself. This is what is telling me there is a Group policy, as the default domain policy, pointing your clients and servers to the PDCe for time synchronization. The PDCe can't synch with itself for time or you will recieve errors.
http://support.microsoft.com/default.aspx?scid=kb;en-us;321044
is this what is happening more or less try the resolution