Frame Corner

Frame Top

GSW Study Notes Home

GSW MCSE Notes Home Networking Essentials Notes NT Server 4.0 Notes NT Administration Notes

Module 19: Troubleshooting Resources

Troubleshooting Category

Category

Description

Action

Boot Computer will not correctly start selected OS. Boot from Windows NT boot disk or use Emergency Repair.
Devices Interrupt conflicts and SCSI problems report errors to Event log. - Error suspected, use Last Known Good before user logs on.

- Use WinMSD to check IRQ and device status.

Logon Inability to log on to system. - Log on using different account.

- if no accounts work, use Emergency Repair to restore accounts database.

Resource access Inability to access resources. - Log on using different account or server.

- Check spelling server and share name

File systems FAT, NTFS problems Run CHKDSK or reformat
Printing Problems with network printer. - Try different remote printer or user account.

- Remove and recreate printer.

Network Cable, adapter, IRQ conflict, protocol or external network problems. Use network cable analyzer, network protocol analyzer, or run diagnostics on adapter card.
Services Services don’t start. Check Event Viewer System log.
Event Viewer

Icon

Event type

Description

Stop sign Error Significant problem (service is not loaded).
! Warning Not necessarily significant but indicate possible future problems. ( example: low disk space)
i Information Infrequent but significant events; describe successful operations of drivers and services.
Key Success Audit Audited security access attempts that are successful.
lock Failure Audit Audited security access attempts that fail.
Event Log Files

System and Application logs can be viewed by all users, Security by Administrators only. Select Computer on Log menu in Event Viewer can be used to view log files from other Windows NT computers.

Log file

Description

System LOG
  • (Systemroot\System32\Config\Sysevent.evt)
  • Contains events logged by Windows NT system components, device drivers (determined by Windows NT and driver vendor)
Security LOG
  • (Systemroot\System32\Config\Secevent.evt)
  • Can contain valid and invalid logon attempts, as well as events related to resource use, such as creating, opening, or deleting files or other objects.
  • Auditing MUST be enabled for this log to work
  • Only the Administrator can view the log
Application LOG
  • (Systemroot\System32\Config\Appevent.evt)
  • Contains events logged by applications. Application vendors decide which events to monitor.
Enabling Security Logging

HKEY_LOCAL_MACHINE\CurrentControlSet\Control\Lsa\CrashOnAuditFail:

This entry directs OS to shut down abnormally, and then a blue screen when Audit log is full. Assures that no audited activities occur while system is unable to log them.

Type is REG_DWORD; two values:

Data value

Indicates

1

Stop if Audit log is full

2

Set by OS just before system crashes because of a full Audit log

Click Detail in View menu of Event Viewer, events are logged with greater detail. Event Detail dialog box shows following information;

  1. Date and time of event
  2. Event identification
  3. Text description of selected event

The usual extension of the Event Viewer files is .evt

Filtering

Arranging

Searching

Archiving Log Files

Windows NT Diagnostics
Performance Monior:

Important Counters:

Finding Memory Bottlenecks

Counters for Memory

 

Counter

Acceptable average range

Desirable value

Action

Pages/sec 0-20 Low Find causing process and add RAM
Available bytes > 4 MB High Find process using RAM and add RAM
Committed bytes Less than physical RAM Low Find process using RAM and add RAM
Pool Nonpaged Bytes Remain steady, no increase N/A Check for memory leak in application

Performance Monitor Exercise

Network Monitor
Configuring the System Recovery Utility
Top of Page Top of page

E-mail Me! Comments and suggestions? E-mail me at grantwilson21@yahoo.com
I'm sorry, but I can't answer specific network-related, or exam-related questions.
Last Updated: August 6, 2001 Grant Wilson, Edmonton, AB Canada