A
Andy Hunt
Hi,
Our Win2k server has suddenly developed DHCP problems I
believe as a result of a recent Win2k update. The result
is that every Monday morning, our few Windows XP Pro PC's
fail to logon. If I restart the server, they're fine until
the next Monday comes along.
The error messages in the log's are no's 1010,1014,1016 &
1037,1038,1039. Looking on the support site, it seemed the
Jet database was some how corrupted. I've just generated a
new database following the instructions in Q173396 and
there is now an error 1044 on the log. Also, in the DHCP
MMC the window is prompting for the server to be
authorised in Active Directory. This seems to fail as the
window does not update on refresh. If you run authorise
again, it tells you the server is already authorised.
Any ideas?
Cheers
Our Win2k server has suddenly developed DHCP problems I
believe as a result of a recent Win2k update. The result
is that every Monday morning, our few Windows XP Pro PC's
fail to logon. If I restart the server, they're fine until
the next Monday comes along.
The error messages in the log's are no's 1010,1014,1016 &
1037,1038,1039. Looking on the support site, it seemed the
Jet database was some how corrupted. I've just generated a
new database following the instructions in Q173396 and
there is now an error 1044 on the log. Also, in the DHCP
MMC the window is prompting for the server to be
authorised in Active Directory. This seems to fail as the
window does not update on refresh. If you run authorise
again, it tells you the server is already authorised.
Any ideas?
Cheers