Hi,

I have a single 2008R2 Terminal Server that's no longer receiving printers from our 2008R2 print server (deployed using GP via. the Print Management console). We have 4 other 2008R2 TS that are properly receiving the printers. All TS are built from the same image.

Until Monday, all 5 of our TS were receiving the deployed printers properly. AFAIK, nothing's changed. There are no new errors or relevant information in the event log of the problem TS.

Now, an employee can log into any of the 4 working TS and get their printers properly. As soon as they log into the last (non-working) TS, they don't receive any printers. This behavior also applies to super-users (like my domain admin ID). This behaviour persists across reboots.

Printers are deployed with the same per-Machine GPO to all 6 of our terminal servers. User GPOs (with loopback processing) ensures that only the correct floor's printers are assigned to a user. GPMC tells me that printers are deployed properly ('Printer Connections' show all the printers and 'Deployed Printer Connections' reports 'Success').

How can I track down this issue and fix things?

Thanks,
Greg

Edit: We have a single print server at our organization, so all TS use the same print server.

• Edited by Greg Beifuss 20 hours 59 minutes ago

might be some problem with one of the print servers

try a fresh image and see if that clears up the problems

I'm going to add that the PrintService (Admin) log has filled up with Event 513. I see error codes 0x709, 0x5 and 0xbc4:

Log Name:      Microsoft-Windows-PrintService/Admin
Source:        Microsoft-Windows-PrintService
Date:          2/12/2014 11:06:42 PM
Event ID:      513
Task Category: Routing print spooler command(s)
Level:         Error
Keywords:      Router,Classic Spooler Event
User:          zzz\xxx
Computer:      TS02.zzz
Description:
Group Policy was unable to add per computer connection \\ps01\4SW_HP9040_01. Error code 0xbc4. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-PrintService" Guid="{747EF6FD-E535-4D16-B510-42C90F6873A1}" />
    <EventID>513</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>39</Task>
    <Opcode>12</Opcode>
    <Keywords>0x8000000000002800</Keywords>
    <TimeCreated SystemTime="2014-02-13T04:06:42.528939900Z" />
    <EventRecordID>42684</EventRecordID>
    <Correlation />
    <Execution ProcessID="1196" ThreadID="2440" />
    <Channel>Microsoft-Windows-PrintService/Admin</Channel>
    <Computer>TS02.zzz</Computer>
    <Security UserID="S-1-5-21-363400830-1954133009-1268342360-1666" />
  </System>
  <UserData>
    <RouterError xmlns:auto-ns3="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://manifests.microsoft.com/win/2005/08/windows/printing/spooler/core/events">
      <Name>\\corpps01\4SW_HP9040_01</Name>
      <Error>0xbc4</Error>
    </RouterError>
  </UserData>
</Event>

This is the error

C:\debuggers>winerror 0xbc4
  3012 ERROR_PRINTER_NOT_FOUND <--> No NTSTATUS matched

Was there some routing table that got updated on the machine?  Did you edit the server name in the event? 

Group Policy was unable to add per computer connection \\ps01\4SW_HP9040_01. Error code 0xbc4. This can occur if the name of the printer connection is incorrect, or if the print spooler cannot contact the print server.
       <Name>\\corpps01\4SW_HP9040_01</Name>

My gut tells me to check the print provider binding order

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Print\Providers

this is what I have

LanMan Print Services
Internet Print Provider

Hi Alan,

Thanks for the reply. You're right, I tried editing out server names/info, but I missed one... oops!

The registry structure looks identical on a working TS and the non-working TS.

I've noticed that if I try to browse to the printer via. NetBIOS name (ie. \\CORPPS01\printer_name), I get the error. If I use the IP (ie. \\192.168.0.1\printer_name), the non-working TS looks for a driver to install.
Both the working & non-working TS resolve the name properly when pinged: ping CORPPS01 returns the FQDN, IP and successful replies.

I've found two links that look promising, that I'll have to try after business hours tonight:
http://social.technet.microsoft.com/Forums/windows/en-US/9af1dc6e-5213-45aa-8296-76ef21be6c19/no-printers-were-found-net-work-printer-error?forum=w7itpronetworking

(delete a bunch of regkeys)

and

http://social.technet.microsoft.com/Forums/windowsserver/en-US/24dfd6c0-b460-40a7-ad18-13e404b361e7/group-policy-printers-dissapearing-from-client-machines-intermittently?forum=winserverGP

(delete the GP history directory)

Thanks,
Greg

There's something wrong with your network configuration when the server name does not resolve.

If you had a file share you also would be unable to add the connection using the name.

Hi Alan,

Thanks for the reply. As far as I can tell, the network/name resolution looks legit (DNS, WINS). I can browse to a file share on the print server (\\corpps01\logs) just fine from the non-working TS, it's only the printers that I cannot access this way. The share & security settings seem to be correct on the printers themselves.

Greg

Thinking.....thinking.....thinking.

Respond to this later if I have not responded back to this in a couple hours.

thanks

I still think installing the server image fresh will be the fastest way back to work

I like printers with their own integrated servers, makes it somewhat easier to deploy and manage.

I guess I did not think hard enough.  I'll come back to this.