Issue with new DC / DNS server w Group Policies for Drive Mapping

cssup

New Member
Hi all,

First let me start with what I'm trying to accomplish:

- My DC will also be a file server for sharing company documents and individual staff members will have their own personal drives (e.g. L: for Staff Files, M: for Company Files).
- Be able to successfully ping DC/File server using hostname both from client computers to server and server to client client computers.
- Be able to pull group policies into all client computers.
- Be able to add additional client computers in the future with no issues joining to Domain due to DNS.

I'm having a dilemma with the following:

- I have added ADDS & DNS on my Server 2016 box.
- I have created 2 security groups (Staff and Company Admins)
- Under the DC I have created 1 OU with 4 sub OU's example below:
- ABC_Company
- Admins OU -> Contains Admin security group
- Staff OU -> Contains Staff security group
- Computers -> Contains few client computers that I've joined to domain
- Users -> Contains individual AD staff and admin accounts
- I have created a GPO under ABC_Company OU that maps the drives to OU's - Staff and Admins

The situation:

My gpupdate /force isn't working due to DNS issues. I've configured DNS on my server with forward/reverse lookup zones with A-Records for my client computers. I had to put the static DNS IP of the DC on the client computers (NICs) in order to join domain, as well as add a HOSTS file entry both on the server and client computers to be able to join them to the domain, otherwise it would fail. I'm desperate to understand where the config fell through or is it something that I missed. I've provided several screenshots that might explain my situation.

My network admin has Ubiquiti Unifi Secure Gateway installed and he swears that there's no filtering or blocking on my VLAN.
 

Attachments

  • Annotation 2019-11-24 014222.jpg
    Annotation 2019-11-24 014222.jpg
    359.5 KB · Views: 125
  • Annotation 2019-11-24 013933.jpg
    Annotation 2019-11-24 013933.jpg
    169.9 KB · Views: 125
  • Annotation 2019-11-24 013818.jpg
    Annotation 2019-11-24 013818.jpg
    80.3 KB · Views: 137
  • Annotation 2019-11-24 013724.jpg
    Annotation 2019-11-24 013724.jpg
    178.3 KB · Views: 120
  • Annotation 2019-11-24 013548.jpg
    Annotation 2019-11-24 013548.jpg
    68.8 KB · Views: 149
  • Annotation 2019-11-24 013423.jpg
    Annotation 2019-11-24 013423.jpg
    177.9 KB · Views: 135
  • Annotation 2019-11-24 013058.jpg
    Annotation 2019-11-24 013058.jpg
    48.1 KB · Views: 125
  • Annotation 2019-11-24 012101.jpg
    Annotation 2019-11-24 012101.jpg
    151.9 KB · Views: 136
Last edited:
My first question would be are you using DHCP for the clients? If so is it working and is it supplying DNS settings server and domain search order? Beside that I'd say a Wireshark capture would be really handy for troubleshooting this
 
My first question would be are you using DHCP for the clients? If so is it working and is it supplying DNS settings server and domain search order? Beside that I'd say a Wireshark capture would be really handy for troubleshooting this

Neemobeer, the DHCP is done on the Ubiquiti Gateway, and DNS is enabled on the DC server. We have also added the DNS suffix to match our domain name. The issue is that the Group Policy seems to work only on the Lockouts, Password complexities, and elevated permissions for installing/uninstalling software, but doesn't work on mapping drives that we configured in group policy.
 
The fact that you have problems joining devices tells me either you have DNS misconfiguration or filtering blocking the traffic. Problems with specific GPOs is either incorrect permissions, or security filtering on the GPOs. Specific issues with drive mappings can also be share permissions, firewalls too. You can enable GPO tracing to further disgnose the issue
 
Back
Top