Domain issues via Wifi randomly started happening

Billy Wotherspoon 21 Reputation points
2021-05-12T15:11:46.753+00:00

Hi guys I gope you can help me with this one.

Ive had a small domain network running just fine over wifi with laptops been able to domain join them via wifi and generall just acted as normal.

Suddenly It seems an issue has started for me where Now I cant access ADUC or any of the AD DS tools via Wifi and have to be wired in.

The wireless part of the network is a Big Thing for our company as we always have staff moving and going so we rely on it so they can get logged in and Running.

Now I cant even login any other user account on the domain as it says it is invalid. However when Connected via wire it works just fine

when I try use ADUC over wireless It states server not operational even though it is running and worked via wired connection.

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

       Adapter Name : {A4ED43A1-DCAB-4F09-A554-07B950E79139}
       Host Name : LT09
       Primary Domain Suffix : EGG.DNS
       DNS server list :
            192.168.8.16, 8.8.8.8
       Sent update to server : 192.168.8.16:53
       IP Address(es) :
         192.168.8.19

The reason the system could not register these RRs was because the DNS server contacted refused the update request. The reasons for this might be (a) you are not allowed to update the specified DNS domain name, or (b) because the DNS server authoritative for this name does not support the DNS dynamic update protocol.

To register the DNS host (A or AAAA) resource records using the specific DNS domain name and IP addresses for this adapter, contact your DNS server or network systems administrator.

I constantly get this event in event viewer and it is getting fustrating as I cant setup Laptops over wifi any more nor Am I able to manage accounts remotely while still being able to remote into the domain controller

My wired network consists of 192.168.8.xxx and my wireless is 192.168.4.xxx

Windows for business | Windows Client for IT Pros | Directory services | Active Directory
0 comments No comments
{count} votes

Accepted answer
  1. Anonymous
    2021-05-13T12:34:50.567+00:00

    Sounds like a routing issue. Generally you'll need a layer three switch to route between 192.168.4.x and 192.168.8.x networks or possibly back off the subnet, but this is another topic so I'd start a new thread if help is needed with routing.

    --please don't forget to Accept as answer if the reply is helpful--

    0 comments No comments

10 additional answers

Sort by: Most helpful
  1. Anonymous
    2021-05-12T15:20:46.693+00:00

    First thing you'll want to remove the google public DNS from connection properties. Domain controller and domain member must have the static ip address of DC listed for DNS and no other such as router or public DNS

    --please don't forget to Accept as answer if the reply is helpful--


  2. Billy Wotherspoon 21 Reputation points
    2021-05-12T15:30:35.74+00:00

    96044-image.png

    I also get this when trying to use aduc

    0 comments No comments

  3. Anonymous
    2021-05-12T15:32:13.517+00:00

    Please run;

    Dcdiag /v /c /d /e /s:%computername% >c:\dcdiag.log
    repadmin /showrepl >C:\repl.txt
    ipconfig /all > C:\dc1.txt
    ipconfig /all > C:\dc2.txt
    ipconfig /all > C:\problemworkstation.txt

    then put unzipped text files up on OneDrive and share a link.

    0 comments No comments

  4. Billy Wotherspoon 21 Reputation points
    2021-05-12T15:40:49.667+00:00

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.