Computer Freezed - Net Logon Related?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have two computers set up to internet share and print share. The server is
a desktop on windows 2000 and the client is a notebook with wireless access,
also running windows 2000.

About a week or two ago the client computer was unable to access the print
share, although it can still access the Internet.

Around the same time, I began having problems where the desktop/server where
it would suddenly freeze on me totally (no CTRL ALT DEL, mouse, keyboard,
nothing!) after several minutes of use.

I tried checking many different hardware related possibilities, when I
noticed in my Error Log that each time, a minute at most before the freeze I
would receive the following two errors:

Event Type: Error
Event Source: NETLOGON
Event Category: None
Event ID: 3095
Date: 6/22/2005
Time: 5:26:40 PM
User: N/A
Computer: DESKTOP
Description:
This Windows NT computer is configured as a member of a workgroup, not
as a member of a domain. The Netlogon service does not need to run in
this configuration.

Event Type: Error
Event Source: Service Control Manager
Event Category: None
Event ID: 7024
Date: 6/22/2005
Time: 5:26:40 PM
User: N/A
Computer: DESKTOP
Description:
The Net Logon service terminated with service-specific error 3095.


Can anyone help me understand if this could be causing my freeze-ups, and
also how to fix it? Thanks!
 
That is not the cause of your lockups - those warnings are normal, but it may indicate that network activity is triggering it.

A lockup like this is almost always a hardware or system driver problem. First do an overall visual check in your server workstation
for obvious problems such as fans not working or cables and cards not firmly seated. Power supply and memory are also possibilites
for this symptom.

Otherwise I'd start with replacing the NIC in that box to see if that corrects the problem. Without getting too specific, let me
just say there are a number of lower-end network adapter chipsets which -- in combination with their drivers -- can cause all kinds
of fascinating and quite unpleasant problems like the one you're experiencing. Since there is a suggestion from the event log that
network activity might be the cause, it is a reasonable place to start.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
Back
Top