shared printers go unavailable after domain controller upgrade/replaced with 2019

Question

Hi All,

we have a domain with XYZ. Forest and domain functional level 2008 R2, combination of 2012 R2 and 2016 DC's, we decided to bring in 2019 DC as part of upgrade in one of the site, we added ADC 2019 and was successful.

however when we shutdown the old 2012 R2 domain controller the printers (deployed via GPO from a different print server) goes to Access Denied Unable to connect ,

when trying to access the print server from any client system via \printserver the below error populates

if we bring the old 2012 R2 DC online the printers become normal and available

can someone advise is there any difference the way authentication happens in CD 2012 R2 & 2019

also on the print the below error appears whenever the old DC is not available
"While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: 6ba. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory"

appreciate if someone knew what is the cause and resolution kindly share the same.

***moved from Windows / Other/Unknown / Install, upgrade, and activate***

Answer 1

this is the error I see in the print server after the old domain controllers are powered off

"While attempting to publish the printer to the Active Directory directory service, the print spooler could not find the appropriate print queue container because the Domain Name System (DNS) domain name could not be retrieved. Error: 6ba. This can occur if DNS cannot resolve the domain controller IP address, or if the domain controller or directory service is not functioning correctly. The printer is not published in Active Directory and cannot be located by searching Active Directory"

but I have verified below
DNS is proper
able to resolve domain name

able to resolve domain controller

able to ping domain controller

Answer 2

Hello,

After replacing the domain controller, did you ensure that the new domain controller is properly promoted and functioning as the AD DS server? Also, confirm if the DNS service is running and configured correctly on the new DC.

Here are some simpler tests to start with:

1. DNS Resolution Test:

• Open Command Prompt and type: nslookup <your_domain>

Check if it returns the IP address of your new domain controller or an authoritative DNS server.

• Also, try: nslookup <new_DC_hostname_or_IP>

It should return the hostname and IP address of the new domain controller.

2. Check AD Connectivity:

• From a client computer in the domain, open Command Prompt and run:

nltest /dsgetdc:<your_domain>

This will verify that the client can find and connect to a domain controller for your domain. Ensure it is returning the new domain controller.

3. Printer Sharing Reconfiguration:

• Log into the server where the shared printer is installed.
• In the Printers settings (Control Panel > Devices and Printers), right-click on the shared printer and ensure it's shared and has the correct permissions set for users/groups in the new domain environment.
• Try to re-publish the printer to the new domain by removing and then adding the printer share again.

4. Check Group Policy Object (GPO) for Printer Deployment:

• If you deployed the printer via GPO, check the GPO settings to ensure they're correctly referencing the new DC.

5. Network Connectivity:

• Make sure the client computers have network connectivity to the new domain controller and the server hosting the shared printer.

Regards,

Karlie

Answer 3

The new domain controller is functional ,

other servers are able to login using the new DC as logon server

shared DFS is accessible,
domain replication is all good

DNS works fine
ns lookup via the new deployed DC& DNS is able to resolve domain name and other servers as well as ADC

printer is shared to everyone have checked the permissions

I am worried to re-publish if every user looses the connectivity to printer and needs a reconfiguration

the GPO is pointing to the print server which is different from domain controller and is referenced correctly

client computers have access to the domain controller
what is strange is when the old 2012 DC is up along with new 2019 ADC the \printserver is perfectly working
when the 2012 DC is brought down and only new 2019 ADC are working \printserver gets permission issues

Answer 4

In the event logs on the print server when trying to access it from a client while only the 2019 DC is online, are there any Kerberos or NTLM authentication errors?