Where is netsetup.log

Also, there were no weird DNS record conflicts for the server in particular. The Netsetup. The netsetup. A typical netsetup. There is a wealth of information that can be gathered from the netsetup. In great detail it will show all the steps completed and tried with the domain join operation. 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. To reproduce this problem and test whether you have fixed it , open a command prompt and run the following command.

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. 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:.

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 client computer must be able to exchange traffic with the domain controller on several different TCP and UDP ports These ports include:. 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.

Renaming seems to have done the trick. While I have used hyphens in PC names in the past, removing it from the name seems to have done the trick. Strange development Seems the hyphen wasn't the actual problem. Tried joining another couple computers, without hyphens, and they wouldn't join. Setup the join with a change in the computer name including the hyphen and they joined It sounds like an issue with the Netbios name that gets fixed when you change the computer name. Hyphens should not cause an issue.

In the "Identification" block, the "Credentials" block must be correct. The "Domain" and "Username" tags are joined to create the account that the desktop will login to the domain as in order to create the Machine Account. The account must exist and be a domain administrator or a service account with sufficient privileges to create Machine Account objects. The desktop logs in to and joins this domain using the credentials described above earlier. It must not refer to the default Computers container.

If you want your desktops to appear in the default Computers container for your domain, you must delete the entire MachineObjectOU line. So to get the default, which you can't specify, you must not have the line at all. Was this page helpful? Thank you! Sorry to hear that. Name Name is required. Email Email address is required. Close Submit. Featured Products. Need more help? Product issues. Open or view cases Chat live. Other support options.

Share this page.