Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, October 2, 2017 8:13 PM
I have a server running 2012 r2 configured to be a RDS terminal server. It is configured as a member server to a domain controller. I can see the terminal server in all servers on the domain controller, but I can't see the servers on the connected client computer. The user can connect to active directory on the domain controller. I have domain network and sharing setup on all servers and the client computer. I am getting this error on the domain controller:
The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:
Adapter Name : {816F4CED-B157-42C1-9FF0-F1AF6AC1622F}
Host Name : ascts
Primary Domain Suffix : ascnyc2.org
DNS server list :
192.168.1.9
Sent update to server : <?>
IP Address(es) :
192.168.1.13
The reason the system could not register these RRs was because the update request it sent to the DNS server timed out. The most likely cause of this is that the DNS server authoritative for the name it was attempting to register or update is not running at this time.
You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.
Do I need to add a DNS entry for the RDS terminal for the TS access to work? If I do have to create a DNS entry for the terminal server, where do I make the DNS configuration on the terminal server or the domain controller? I would like to add, that I am just learning how to make server configurations. Any assistance will be greatly appreciated.
Thank you.
All replies (12)
Monday, October 2, 2017 9:43 PM
Hi Check if dynamic updates on you DNS zone is enabled this could solve the issue with the problem mentioned
Tuesday, October 3, 2017 3:45 AM
Yes, I will try that when I get in tomorrow. Thanks.
Tuesday, October 3, 2017 1:53 PM
I configured dynamic updates on the domain controller, which is my DNS server as well. It did not work, I was not able to log in to the RDP terminal server. Before I configured the dynamic updates, when I looked at network places on the client computer, I could see the client computer. After changing to dynamic updates, I couldn't see anything in network places on the client computer. When I switched the dynamic updates back to none, I could at least see the client computer in network places. As I said, I am totally new to server configurations, but let me tell you something I noticed. I haven't been able to get this configuration to work, so I was just trying different things. Last week I made a DNS entry on the DNS server(my domain controller--192.168.1.9), for the RDP terminal server. When I tried to connect to the terminal server from the client computer, it still did not work, but I could see both serversthe domain controller and the terminal server and the client machine in network places of the client machine. is it possible that I do need to create a DNS entry for the terminal server on the DNS server? I would like to try and fix the errors I'm getting one by one if you can assist me. Thank you very much.
These are the errors I'm getting on all servers. ASCNYC-DC03 is the domain controller.
Wednesday, October 4, 2017 4:21 AM
Hi Acenyc59,
>>The master browser has received a server announcement from the computer <computer name> that believes that it is the master browser for the domain on transport NetBT_Tcpip_{B7545DFC-BA6C-4712-81. The master browser is stopping or an election is being forced.
You could try the steps blow:
1. Look at the System Event log on your server and look for the error 8003. Within that log, identify the “computer” that is announcing itself as a master browser.
2. Go on to the computer identified in step 1, go to the Services Administration panel. You can usually find this by going to Control Panel -> Administrative Tools -> Services.
3. Once you have Services open, look for an entry called “Computer Browser”. If that service is “started, ” you have found your culprit. If not, you may have to try the registry hack listed in step 6.
4. Double click on the “Computer Browser” service to edit it. Stop the service and then change the type to „Disabled” (from either Manual or Automatic). Click OK to apply your changes.
5. That should have resolved the issue. You should check your main servers event logs periodically to be sure that the error does not show up. If the error continues to appear read step 6.
6. Check the following registry value on the computer: "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Browser\Parameters\IsDomainMaster". Ensure that it is set to false. You probably have to reboot the machine to make the change take place.
For more details, please refer to the following link:
http://www.eventid.net/display.asp?eventid=8003&eventno=680&source=mrxsmb&phase=1
Please Note: Since the web site is not hosted by Microsoft, the link may change without notice. Microsoft does not guarantee the accuracy of this information.
Best Regards,
Candy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Wednesday, October 4, 2017 2:15 PM
Thank you for your help. I will try this when I get to the office. As you can see, I have a lot of problems with this RDP terminal server configuration, as I have never done this before. Thanks!
Wednesday, October 4, 2017 8:55 PM
Thank you very much for your help. I cleared the logs on the TS and the domain controller and after about 15 minutes, the error 8003 came right back on the domain controller. I checked the registry path you gave me, and I don't have **IsDomainMaster in BROWSER. ** Is there anything else I can try to fix this error. As I said, I have so many errors, I am hoping maybe you can assist me with fixing some of them. One of the primary problems I am having is when I try to connect to the RDS terminal server from a connected client computer, it does not connect and I get an error message. The third message says, "the remote computer is not available on the network". When I open network places on the client computer, I only see the local computer(asc1139). I do not see the domain controller or the RDS terminal server in network places. Should I be able to see the domain controller and the RDS terminal server in network places on the client computer? Could that have something to do why I can not connect to the terminal server? I can PING the domain controller and the RDS terminal server from the client computer. I have included two screen shots of the errors.
Thank You.
Wednesday, October 4, 2017 11:29 PM
Thanks, but that was one of the first things I checked. The clocks on the DC, TS and client computer are all on the same time. Any other suggestions would be greatly appreciated. Thank You.
Thursday, October 12, 2017 9:39 AM
Hi Acenyc59,
I am trying to involve someone familiar with this topic to further look at this issue. There might be some time delay. Appreciate your patience.
Thank you for your understanding and support.
Best Regards,
Candy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, October 13, 2017 3:04 PM
Thank you Candy for trying to help me. As I said, I am totally new to all this, but I need to ask you this question. When I add any member server to a domain controller, do I have to make a new DNS entry for that member server? If I do, where do I create the entry? On the RDS terminal server, or the the domain controller? As of right now, I do not have a DNS entry for the RDS terminal server. Maybe that's the problem. Also, I am going to send you a link for a posting I made on another section of the forum.
Thank you so much.
Monday, October 16, 2017 8:04 AM
Hi Acenyc59,
>>*When I add any member server to a domain controller, do I have to make a new DNS entry for that member server? If I do, where do I create the entry? On the RDS terminal server, or the the domain controller? *
As far as I know, you don't need to create the entry on the RDS terminal server.
If dynamic DNS registration is enabled, it should automatically register it. You can try IPCONFIG /Registerdns from the RDS terminal server.
If there is no DNS entry created in DC , you could create it manually in DC.
For your reference:
https://technet.microsoft.com/en-us/library/cc771255(v=ws.11).aspx?f=255&mspperror=-2147217396
>>I can PING the domain controller and the RDS terminal server from the client computer.
1.Please check if you could ping FQDN or IP address and post out warnings and errors in the ping result.
2.You may turn on exhaustive debugging mode of NSlookup, this will display detailed information of name resolving process.
Open Command Prompt on client ,type nslookup and type set d2 . we could find out the problem through the process .
>NSlookup
>set d2
>[name which you want to resolve]
Here is the guide for Nslookup :
Nslookup
https://technet.microsoft.com/en-us/library/cc940085.aspx
Best Regards,
Candy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].
Friday, October 20, 2017 8:03 PM
Here is the information you requested
My domain is:
ascnyc2.org
My domain controller is named:
ascnyc2-dc03 192.168.1.9
FQDN is:
ascnyc2-dc03.ascnyc2.org
My terminal server is named:
ascts 192.168.1.13
FQDN is:
ascts.ascnyc2.org
I can ping from the connected client computer to the domain controller with the IP address 192.168.1.9
I can ping from the connected client computer to the domain controller with the server name and the FQDN
I can ping from the connected client computer to the terminal server with the IP address 192.168.1.13
I can ping from the connected client computer to the terminal server with the server name and the FQDN
I get no errors when I ping both servers.
Also, I noticed that on both my domain controller and my RDS terminal server, when I go into network, I can see the domain controller, the RDS terminal server and the connected client computer. When I go into network on the connected client computer, I can not see the domain controller, or the RDS terminal server.
*** UnKnown can't find nslookup: Non-existent domain
> set d2
> set d2
> nslookup
Server: UnKnown
Address: 192.168.1.9
SendRequest(), len 38
HEADER:
opcode = QUERY, id = 6, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
nslookup.ascnyc2.org, type = A, class = IN
Got answer (109 bytes):
HEADER:
opcode = QUERY, id = 6, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
nslookup.ascnyc2.org, type = A, class = IN
AUTHORITY RECORDS:
-> ascnyc2.org
type = SOA, class = IN, dlen = 48
ttl = 3600 (1 hour)
primary name server = ascnyc2-dc03.ascnyc2.org
responsible mail addr = hostmaster.ascnyc2.org
serial = 1411
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
SendRequest(), len 38
HEADER:
opcode = QUERY, id = 7, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
nslookup.ascnyc2.org, type = AAAA, class = IN
Got answer (109 bytes):
HEADER:
opcode = QUERY, id = 7, rcode = NXDOMAIN
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
nslookup.ascnyc2.org, type = AAAA, class = IN
AUTHORITY RECORDS:
-> ascnyc2.org
type = SOA, class = IN, dlen = 48
ttl = 3600 (1 hour)
primary name server = ascnyc2-dc03.ascnyc2.org
responsible mail addr = hostmaster.ascnyc2.org
serial = 1411
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
*** UnKnown can't find nslookup: Non-existent domain
>
C:\Windows\System32>nslookup
Default Server: UnKnown
Address: 192.168.1.9
> set d2
> ascts
Server: UnKnown
Address: 192.168.1.9
SendRequest(), len 35
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
ascts.ascnyc2.org, type = A, class = IN
Got answer (51 bytes):
HEADER:
opcode = QUERY, id = 2, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 1, authority records = 0, additional = 0
QUESTIONS:
ascts.ascnyc2.org, type = A, class = IN
ANSWERS:
-> ascts.ascnyc2.org
type = A, class = IN, dlen = 4
internet address = 192.168.1.13
ttl = 1200 (20 mins)
SendRequest(), len 35
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: query, want recursion
questions = 1, answers = 0, authority records = 0, additional = 0
QUESTIONS:
ascts.ascnyc2.org, type = AAAA, class = IN
Got answer (95 bytes):
HEADER:
opcode = QUERY, id = 3, rcode = NOERROR
header flags: response, auth. answer, want recursion, recursion avail.
questions = 1, answers = 0, authority records = 1, additional = 0
QUESTIONS:
ascts.ascnyc2.org, type = AAAA, class = IN
AUTHORITY RECORDS:
-> ascnyc2.org
type = SOA, class = IN, dlen = 48
ttl = 3600 (1 hour)
primary name server = ascnyc2-dc03.ascnyc2.org
responsible mail addr = hostmaster.ascnyc2.org
serial = 1411
refresh = 900 (15 mins)
retry = 600 (10 mins)
expire = 86400 (1 day)
default TTL = 3600 (1 hour)
Name: ascts.ascnyc2.org
Address: 192.168.1.13
>
Wednesday, October 25, 2017 5:58 AM
Hi ,
You might need to use network monitor to analyze the process.
https://www.microsoft.com/en-sg/download/details.aspx?id=4865
Best Regards,
Candy
Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected].