Logo
programming4us
programming4us
programming4us
programming4us
Home
programming4us
XP
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Windows Phone
 
programming4us
Windows 7

The Process of Troubleshooting Network Problems (part 4) - How to Troubleshoot Joining or Logging on to a Domain

- How To Install Windows Server 2012 On VirtualBox
- How To Bypass Torrent Connection Blocking By Your ISP
- How To Install Actual Facebook App On Kindle Fire
11/4/2012 6:20:19 PM

5. How to Troubleshoot Joining or Logging on to a Domain

Administrators often encounter problems when joining a computer running Windows to an AD DS domain. Additionally, users might receive error messages about domain controllers being unavailable when trying to log on to their computer with a domain account.

The first step in troubleshooting domain join problems is to click Details in the Computer Name/Domain Changes dialog box to view the error information. For example, the error shown in Figure 4 indicates that the DNS server does not have a DNS entry for the domain controller. If you want to view this error information after closing the Computer Name/Domain Changes dialog box, open the %WinDir%\Debug\Dcdiag.txt log file.

Figure 4. In most cases, Windows will reveal the source of the problem in the detailed error message.


5.1. How to Analyze the NetSetup.Log file

If the Computer Name/Domain Changes dialog box does not reveal the source of the problem, view the %WinDir%\Debug\Netsetup.log file. This log details the process of joining a domain as well as the details of any problems encountered. For best results, compare a log file generated on a computer that successfully joined your domain to a computer that failed to join the domain. For example, the following entry indicates that the computer successfully located the hq.contoso.com domain controller (note the return value of 0x0).

-----------------------------------------------------------------
NetpValidateName: checking to see if 'HQ.CONTOSO.COM' is valid as type 3 name
NetpCheckDomainNameIsValid [ Exists ] for 'HQ.CONTOSO.COM' returned 0x0
NetpValidateName: name 'HQ.CONTOSO.COM' is valid for type 3
-----------------------------------------------------------------

					  

The following entry indicates that the computer failed to locate the hq.fabrikam.com domain controller (note the return value of 0x54b).

-----------------------------------------------------------------
NetpValidateName: checking to see if 'hq.fabrikam.com' is valid as type 3 name
NetpCheckDomainNameIsValid for hq.fabrikam.com returned 0x54b, last error is 0x3e5
NetpCheckDomainNameIsValid [ Exists ] for 'hq.fabrikam.com' returned 0x54b
-----------------------------------------------------------------

					  

If you see this type of name resolution failure during an unattended setup but you are able to manually join a domain, verify that clients are receiving a valid DHCP configuration. Specifically, verify that the DNS server addresses are correct and that the identified DNS servers contain service location (SRV) resource records for your domain controllers in the format _ldap._tcp.dc._msdcs.DNSDomainName.

If you see an error resembling the following, it indicates that the computer was previously joined to a domain using the same computer name but a different account. Joining the domain might fail because the administrative user account does not have permission to modify the existing account. To work around the problem, change the computer name, have the computer account deleted from the domain, or use the original user account to join the computer to the domain.

NetpManageMachineAccountWithSid: NetUserAdd on '\\hq.contoso.com' for
'43L2251A2-55$' failed: 0x8b0
04/06 06:36:20 SamOpenUser on 3386585 failed with 0xc0000022

If you see an error resembling the following, it indicates that the client could not establish a Server Message Block (SMB) session to the domain controller to manage the client computer account. One possible cause of this issue is missing WINS registrations for a domain controller.

NetUseAdd to \\ntdev-dc-02.ntdev.corp.microsoft.com\IPC$ returned 53

To reproduce this problem (and test whether you have fixed it), open a command prompt and run the following command.

net use \\<server from above>\ipc$ /u:<account used for join> <password>

To determine whether the edition of Windows supports joining a domain, search for the keyword NetpDomainJoinLicensingCheck (most recent entries are at the bottom of the log file). If the ulLicenseValue is anything other than 1, it indicates that the edition of Windows cannot join a domain. To join a domain, a computer must be running the Windows 7 Professional, Windows 7 Enterprise, or Windows 7 Ultimate operating systems. The following shows a log file entry for a computer running a supported version of Windows (as indicated by ulLicenseValue=1).

NetpDomainJoinLicensingCheck: ulLicenseValue=1, Status: 0x0

5.2. How to Verify Requirements for Joining a Domain

To join or log on to a domain successfully, you must meet several different requirements. When troubleshooting a problem joining a domain, verify each of these requirements:

  • The client computer must be able to resolve the IP address for a domain controller In most enterprise networks, client computers receive an IP address assignment from a DHCP server, and the DHCP server provides addresses for AD DS–enabled DNS servers that can resolve the domain controller IP address. If another DNS server is configured, you should update the client computer's IP configuration to use an AD DS–enabled DNS server. If this is not possible, you can add two records to your existing DNS server that resolve to a domain controller's IP address:

    • The _ldap._tcp.dc._msdcs.DNSDomainName SRV resource record, which identifies the name of the domain controller that hosts the AD DS domain. DNSDomainName is the DNS name of the AD DS domain the computer is attempting to join.

    • A corresponding address (A) resource record that identifies the IP address for the domain controller listed in the _ldap._tcp.dc._msdcs.DNSDomainName SRV resource record.

  • The client computer must be able to exchange traffic with the domain controller on several different TCP and UDP ports These ports include:

    • TCP port 135 for RPC traffic

    • TCP port 389 and UDP port 389 for LDAP traffic

    • TCP port 636 for LDAP over SSL traffic

    • TCP port 3268 for LDAP Global Catalog (GC) traffic

    • TCP port 3269 for LDAP GC SSL traffic

    • TCP port 53 and UDP port 53 for DNS traffic

    • TCP port 88 and UDP port 88 for Kerberos traffic

    • TCP port 445 for SMB (also known as CIFS) traffic


  • The administrator must have privileges to add a computer to a domain Administrators who add a computer to a domain must have the Add Workstations To Domain user right.

  • The computer must be running Windows 7 Professional, Windows 7 Enterprise, or Windows 7 Ultimate Windows 7 Starter, Windows 7 Home Basic, and Windows 7 Home Premium operating systems cannot join a domain.

6. How to Troubleshoot Network Discovery

With Network Discovery, users can browse shared network resources from the Network window. On private networks, this is convenient because users can connect to resources without knowing the names of other computers on the network. On public networks, however, Network Discovery is a security concern because it will announce the presence of the computer on the public network and users might use it to connect to a potentially malicious computer.

For these reasons, Network Discovery is enabled on private networks but disabled on public networks by default. When connected to an AD DS domain, Network Discovery is controlled by Group Policy settings but is disabled by default. Therefore, if the Network window does not display shared resources on the local network, it is almost certainly because Network Discovery is disabled. To remedy this, follow these steps (all of which require administrator privileges and can increase your computer's exposure to security attacks):

  1. Verify that the Function Discovery Provider Host service is running.

  2. Verify that Windows Firewall has exceptions enabled for Network Discovery.

  3. Change the type of network from public to private. Alternatively, you can manually enable Network Discovery by opening the Network And Sharing Center window and enabling Network Discovery.

Other -----------------
- Microsoft Excel 2010 : Analyzing Data by Using Descriptive Statistics
- Microsoft Excel 2010 : Finding Optimal Solutions by Using Solver
- Microsoft Excel 2010 : Varying Your Data to Get a Desired Result by Using Goal Seek
- Microsoft Word 2010 : Working with Outlines - Working with Master Documents
- Microsoft Word 2010 : Working with Outlines - Creating a Standard Outline
- Using Microsoft OneNote 2010 with Other Programs : OneNote Integration with Internet Explorer
- Using Microsoft OneNote 2010 with Other Programs : A Quick Note About Interface Differences, OneNote Integration with Windows
- Conquering Malicious Software : Conquering Spyware with Windows Defender
- Parental Controls and Family Safety : Using Parental Controls from Windows Live
- Parental Controls and Family Safety : Using the Built-In Parental Controls
 
 
Top 10
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 2) - Wireframes,Legends
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Finding containers and lists in Visio (part 1) - Swimlanes
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Formatting and sizing lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Adding shapes to lists
- Microsoft Visio 2013 : Adding Structure to Your Diagrams - Sizing containers
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 3) - The Other Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 2) - The Data Properties of a Control
- Microsoft Access 2010 : Control Properties and Why to Use Them (part 1) - The Format Properties of a Control
- Microsoft Access 2010 : Form Properties and Why Should You Use Them - Working with the Properties Window
- Microsoft Visio 2013 : Using the Organization Chart Wizard with new data
- First look: Apple Watch

- 3 Tips for Maintaining Your Cell Phone Battery (part 1)

- 3 Tips for Maintaining Your Cell Phone Battery (part 2)
programming4us programming4us
Popular tags
Microsoft Access Microsoft Excel Microsoft OneNote Microsoft PowerPoint Microsoft Project Microsoft Visio Microsoft Word Active Directory Biztalk Exchange Server Microsoft LynC Server Microsoft Dynamic Sharepoint Sql Server Windows Server 2008 Windows Server 2012 Windows 7 Windows 8 windows Phone 7 windows Phone 8
programming4us programming4us
 
programming4us
Natural Miscarriage
programming4us
Windows Vista
programming4us
Windows 7
programming4us
Windows Azure
programming4us
Windows Server
programming4us
Game Trailer