I cannot join my company domain (windows 7)
hi, this is Young Lew. hope you are well.
i posted my trouble on MS answers and lead me to this forum since it is complex(?) matter.
Anyhow, I have upgraded my windows7 home premium to windows7 pro to use my laptop as my work computer. however, i am having very difficult time figuring out how.
here are what i have done so far. i went to computer-property to change the computer name/domain/workgroup settings. and, i followed "join domain or workgruop"wizard. however, i am getting following error.
The domain name "BMSLLC" might be a NetBIOS domain name. If this is the case, verify that the domain name is properly registered with WINS.
If you are certain that the name is not a NetBIOS domain name, then the following information can help you troubleshoot your DNS configuration.
The following error occurred when DNS was queried for the service location (SRV) resource record used to locate an Active Directory Domain Controller (AD DC) for domain "BMSLLC":
The error was: "DNS name does not exist."
(error code 0x0000232B RCODE_NAME_ERROR)
The query was for the SRV record for _ldap._tcp.dc._msdcs.BMSLLC
Common causes of this error include the following:
- The DNS SRV records required to locate a AD DC for the domain are not registered in DNS. These records are registered with a DNS server automatically when a AD DC is added to a domain. They are updated by the AD DC at
set intervals. This computer is configured to use DNS servers with the following IP addresses:
68.87.73.242
68.87.71.226
- One or more of the following zones do not include delegation to its child zone:
BMSLLC
. (the root zone)
i am a student in network so please give me detailed suggestions.
thank you in advance
regards,
February 17th, 2011 11:05am
Two things:
1. Make sure your DNS is pointing to your internal domain's DNS and not your IPS's DNS.
2. Use the fully qualified domain name (FQDN) and not the NetBios name.
Free Windows Admin Tool Kit Click here and download it now
February 17th, 2011 11:48am
Hi Bob
I have the same issue - different domain of course. I made the changes you stated. I looked up the IP address on a connected computer and added the appropriate DNS IP address to TCP-IP v4. I unchecked IP v6 and used the FQDN when joinin the computer.
Got the same error - only difference is that instead of the 68..x.x.x address it listed the IP address I manually entered. Any ideas?
MattMatt
February 22nd, 2011 11:09am
Hi Bob
You can disregard my request. I brought the computer to a different cube and found the issue. The newly formed cube I was in had it's network port wired incorrect. It was setup for VoIP and was going to the wrong network. The IP addressing
is very similar between the two networks (10.x.x.x) and I didnt recognize it until I moved to a different cube.
Hopefully my blunder here will help someone else in the future.
Thanks
MattMatt
Free Windows Admin Tool Kit Click here and download it now
February 22nd, 2011 11:17am