Troubleshooting Page
Updated: 10/10/2003 Version 1.00
A. Things to check for issues encountered when joining the machine
to the domain:
- Run ipconfig /all and verify that the correct TCP/IP settings are
being used. The machine should be configured to use ns1.berkeley.edu
and ns2.berkeley.edu for DNS.
- NTLM version level - Verify that the machine is set to use NTLM
v2 by following the instructions here.
- The NetBIOS network API (also loosely called the "NetBIOS protocol")
is not necessary to join the domain, but a separate service called
the TCP/IP NetBIOS Helper service must be running. Otherwise,
you will get the error message: "Network
Location Cannot be Reached" Error Message When You Try to Join
a Domain".
- Open the netsetup.log file in %systemroot%\debug. This file contains
the log of events during domain join/disjoin.
- Configure auditing and check the event logs after trying to join
the domain.
- Run netdiag.exe and check the report in the netdiag.log file.
B. Things to check for user logon issues:
- Check the machine account attributes using the ADSI Edit Console.
Follow the instructions listed in this document: HOW
TO: Verify Machine Account Attributes. Make the appropriate changes,
if needed, using the ADSI Edit Console.
- Make sure the correct CalNet ID and passphrase are being used for
logon. See the FAQ
for tips on user logon.
- Check the Kerberos name mapping for the CalNetAD shadow account.
Refer to the Kerberos
User Setup document for instructions.
|
