Re: Printers keep disapearing

From: MDPILWL (anonymous_at_discussions.microsoft.com)
Date: 08/19/04 

Date: Thu, 19 Aug 2004 15:35:18 -0700

David;
Thanx for the info. So you don't think it has something to
do with the ADS Connectors in the AD Sites and Services?

Should I have a connector for each site that connects to
all other DCs at all other sites? In other words I have 10
sites so should each site have 9 connectors to replicate
to the other 9 DCs at each of the other sites?

>-----Original Message-----
>Restart Netlogon Service on the DC(s) at the remote
location where the print
>server is.
>
>Next, restart the Print Spooler service on the print
server. Once this is
>done open AD Users and Computers on the DC(s) in the same
site as the print
>server. In ADU&C check View on the menu bar and place a
check next to the
>options of "Users, Groups, and Computers as containers"
and "Advanced
>Features".
>
>Locate the print server in ADU&C and see if the printers
appear under that
>print server. If there is more than one DC in that site
then focus ADU&C on
>those DCs until you find one that lists the printers
under the print server.
>
>NOTE: If the printers do not publish on any DC then
run "gpresult /s
>>servername.txt" on a DC and on the print server. then
check the
>servername.txt files to see if any policy settings
mentioned in the KB
>234270 could be are preventing the printers from being
published. If no
>policies are configured then open ADU&C and check the
Security permissions
>under the print server's Properties. Verify the Self
group has Allow set on
>the following permissions:
>
>"Validate write to service principal name"
>"Validate write DNS host name"
>"Create child objects"
>"Delete child objects"
>
>If the printers do appear on any DC in that print
server's location, log on
>to that DC as Enterprise Admin and run this command:
>
> repadmin /syncall /e /d /P <name-of-the-DC-with-the-
printers>
>
>If you get errors then DNS or other issues might be
preventing this DC from
>replicating to the other DCs and they could be preventing
the print server
>from publishing in AD. If you do get errors use "net
helpmsg ###" to see
>what the error translate to.
>
>By default, the DC(s) in the site of the print server
check every 8 hours by
>pinging the print server to verify that the print server
is online. When a
>print server fails to respond an Event ID: 47 is
generated in the System
>event log of the DC. If the print server fails to
respond three times in a
>row the DC(s) in that site will prune the printers from
AD. When this
>occurs an Event ID: 50 is registered on the DC.
>
>You can modify print pruning behavior in GPO if needed.
>
>234270 Using Group Policies to Control Printers in Active
Directory
>http://support.microsoft.com/?id=234270
>
>--
>David Everett
>Microsoft Corporation
>
>This posting is provided "AS IS" with no warranties, and
confers no rights.
>
>"MDPILWL" <anonymous@discussions.microsoft.com> wrote in
message
>news:180201c48574$2f8e4510$a301280a@phx.gbl...
>> We have 10 remote sites with 1 DC in each and each has a
>> global catalog. the main location has connections to
each
>> of the sites and each of them have a single connection
>> back. One day the main location lost power and was down
>> over the weekend and the DS replication appointed
another
>> site as the main one and sense that time we have not
been
>> able to get our shared printers back into AD so that
each
>> site can see them. I remoted into each site server and
>> unshaered the printer then reshared them tehn restarted
>> the FRS and they came back. that lasted until this power
>> outage. Now even if I go to each site and reshare the
>> printer they don't show up at each site when trying to
>> add a printer.
>>
>> Any idea?
>
>
>.
>

Relevant Pages

  • Re: Printers keep disapearing
    ... If you are referring to the connection objects which enable AD Replication ... print server has the printers published in AD, ...
    (microsoft.public.windows.server.active_directory)
  • Re: Not sure where to post this - Print server functionality
    ... Couldn't y'all use a Unix or VMS box to serve them up via LPR? ... I can define a PC at each site as a print server, define the printers on that print server and deploy the printers via Group Policy, but the down sides are the usual concerning if the PC is turned off, if the PC gets hit by a virus and has to be sent up here to be rebuilt, all the usual. ... Spool its own jobs. ...
    (microsoft.public.windows.server.general)
  • Re: Printer Sharing in FC3
    ... >> Printing is done with cups on FC. ... >> print job over the network to the print server, ... >> I don't know the details in the configuration, ... printers are shared by default and no configuration of a cups ...
    (Fedora)
  • Switch between printservers
    ... Do a quick searh of this newsgroup for a sender called MARCUS. ... work automatically if one print server fails. ... > I intend to connect the printers for my clients using IPP ... > want to change the DNS-Alias and use another printserver. ...
    (microsoft.public.win2000.printing)
  • Re: Printer Listing Issue in AD
    ... Please verify the printers are published in Active Directory. ... > the DCs in each office is a print server. ...
    (microsoft.public.win2000.active_directory)
Loading