|
|
|
|
|
|
|
|
|
|
Microsoft Windows NT Server
Basic Diagnostics
 |
|
|
|
|
|
Server
Upgrade Blues |
|
|
If you installed a full retail version of Windows NT Server over an NFR
version and still can't connect more than 10 clients, you need to make
a Registry edit. Open the HKEY_LOCAL_MACHINE
\System\CurrentControlSet\Services\LanManServer
\Parameters\Users key, double-click the Users value name (it's a
REG_DWORD type key), and change the value from 10 (Hex 0a) to Hex
FFFFFFFF and reboot. |
|
|
 |
|
|
Multiple Logons with NetExec |
|
|
A small utility called NetExec (http://www.detebe.org/diverse/netexec/NetExec_ENG.html)
lets you run different applications under different user logons. For
example, run your Internet browser on an account with no administration
privileges to prevent a virus from causing major damage. |
|
|
 |
|
|
Flash!-System BIOS Upgrades |
|
|
You should regularly check to see if your PC manufacturer is offering
system BIOS upgrades. Some problems with peripherals-such as PCI
latency controls-might be remedied with a newer version of the BIOS. |
|
|
 |
|
|
Connection Constraints |
|
|
The NFR (Not For Resale) version of Windows NT Server handles a maximum
of 10 NetBIOS connections at a time. If you need more than 10
connections, get the full retail edition. The connection limit does not
apply to TCP/IP connections. |
|
|
 |
|
|
Unlock Win9x Logons |
|
|
If you run C2CONFIG from the Resource Kit on your domain controller,
Windows 9x clients that log in might receive a "User not allowed to
log on at this computer" warning, and an error in the system log
(#533) might be generated. To avoid this, edit the domain controller's
Registry and delete the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\ Control\Lsa\CrashOnAuditFail key. |
|
|
 |
|
|
DHCP Distress |
|
|
The DHCPLOC.EXE utility in the Resource Kit helps administrators
determine what Dynamic Host Configuration Protocol (DHCP) servers are
available to clients on a particular network segment. But don't run
DHCPLOC.EXE on any computer that is a DHCP server; it might stop the
DHCP from responding to requests for IP addresses from DH CP clients. |
|
|
 |
|
|
Nuke NIC Error |
|
|
If you add a second network interface card (NIC) into your server and
get an "Error 20101" in the log, don't panic. This doesn't
prevent Remote Access Service (RAS) from working, and you can eliminate
the error by editing the Registry. Go to the KEY_LOCAL_MACHINE\SYSTEM
\CurrentControlSet\Services\Router\Interfaces\(X) key (X varies
depending on the number of NICs installed.) Look for the Enabled value
name of each key, a type REG_DWORD value. The valid entries are 0 for
disabled and 1 for enabled. When you find the Enabled value name that is
not set to 0 or 1, set it to 1. |
|
|
 |
|
|
FrontPage Server Snafu |
|
|
If
you've installed FrontPage Server Extensions on NT Server and you're
getting errors such as "Error 20002: cannot open file 'isapi stream
out' for writing," open this Registry key:
Hkey_Local_Machine\System
\CurrentControlSet\Services\W3SVC\Parameters. Check the Filter DLLs key
and remove any invalid paths. |
|
|
 |
|
|
Short Circuit Power Down Message |
|
|
Sick of that "It is now safe to turn off your computer"
message? Edit HKEY_LOCAL_MACHINE\Software\Microsoft\Windows NT
\CurrentVersion\Winlogon, and change PowerDownAfterShutdown (REG_SZ) to
1. This only works if your Hardware Abstraction Layer (HAL) supports it
(most Service Pack 3 HALs will.) |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|