cant connect windows 7 pro to sbs 2003 server - error code 0x0000232B

[mffk]

I have not a great deal of network experience and am trying to connect a workstation with windows 7 pro to sbs 2003 server at my workplace. I have connected workstations with XP pro with no problem by changing membership of the computer name from workgroup to Domain.

Windows 7 Pro will not allow the change from workgoup to domain. I have tried setting IP Address both using Obtain IP Address automatically, and also setting them manually in network properties. This works for XP Pro using IP addresses for gateway and server from ipconfig /all. I have tried setting IP Addresses in 7 Pro but it does not work.

Error message is as follows:

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 "MIRACLEFLIGHTSFORKIDS.local":
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.MIRACLEFLIGHTSFORKIDS.local
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:
192.168.1.1
- One or more of the following zones do not include delegation to its child zone:
MIRACLEFLIGHTSFORKIDS.local
local

 

[VistaKing]

mffk welcome to SevenForums


See if this will help

:ar: Unable to join 7 Pro to SBS 2003 domain - Microsoft Community

 

[Shadowjk]

I have not a great deal of network experience and am trying to connect a workstation with windows 7 pro to sbs 2003 server at my workplace. I have connected workstations with XP pro with no problem by changing membership of the computer name from workgroup to Domain.

Windows 7 Pro will not allow the change from workgoup to domain. I have tried setting IP Address both using Obtain IP Address automatically, and also setting them manually in network properties. This works for XP Pro using IP addresses for gateway and server from ipconfig /all. I have tried setting IP Addresses in 7 Pro but it does not work.

Error message is as follows:

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 "MIRACLEFLIGHTSFORKIDS.local":
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.MIRACLEFLIGHTSFORKIDS.local
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:
192.168.1.1
- One or more of the following zones do not include delegation to its child zone:
MIRACLEFLIGHTSFORKIDS.local
local

Can you please follow this tutorial and post back your ipconfig settings on the Windows 7 machine.

http://www.sevenforums.com/network-sharing/144365-network-posting-tips.html

You need to make sure that the DNS server settings on each workstation goes to the server when joining Active Directory. For example on my Windows Server 2012 machine I have the primary DNS as the server IP and the secondary DNS as my router.



May I also ask, do you know where your DHCP server is installed if any?

Many Thanks,
Josh!

 

[chev65]

I have not a great deal of network experience and am trying to connect a workstation with windows 7 pro to sbs 2003 server at my workplace. I have connected workstations with XP pro with no problem by changing membership of the computer name from workgroup to Domain.

Windows 7 Pro will not allow the change from workgoup to domain. I have tried setting IP Address both using Obtain IP Address automatically, and also setting them manually in network properties. This works for XP Pro using IP addresses for gateway and server from ipconfig /all. I have tried setting IP Addresses in 7 Pro but it does not work.

Error message is as follows:

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 "MIRACLEFLIGHTSFORKIDS.local":
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.MIRACLEFLIGHTSFORKIDS.local
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:
192.168.1.1
- One or more of the following zones do not include delegation to its child zone:
MIRACLEFLIGHTSFORKIDS.local
local

Besides using the correct DNS servers it may be required that this machine or User name needs to be added to the Active Directory of the Server in order to be added to the Domain.

It may also require that you make adjustments to the Local Security Policy, specifically the lanman server settings and the encryption on the Windows 7 machine needs adjustments before it can be joined to an older server such as Windows Server 03.

The following link will show you the adjustments to make on the Windows 7 machine.
Solved W2K3 Server can access W8 W8 computer cant see W2K server

 

[mffk]

sorry for late reply, changed settings in Local Policies settings as suggested including disabling 128 bit encryption. Rebooted, same problem. Any more suggestions about settings that may need changing in Admin tools? The new user name I created for windows 7 pro machine work on a XP Pro machine that connects to sbs 2003 no problem.

 

[chev65]

sorry for late reply, changed settings in Local Policies settings as suggested including disabling 128 bit encryption. Rebooted, same problem. Any more suggestions about settings that may need changing in Admin tools? The new user name I created for windows 7 pro machine work on a XP Pro machine that connects to sbs 2003 no problem.

For this particular error message try this on the workstation, add ONLY the domain internal DNS server on the NIC and nothing else. Then run ipconfig /flushdns and ipconfig /register DNS on the client and try again to join it.

OR, If you are trying to add a Windows 7 machine to a domain over a WAN link and are getting the 0x0000232B DNS error, try adding the IP address of your DC as a WINS server.

There is also an update that may help.
http://support.microsoft.com/kb/926505

 

[mffk]

ipconfig settings

ipconfig /all of sbs2003 server is:


xp pro ipconfig /all is:


iopconfig /all windows 7 pro that is not recognizing domain is:


Using the Properties dialog box of network settings I have set the network ip address settings of default gateway & the preferred server to 192.168.1.1 of windows 7 pro machine. Still get the same error message.

I have also tried ipconfig /flushdns & ipconfig /registerdns. This changed all the ip addresses and no one could connect to the server until I set the server machine addresses back to that as posted above, then all the windows xp pro workstations could once again connect to domain MIRACLEFLIGHTSFORKIDS.local, but not the windows 7 pro machine. Any clues as what I could try next?

 

[mffk]

ipconfig /flushdns command

I have another question, as i mentioned I am inexperienced with networking so I may have done the ipconfig /flushdns & registerdns on the wrong machine - I did it on the server machine, not the workstation. Is this why everyone was bumped off the server? Or put another way, if I do a ipconfig /flushdns and /registerdns on the workstation / client will it only affect that machine or will it take down the server again?

 

[Shadowjk]

The noticeable issue that you have here is that the DNS server of the machines is not going to the server. On each machine please set the following DNS servers by following this tutorial - http://www.sevenforums.com/tutorials/15037-dns-addressing-how-change-windows-7-a.html

Preferred DNS Server:192.168.1.6

Alternative DNS Server:192.168.1.1

   Note

You may choose to not add the alternative DNS server however please be advised that unless your 2003 server has NAT routing protocol installed then the devices joining the domain will not be able to connect to the internet. If you want them to connect to the internet I would strongly recommend placing the above alternate DNS server to the machines

Also could you please make sure that your Windows 2003 Server has a static IP address by following the same tutorial but setting the following IP address stack (Use the IP addresses in the image):



After setting that simply press ok and then close all over prompts. Now please retry connecting devices to the domain

Hope This Helps,
Josh!

 

[Shadowjk]

I have another question, as i mentioned I am inexperienced with networking so I may have done the ipconfig /flushdns & registerdns on the wrong machine - I did it on the server machine, not the workstation. Is this why everyone was bumped off the server? Or put another way, if I do a ipconfig /flushdns and /registerdns on the workstation / client will it only affect that machine or will it take down the server again?

Do not worry about the flush DNS since this would most likely not resolve your issue. Based on the evidence you have presented the above solution should fix your issue and allow the machines to join the domain

Josh

 

[mffk]

latest attempt to connect

after ipconfig /flushdns and ipconfig /registerdns on client machine, and adding alternate dns server I still cannot connect. i get the following error message:


current network settings on client machine:

 

[mffk]

after flushdns and register dns, and setting alternate dns server to 192.168.1.6 i still cannot connect

 

[Shadowjk]

You need to change your DNS servers around so that 192.168.1.6 is the preferred one and that 192.168.1.1 is the alternate DNS server

Josh