Print Server listing shared printers but connection failing when trying to connect

I set up a Windows Server 2008 R2 as a print server on our domain.

All 30 printers have been installed and shared.

On the clients I can view all of the printers on the servers IP. I could then connect and install them on the client machines successfully.

I wanted to make it simpler by using \\printers so I set up an A record to point to the Server IP. This worked and entering \\printers sure enough shows all of the printers listed. But as soon as i tried to connect / install I am getting the following error??

"Operation could not be completed (error 0x00000709) Double check the printer name and make sure that the printer is connected to the network"

I have scoured some forums but with little success.

Any help will be much appreciated.

BF

Microsoft Legacy OSWindows Server 2008

Last Comment

bigfooter

8/22/2022 - Mon

max_the_king

12/4/2013

Hi,
why don't you just do "add printer" "from network" on the specific client, browse the printer you want to install and click on it ?

then you are sure it finds the right printer without worrying about dns name an ip addresses-

hope this helps
max

bigfooter

12/4/2013

ASKER

Hi Thanks for your comments but it is not they way we are looking to set this up.

Basically I can go to to a clients machine and use the local IP or Computer name to connect to the print server

\\192.168.100.150
\\computername

This lists the shared printers and i can install them with one click.

To keep things simple I just want to use

\\printers

for many reasons.

The A record has done half the Job as it resolves lists the server and lists the printers that are shared but does not allow the printers to install.

Cheers

ASKER CERTIFIED SOLUTION

max_the_king

12/4/2013

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.

View this solution by signing up for a free trial.

Members can start a 7-Day free trial and enjoy unlimited access to the platform.

See Pricing Options

Start Free Trial

GET A PERSONALIZED SOLUTION

Ask your own question & get feedback from real experts

Find out why thousands trust the EE community with their toughest problems.

bigfooter

12/4/2013

ASKER

Hi Max,

Thanks and almost...

I found a post based on your PTR

++++++

This error is returned because of the optimization changes to the spooler service in Windows 2008 R2 Server. The Print Spooler service uses the local names to service requests. We’ve verified the name being used is correct and we can connect using the NetBIOS, FQDN and IP address of the server.

Step one is to make sure the target print server has the DNSOnWire registry key set to 1:

HKLM\SYSTEM\CurrentControlSet\Control\Print\DNSOneWire (REG_DWORD)

++++++

I created the KEy and restarted the Print Spooler and Bingo. All good

Experts Exchange has (a) saved my job multiple times, (b) saved me hours, days, and even weeks of work, and often (c) makes me look like a superhero! This place is MAGIC!

Walt Forbes