Quantcast
Channel: Print/Fax forum
Viewing all 3156 articles
Browse latest View live
↧

Updating one printer driver on Windows server 2003 causes other printer's to request updates to their drivers too.

February 8, 2013, 9:25 am
$
0
0

We have numerous printers installed on Windows 2003 server. Most of them are HP, and the problem only effects the HP printer, sometimes it also effects are Ricoh copiers. The problem occurs when we update the driver for any printer. All printers are connected via our network. When we update the drivers for one printer, it will apparently start updating the drivers for all the other HP printers on the server. All users starting having request pop up on their machines telling them that they need to update their printer drivers. 

Some specifics about the most recent time:

-We were installing a new printer on the server, an HP 500 M551

-There are already drivers on the server from a previous HP 500 M551 that was installed, so we did not install a new driver, we used one that already existed on the server

-I noticed that no computers with XP needed to update their drivers, but every Windows 7 computer that uses an HP printer need to install the update. All computers are 32 bit

In the past it does not immediately effect every printer globally, but it does happen every time we update one driver on the server, it will update all drivers(request users to update their drivers). I do recall XP computers requesting an update of drivers before, just not in this recent case.

↧
Search

Why does Windows Firewall have to be turned on in order to share printers? This makes no sense at all.

February 7, 2013, 11:33 am
$
0
0

On a server with Windows Server 2008 R2 in Print Management, I added a network printer to be shared with workstations. After installing, the installer said the driver installed successfully, but the printer did not; it had an error code: 0x000006d9. I found a forum with a post suggesting that the firewall needs to be turned on.

I turned on Windows Firewall from services.msc, and I was then able to install the printer and share it. What I don't understand is why the firewall needs to be on just to share a printer. Why can't I keep the firewall offand share a printer?

I understand that running the "Print Server" service creates a firewall exception for file and printer sharing; but if the firewall is off, common sense would suggest that no such exception is necessary. I should be able to share a printer with no problems. I can sharefiles just fine without the firewall enabled, why can't I share printers?




↧
↧

Disappear local port when restart print spooler

September 13, 2012, 5:46 pm
$
0
0

Hello,

I've a problem, when I restart the print spooler or I reboot the windows, the Local port disappears.
This error began after I ran the Printer Migrator Restore in Windows Server 2008, the file restore was from Windows Server 2003.

I added the local port using the snap-in Print Manager(Print Server)
Ex: \\svr01\Printer01

If I don't restart the service print spooler I can use normally this port, but I'm restart the service "Print Spooler" this port is removed.

This behavior didn’t occur before I run Print Migrator


SO: Windows Server 2008 R2 Standard


↧

regards print the documents in serial port

February 9, 2013, 10:34 pm
$
0
0

i have an 2008 server, i can print the documents in windows, but cant print when printers all in parallel port, how to access my printer using Queue or Any Other technique to print via parallel port...

↧

Error message on a Windows Server 2003-based computer: "You do not have sufficient access to your computer to connect to the selected printer"

February 11, 2013, 5:57 am
$
0
0

Afternoon all,

Following these instructions has made no difference:  http://support.microsoft.com/kb/259937

All users are using terminal services 2003 with a 2000 print server.  They are connecting via Citrix.

How ever, when a user tries to connect a printer they get the following error:  "You do not have sufficient access to your computer to connect to the selected printer".

I've also checked GPO and the relevant local security option has been disabled, as per the instructions in the above article.

Any help would be appreciated.

Thanks

Martin

↧
↧

2008 R2 printing from Office randomly gives "there was an error when printing started"

February 11, 2013, 12:33 pm
$
0
0

This comes from a terminal server environment. This error only happens from outlook/word 2010. Printer is fine 100% of the time from the biz application and adobe or test page function. I have several users on several servers reporting this. Here is what I have tried.

-Recreated user's roaming profile

-Changed drivers

-Changed default printer

-Deleted outlprnt file

-Changed user to a different TS

-Repaired office.

The only fix when this error happens is for the user to log off and back on. Nothing in the eventvwr that tells me its even happening.

Any advice?

↧

Server 2003 LanMan Print Services - CacheChangeID Problem

February 13, 2013, 10:46 am
$
0
0

Hello,

We are expriencing a problem with printing from our server 2003 Citrix servers using a 2008 R2 print server. Ever since we migrated to a 2008 R2 server sometime last year we began expriencing client side printing issues. It began with users trying to print to their default printer out of Office 2010 on a 2003 Server. When they would go to print Office would show the printer as "Connecting ..." or "Unavailable ..." and other 3rd party applications would show that the printer does not exist and when you would browse the list of printers from the applications it would not show the default printer as an option. When you would go into the control panel > Printers & Faxes it would show all of the printers and you could bring up the properties of the default printer and print a test page. After printing a test page it would resolve the issue temporarily until the user logged off of their session and would log back in again and it would happen again at some point.

Eventually using process monitor I was able to track the registry changes made by printing a test page to a registry value namedCacheChangeID under HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\LanMan Print Services\Servers\(print server name here)\Printers\(printer name here)\. Everytime there was a problem and I printed a test page it would change this reigstry value on the client side and they would be able to print again. I've tried clearing all printers from the client server, deleting the entire registry key for all of the printers underHKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Print\Providers\LanMan Print Services\Servers\(print server name here)\and adding all of the printers back but when I do on certain servers the CacheChangeID never matches the ChangeID on the print server.

If anyone could help explain this behavior and why it resolves this printing issue it would be appreciated. Also it would be nice to find some more detailed documentation of this registry value "CacheChangeID". I do not see this value on any of our Windows 7 desktops or 2008 R2 terminal servers for their printer mappings.

Thanks,

bank-tech

↧

Problems installing 32 bit printer in Windows Server 2008 R2

May 14, 2010, 6:41 am
$
0
0

I'm trying to install 32 bit printer drivers on our Windows Server 2008 R2 print server for various printers including Xerox copiers and some older HP printers.  The 64 bit versions (universal printer drivers for HP and Xerox) of the drivers install without problems for the most part but I get stuck on the 32 bit install.  It wants the 32 bit NTPRINT.INF/NTPRINT.DLL files from the I386 directory of our Windows XP SP3 which has been copied to the local server directory.  It asks for the files in D:\I386 or C:\I386 but when I browse to those directories and select the NTPRINT files and click OK it just keeps asking for the same file.  I have no choice but to abort the driver install. 

We're in the process of moving to AD this summer and eventually moving to Windows 7 Enterprise 64 bit but in the mean time, we still have a boatload of Windows XP systems on campus that still need 32 bit printers in order to print.  Any ideas?

↧
Search

Printing slow after IP schema change

March 22, 2011, 1:11 pm
$
0
0

Over the weekend we switched from a class C network to Class B. We only have 150 hosts. Since then, printing from our print server has become slow. Everything else is working ok. If you add the network printer directly to your workstation, it prints fine. If you send a print job directly from the server to the printer installed on it, it works fine. But if a print job has to go through a share to then print, it's really slow.

The issue appears to be isolated to our domain controller. If you add a printer being hosted from another machine, the print job goes through fine.

 

This became apparent right after our IP schema change.

 

Any ideas?

 

We ruled out network congestion or any issues relating to broadcast.

↧
↧

How to add IP printer to active directory?

August 12, 2008, 1:21 am
$
0
0

Hi expert people

I have question

I want to add IP printer to the active directory

I am going to active directory users and computers and trying to add the printer

But it ask me for network path like “\\server\share”

I try to put printer IP address but it’s not accepting it

Can anyone tell me what is the best way to add this printer to the domain

The reason to add this printer to the domain is to make it the defult printer via login script

 the printer is avilable throw the network but i want to add it to the AD

I hope to find the solution in your experience

 

 

 
↧

Windows Server 2008 R2

February 13, 2013, 10:37 pm
$
0
0

Hi,

Just want to ask if Server 2008 R2 supports WSD installation for Printer?

↧

Windows Server 2008 R2 Print Server Job Owner Issue

August 17, 2011, 1:22 pm
$
0
0

At the start of the year we rebuilt our server infrastructure from Windows Server 2003 R2 (Enterprise) to Windows Server 2008 R2 (Enterprise). Since then we've had a sporradic/rare unusual issue occur with our Print Server.

 

Our Print Server is setup fairly simply, it's a standard Windows Server 2008 R2 Print Server, it has print drivers (64-bit) for our Xerox ApeosPort IV 5570 machines, and it runs Equitrac Office 4.2 for printer authentication and follow me printing. The servers that the users are printing from are Windows Server 2008 R2 Terminal Servers (2 in a Farm).

 

The issue we encountered first was that in rare instances users printing and picking up jobs from their Follow-Me print bins on the printer would find that a job would be missing. Another user would come along and do some printing of their own and find the missing job in their own Follow-Me print bin instead.

 

We originally thought that this was an Equitrac issue and worked closely with our printer support reps in an attempt to find the issue and fix it, but after many logs and months back and forth between Equitrac, our print support reps and ourselves we found that the issue wasn't with Equitrac but seemingly from the Windows Print Server itself.

 

What we found was that in rare instances (Unfortunately it's rare and I haven't been able to replicate it on demand yet) when a user prints a job, the event log for the print server actually shows that the owner of the job was the LAST user that printed to that print server, not the current user.

 

Our printer support reps found us an article which seemed to fit our scenario perfectly, but the article is only for Vista SP1 and Windows Server 2008 (Not R2). When we download and try to apply the hotfix (On the off chance that it might fix the issue) it comes up with an error stating that the hotfix is not applicable to this operating system (As expected).

 

The article referenced above is: http://support.microsoft.com/kb/958741

 

What we're both wondering now (Myself and our printer support reps) is that if this issue has potentially resurfaced in Windows Server 2008 R2 (Being that the article fits the scenario and symptoms perfectly) but has yet to be fixed, could someone assist us to solve this issue?



↧

Problems with Client Side Rendering Spooler/SpoolerWin32SPL

February 14, 2013, 7:36 am
$
0
0

Hi folks,

I have a small problem on a SBS2008. In the system event are entries with the source SpoolerWin32SPL (when I open the log on a 2003 server the source is Client Side Rendering Spooler), event ID 3 and the following description: The print spooler failed to reopen an existing printer connection because it could not read the configuration information from the registry key S-1-5-21-998185116-1257425660-3357847141-1142\Printers\Connections\S-1-5-21-998185116-1257425660-3357847141-1142\Printers\Connections. The print spooler could not open the registry key. This can occur if the registry key is corrupt or missing or if the registry recently became unavailable.

The first part of the registry key until ....\Printer\Connections\ is present, below this are other keys and also the printers listet who are shared on other systems. The second part who is starting again with S-1-5-21-998185116-....\Printers\Connections is not there.

The problem is that the server is not printing when this error occurs. It looks like that some time after this error occurs the printers are working fine without any action taken but they are not printing the documents that should be printed during this error.

The server is a SBS2008 with SP2, the only updates that are not applied are the ones from the last patch day yesterday.

Thanks for your help.

Mike

↧
↧

W2k8 R2 GPO deployed printers are deployed every logon

February 14, 2013, 7:39 am
$
0
0

We recently migrated from Windows 2003 Terminal server to a Windows 2008 R2 terminal server. For the Windows 2003 Terminal Server I used the per machine GPO to push the printer connections. The printer server runs Windows server 2008 r2 for over a year now. In combanation with a 2003 terminal server it worked really well. 

With the 2008 terminal server it looks like the printers are being pushed at every user logon. When I user logs on and opens directly devices and printer. We see the pushed printer slowly being added. On the 2003 terminal server the printers are directly available when a user log on. Does someone expiernce with this behaviour? Terminal server printing can be such a pain.

↧

Spooler Service is stopping automatically

February 14, 2013, 2:33 am
$
0
0

Hello All,

I am facing printer issue on our printer server, I know its becasue of faulty printer driver,

Could you please let me know how to find faulty print driver details.

Regards

Shyam Hendre

MCP, MCTS

↧
Search

Default Printer Not Being Saved

February 14, 2013, 9:46 am
$
0
0
This is the problem-> The default printer (regardless of the make/model) which I pick stays for about a day but then the next day when I remote in (I do not log off of the terminal server, I just end my session) my default printer goes to one of the PDF writers that I use.

The set up -> terminal server is 2008 R2, back end server is a SBS 2011

Is this a bug with Microsoft because it has been popping up more recently after I moved my servers to the data center. This happens in PCs with XP as a base OS and also with Win7.

Any thoughts?

Mackenzie

↧

Help please. Multiple Computers, Same Domain Username Print Notification

February 14, 2013, 10:24 am
$
0
0

Hello everyone,

I have spent the last 2 days trying to figure this one out.  I have a department of 6 computers all logged in as the same "department user."  They all have a network printer on another server added to their printers.

Sometimes, NOT ALWAYS, when one of the pc's prints to this printer, some of the other PC's will get the notification as well.  I've gone to the server that the printer is on and set the option under remote notification to notify compter instead of user, but it is still happening.  Just to cover all bases, I did the same on each of the department PC's.  However, they are still receiving the notifications from time to time. 

I could disable the notifications all together, but the problem is I need the notification to stay on the pc that actually prints (it's part of a workflow process to confirm that they actually printed it) because it goes to another area of the building.

I've played around with different combinations of settings on both the print-server side and the local pc's without avail.  The next step (which i do NOT want to do) is to install the printer as a local tcp/IP printer on each machine instead of a network printer.

Please help me.


↧
↧

Printing from XP to type 4 drivers

February 14, 2013, 11:09 am
$
0
0

Is there any hope for printing from XP to a Windows Server 2012 print queue that uses a type 4 driver?

We are building a new print server, but expect to still have some XP clients when we go into production. Naturally, I'd prefer to use the type 4 drivers to simplify printer installation and administration, as well as to enable printing from RT.

What are other folks doing? Installing two print queues, one with type 3 and one with type 4 drivers? Thanks,

Tony

↧

How to make Windows Server 2008 R2 printers visible in Print Management console (printmanagement.msc) to help desk support staff who have "Manage Documents" security property

February 4, 2013, 3:19 pm
$
0
0

I have multiple Windows Server 2008 R2 print servers (member servers in a single domain). Several are new and I set up the default print server security properties according to "Assigning Delegated Print Administrator and Printer Permission Settings in Windows Server 2008 R2" (http://technet.microsoft.com/en-us/library/ee524015%28v=ws.10%29.aspx). I added an Active Directory global group called "PrintQueueMgr" which contains all of our help desk support staff accounts. To this group I gave permission to Manage Documents.

I added several hundred shared printers which are published in Active Directory. End users are connecting to these print servers and printing. Call these print servers PRT01 PRT02 PRT03. Our help desk support staff can open Print Management console, add the aforementioned print servers PRT01 PRT02 PRT03 and see all printers (several hundred printers on 3 print servers). They can manage print jobs on those print servers. All is good.

However, we also have a couple of Windows Server 2008 R2 application servers which also have the Print and Document Services role. Call these print servers APP01 APP02. A different sysadmin added local printers (they are not shared). The application generates print output on behalf of users of the application also running on this server. I am not familiar with the application setup, but the printers are very ordinary using a Standard TCP/IP port and built-in print drivers (a variety of Windows Server 2008 R2 print drivers, mostly for HP LaserJet models).

Knowing I would need to grant the AD group PrintQueueMgr with permission to Manage Documents, I did that at the print server security tab on both APP01 and APP02. Also realizing that this permission is not inherited, I selected a sample printer and added the same permission. I restarted the print spooler service. I also added a new local printer with Standard TCP/IP port. I noted that the new printer inherited the Manage Documents permission for the PrintQueueMgr AD group. I did not share the new local printer.

The help desk support staff can add the application servers APP01 and APP02 to their Print Management console. But they cannot see any printers! They can see print drivers, forms, and ports for APP01 and APP02. There is one shared printer on APP01 (not sure why) and that printer is the only printer that is displayed in the Print Management console.   From an RDP console session on APP01 I can PING the computer which the help desk support staff is logged onto (so yes, the host (A) record does exist and is resolvable by the DNS server configured for APP01).

Does the Print Management console only manage shared printers? I don't find this limitation in the documentation. We do not wish to share the application server's printers. Only the application running on APP01 and APP02 should create job output for the printers.

When I, a domain administrator, logon to the same Windows 7 workstation used by the help desk support user account, I can see all of the printers on APP01 and APP02!

What else can I try?

↧

OS X printing to Server 2012 and type 4 drivers

February 14, 2013, 11:05 am
$
0
0

Has anyone tried printing to a print queue with a type 4 driver on a Windows Server 2012 print server from a AD-joined Mac? I can install type 3 drivers and those work just fine. I suspect that it is using the older SMB-based

We are building a new print server and was hoping to use all type 4 drivers (to support printing from RT, among other reasons). Thanks,

Tony

↧
Viewing all 3156 articles
Browse latest View live
Search
<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>