Printershare Generic Driver Pack

PrinterShare fornisce supporto di stampa nativo su. Analizza e scarica da sola i driver di stampanti obsolete come. Added generic driver for Eltron. These drivers are distributed under GNU General Public License, version 2. App Info: App name:PrinterShare Android - only Paid - Week 36 2016 - APPS.

I've installed Server 2012 as a print server (Print server will be the only function of this server). I'm now trying to add printers. The first one I've added is a HP 2035 with the Windows update HP Universal PCL6 driver. If I chose to share the printer during the setup I receive 'There are no more endpoints available from the endpoint mapper.' If I choose not to share during the setup, it adds without any issues.until I launch Properties and attempt to share it.

I'm finding it doesn't seem to matter what driver I use, whenever I share I end up with the same result. I've also tried using the PCL6 Universal Driver from HP, no change.

I'e been researching this issue for hours without any change. By default, we disable firewalls on servers (Some TN thread suggested checking to ensure the firewall is disabled). Spooler isn't crashing. I've tried adding a few others printers, running into the exact same issue.

Why is trying to share the printers causing this issue? I've seen some people state they get this error when disabling the Windows Firewall service. I've never seen the error with the service disabled but it may be the replacement software interfering.

If it's off start up the service and let us know the outcome. Alan Morris formerly with Windows Printing Team This is the answer, for some reason even sharing printers from PC's in Win7 and Win8 wont work unless the firewall is running.

Start the firewall and share the printers then stop it again if you do not require it. I've seen some people state they get this error when disabling the Windows Firewall service. I've never seen the error with the service disabled but it may be the replacement software interfering. If it's off start up the service and let us know the outcome. Alan Morris formerly with Windows Printing Team This is the answer, for some reason even sharing printers from PC's in Win7 and Win8 wont work unless the firewall is running. Start the firewall and share the printers then stop it again if you do not require it. I wish I knew or could even reproduce the issue.

The error message is from the Server Service when the share for the printer is added. The print spooler does not take a dependency on the firewall service and one can add a printer that is not shared without issue. The Server Service team did investigate and also stated they do not have a dependency on the firewall service running but since no one was ever able to replicate the issue at MS, there was never anything to fix. Alan Morris formerly with Windows Printing Team.

I'm trying to add x64 under additional drivers for our existing 32bit printer shares on x86 2003 Server sp2. If i try to add x64 drivers for say, laserjet 2200, I browse out to the x64 2003 CD for the inf file under AMD64. It then prompts stating: 'the specified location does not contain the driver HP LaserJect 2200 Series PCL 6 for the requested processor architecture'.

I tried this same routine for our Phaser 6250DP printer, if I browse to the x64 folder, where we have the specific x64 drivers for it, I get the error 'selected driver must be installed remotely'. Is it not possible to install an x64 version of a printer driver on a x86 server (not itanium)?

Have you all tried this method: 1) On the x64 machine, from Start >Run, type, where servername = the name of the x86 print server. 2) In the list of shares, open the Printers folder.

3) Right-click in the Printers folder and select Server Properties. 4) Go to the Drivers tab and add a new x64 driver.

The x64 option should be there since you are viewing the printers folder on the x86 machine from the x64 machine. This process should work if there is an inbox driver. Otherwise, you'll have to provide the location of the OEM driver. The print server must have both x86 and x64 drivers to be able to serve them to clients. The driver for the architecture of the server can be installed the usual way.

The driver for the other architecture must be installed from a computer using that same architecture. You then need to open the 'Printers' share on your print server from that other computer and add the driver in the server properties. Here's an example. You have a Windows Server 2003 running on a x86 processor and Windows Vista clients running on a x64 processor. Install the x86 driver directly on the server.

Log on a Vista computer (using an account with sufficient privilege to access the server!). Open in Windows Explorer. Go to File, Server Properties. In the Drivers tab, click on Add.

Select only the x64 architecture and browse to find your driver. The x64 will be uploaded to the x86 server.

Please note however that both x86 and x64 drivers must have the exact same name! 'HP LaserJet 2200 PCL 6' and 'HP LaserJet 2200 PCL6' are regarded as totally different drivers! If they have the same name, they will appear automatically in additional drivers for both architectures in your printer's sharing properties. Right-click the printer to which you want to add additional printer drivers, and then click Manage Sharing.• Click Additional Drivers. The Additional Drivers dialog box appears.• Select the check box of the processor architecture for which you want to add drivers.

In your instance this would be x64.• If the print server does not already have the appropriate printer drivers in its driver store, Windows prompts you for the location of the driver files. Download and extract the appropriate driver files, and then in the dialog box that appears, specify the path to the.inf file of the driver.

The driver files you install must match the drivers installed on the print server (the printer name must be identical as well as the driver version). Note You might not be able to extract some printer drivers without installing them. If this is the case, log on to a client computer that uses the same processor architecture as the printer drivers that you want to add to the print server, and install those printer drivers. Then use Print Management from the client computer to connect to the print server, and add the additional drivers from the Additional Drivers dialog box. Windows automatically uploads the drivers from the client computer to the print server. I hope that this helps!

I have had a similar problem in the reverse, trying to install x86 additional drivers on x64 servers. I had to go to the manufacturers website to download new drivers.

I found that the x86 and x64 drivers must have the same name and if you have installed the PCL x86 drivers then you must install PCL x64 drivers. They cannot just be similar drivers. I would suggest downloading the drivers again making sure they are the same driver but for different architechtures, you will probably also find that many of your printers may not even have x64 drivers so you will have try similar drivers. Have you all tried this method: 1) On the x64 machine, from Start >Run, type, where servername = the name of the x86 print server.

2) In the list of shares, open the Printers folder. 3) Right-click in the Printers folder and select Server Properties. 4) Go to the Drivers tab and add a new x64 driver. The x64 option should be there since you are viewing the printers folder on the x86 machine from the x64 machine. This process should work if there is an inbox driver.

Otherwise, you'll have to provide the location of the OEM driver. The print server must have both x86 and x64 drivers to be able to serve them to clients. The driver for the architecture of the server can be installed the usual way.

The driver for the other architecture must be installed from a computer using that same architecture. You then need to open the 'Printers' share on your print server from that other computer and add the driver in the server properties. Here's an example. You have a Windows Server 2003 running on a x86 processor and Windows Vista clients running on a x64 processor. Install the x86 driver directly on the server. Log on a Vista computer (using an account with sufficient privilege to access the server!). Open in Windows Explorer.

Go to File, Server Properties. In the Drivers tab, click on Add. Select only the x64 architecture and browse to find your driver. The x64 will be uploaded to the x86 server. Please note however that both x86 and x64 drivers must have the exact same name! 'HP LaserJet 2200 PCL 6' and 'HP LaserJet 2200 PCL6' are regarded as totally different drivers!

If they have the same name, they will appear automatically in additional drivers for both architectures in your printer's sharing properties. I see several have done the reverse successfully. I am testing Longhorn x64 and was attempting to load additional x86 drivers for a Lexmark X945e. Had to go through a 32 bit client (Vista Ultimate) to the server's printer folder, unhide the menu bar to access Server Properties, and attempted to install the additional drivers from there.

However, once I navigate to the drivers folder and hit OK, it acts as if loading the appropriate x86 drivers, but ends up cycling through an install window with a progress bar probably a dozen times before it gives me the following error: Unable to install Lexmark X945e, Type 3- User Mode, x86 driver. Operation could not be completed (error 0x800f0247 ).

In my case I have a windows 2003 x64 witha shared printer hp 3600 with a x64 driver. I have windows x86 clients that need to print to it. I added the x86 driver from a windows xp x86 on the windows 2003 x64, and was able to install the printer on the XP computer.However when I sent a print test from the xp computer it shows this error.

'Test page failed to print. Would you like to view the print troubleshooter for assistance? Operation could not be completed' Any help will be very appreciated. I've followed your instructions, but am still unable to get this to work. We have a Windows Server 2003 (Small Business Server) running on an x86 CPU. We've just got a couple of new workstations running Windows XP Professional x64. On the workstation, I browse to the Printers and Faxes Folder on the server, go to Server Properties, Drivers tab.

I click Add., Next and I get a list of processors and operating systems to choose from. The only options here are Itanium and x86. The x86 drivers are already installed, so I select Itanium, even though from what I understand, that is different to x64 (?).

I select the x64 driver, click Finish on the wizard. The system copies the files, but then gives me a message: 'The files installed are not valid for the selected architecture'. Where is the option to install x64 drivers?? Right-click the printer to which you want to add additional printer drivers, and then click Manage Sharing.• Click Additional Drivers.

The Additional Drivers dialog box appears.• Select the check box of the processor architecture for which you want to add drivers. In your instance this would be x64.• If the print server does not already have the appropriate printer drivers in its driver store, Windows prompts you for the location of the driver files. Download and extract the appropriate driver files, and then in the dialog box that appears, specify the path to the.inf file of the driver. The driver files you install must match the drivers installed on the print server (the printer name must be identical as well as the driver version). Note You might not be able to extract some printer drivers without installing them.

If this is the case, log on to a client computer that uses the same processor architecture as the printer drivers that you want to add to the print server, and install those printer drivers. Then use Print Management from the client computer to connect to the print server, and add the additional drivers from the Additional Drivers dialog box. Windows automatically uploads the drivers from the client computer to the print server. I hope that this helps!

Right-click the shared printer and select Connect. Your XP machine will warn you that you are about to install software from the server, etc. I explained everything in detail because I wasn't sure what experience level you had and thought a step by step might be useful to others. So when sharing printers and adding additional drivers of different architectures, just remember it's going to look for two things. First, you'll need the actuall 64bit/32bit printer driver you want to share, which should be provided by your printer vendor. Second, you'll need the print architecture files to be able to share that printer to a machine with a different system architecture.

If you're installing on Server 03 32-bit, an XP 64-bit CD will suffice, and vice versa for Server 03 64-bit. For Vista, it's a different story.

I'll post a step by step for Vista later. Zeff, Thanks for your help. I'm unable to follow your instructions past step 3 because on our Windows Server 2003 installation, there is no x64 Processor option on the Additional Drivers dialog box. The only options I have are Itanium or x86. Is there a patch or something for Server 2003 to enable this? The server is Small Business Edition - I didn't mention that before, I don't know if that makes a difference.

I have tried installing the x64 drivers with the Itanium option and it didn't work. I understand that Itanium is different to x64, so didn't spend too much time with that. In answer to your assumptions: Yes, I have the printer installed and shared on the server. I don't think there are any x64 drivers on the printer driver CD, but we've downloaded some off the internet.

No, I don't have an install CD for XP 64 as it is an OEM install, but I'm sure I could find the file/s I need when I get to that step. Thanks again, Bernie. I ran into this problem too and found another solution (which works for Vista too), so I just wanted to share it: In our case the client workstation is running Vista x64. And I couldn't get the server to install the x64 drivers from the CD *or* find them for download from HP's support site, so I ended up following the steps in KB 895612 () to add the printer locally but providing the network path in the port name.

(Look for the 14-step list of directions under the subheading for 'How to choose a compatible printer driver if you cannot locate a printer driver for your printer') Basically, you pretend the printer is a local printer, but you give it the path to the network printer when you create a new local port. This ends up printing the job locally and then redirecting it to the network printer. It worked for me, and I was able to select a compatible driver from the *workstation* instead of having to use whatever driver was on the server. The KB says the downside of this method is that the workstation will not automagically pull down any driver updates on the server, but that seems like a pretty minor drawback. Hope this helps someone since I spent way too much time on this.

Alexander, Brilliant mate! Your last paragraph with the bit about all drivers needing to have the exact same name was the key to my problem. I have a Vista x64 print server, and nothing I seemed to do would allow me to install the 32-bit XP driver (x86). Printing with Vista worked perfectly but it just wouldnt' connect with XP.

I even have my Vista print server in a dual boot config, and when it boots into 32-bit XP, all computers could print without difficulty. All I needed to do to fix Vista was to rename the printer name (and the share name for good measure) so that it exactly matched the XP driver name.

In my case, Vista automatically picked up my printer as 'Epson Stylus Photo 895 (M)' on install, but on my laptop running XP, the driver was named the same way but without the '(M)'. As soon as I renamed the printer on Vista by simply deleting the '(M)', XP started printing.

No need to actually install anything as XP had long ago had the correct driver installed. I found a relevant link that helped a lot. My specific case: 1. Had a Windows Server 2003 SP2 Small Business Server. Installed domain controllers with Windows 2008 x64. Was unable to add x86 drivers to the printer server.

NOTE: I tried even with Windows XP x86 client, but it would only download the drivers locally. I believe that Vista will push, but not XP x86. From client the add additional drivers button on the sharing tab was grayed out. Reference Link that solved the issue: What I did. I followed the steps to export the printers from the old server and install them on the new print server.

I made sure no printers were installed when I did this. I set them also to overwrite any existing printers. Despite a couple of errors it worked like a charm. NOTE: RD to the server and open each printer.

It will complain about not having the drivers installed, and just click 'ok' to install them. It is really complaining about the x64 drivers since the x86 drivers were imported already. This seems to bypass the printer driver problem with them not being named the same, and so far I can print just fine.

I know this won't help folks with fresh installs but for those of us upgrading their infrastructure this seems to do the trick. Hope this helps. Hi re your post Posted on 03 May 2007 16:02:37: 'Here's an example. You have a Windows Server 2003 running on a x86 processor and Windows Vista clients running on a x64 processor. Install the x86 driver directly on the server. Log on a Vista computer (using an account with sufficient privilege to access the server!).

Open in Windows Explorer. Go to File, Server Properties. In the Drivers tab, click on Add. Select only the x64 architecture and browse to find your driver. Powerdvd Serial Number Free. The x64 will be uploaded to the x86 server.' I would like to do this but the Add Drivers button is grayed out.

I have tried various ways, but how do I make it so that my user account on my Vista Home Premium Laptop has the relevant user permissions to access my XP Home print server with a Dell AIO 924 printer shared off it? Do I set these perimssions from the server end or client end. I also recently struggled with this scenario using a Windows Server 2003 x86 server with Windows XP x64 clients, using HP 2840 printers. This thread certainly helped me in solving the issue, but the method I used hasn't been mentioned here so I'll share. Download and extract the appropriate x86 and x64 drivers from your printer vendor to your Windows Server 2003 machine. In my case, the only x64 PostScript driver for the HP 2840 was the HP Universal Print Driver for Windows.

There were many more options for x86 drivers, however I downloaded the x86 version of the HP Universal Print Driver for Windows as well. On the Windows Server 2003 machine, open 'Printers and Faxes', click on the 'File' menu and select 'Server Properties' 3. Select the 'Drivers' tab and click the 'Add' button. When presented with checkboxes, check the x64 and x86 boxes for Windows XP / 2003 5. You should then be prompted for the location of the printer drivers twice. Simply navigate to the location you extracted either the x64 or x86 drivers depending on which one it asks for and select the appropriate.inf file.

Now try adding your printer, or if it is already added, change the driver on the 'Advanced' tab of the printer properties to the one you just added. After clicking 'Apply' it may take a few seconds, then go to the 'Sharing' tab and click on the 'Additional Drivers' button.

You should now see both the x64 and x32 drivers checked off. Hope that helps. I solved the reverse issue here. We had the following situation: Printer Server Installed on W2K8 64-bit Clients are all WinXP 32-bit Got prompted for driver installation when adding printers on alll clients. Could not install the x86 driver on the 64-bit server using any of the methods above, always got this error: 'The selected driver must be installed remotely from an x86 computer using Type 3 (User mode) drivers.'

Install W2K8 32-bit 2. Install Printers using x86 drivers 3. Go to Admin Tools->Print Management 4. Choose x86 server 5. Right click->Export printers to a file. Go through the export 7.

Connect to x64 server 8. Choose x64 server 9. Right click->Import printers from a file 10. Go through the import This got the x86 drivers installed on the 64-bit Server, and the 32-bit clients can now connect to the printers without being prompted for drivers. Has anyone tried doing the printer export thing on a PC?

I don't think installing a server OS is a valid solution to a printer problem. I'll try the PC method and report back. BTW, several people have mentioned that when installing a printer driver on a client it uploads to the server.

This does seem to be true. I see it now in the list of drivers on the print server.

However, it doesn't show up when I got to manage sharing. I still have the box for x86 empty. People say the driver has to have the same name. And it does, and that is the same driver that shows as the driver for x64 (what the server is). But it has not added itself as the 32 bit driver. I have seen this work, but for the PS driver and I need this PCL driver to be used instead. Damn Toshiba!

LOL What's more irritating is that the drivers from Toshiba don't work right - they cause a conflict between the server and client resulting in very slow printing. When the same client driver is used to print directly to the IP of the printer, it prints very fast. What I'm doing as a temporary solution for a few users who have to print large docs now, is installing the printer toas a local printer (TCP/IP) using the MS universal driver, then deleting it. That causes the mapped printer from the server to use that driver.

The irritating thing is, I can't get that driver to show up on the server! How do I download a MS driver without using Windows Update? Just had the same issue getting the 'not requested processor architecture' error when adding Vista x64 additional drivers on server 2003. I tried the solution to add from the Vista x64 machine and 'Add' was also greyed out, regardless of whether explorer was run as administrator or not.

I decided to go back to the server and dump the inf to see what architecture it was listed for. In my case the Vista x64 printer driver was for 'ntamd64.6.0'. That should be the right architecture, but maybe server 2003 is getting confused on the.6.0 extension? I changed the occurrences to 'ntamd64' and saved the inf. Tried adding it again as a x64 additional driver and this time server 2003 accepted it.

Double-clicked the network printer on the Vista x64 machne and it proceeded to install the driver, printed a test page and everything works. Apparently, server 2003 only likes infs with 'ntamd64' and considers 'ntamd64.6.0' as a different architecture. If you're still having the same problem, i would go and check the manufacturers website. You may just be using the wrong 64 bit driver. I've run into this when installing the XL drivers but if i switch to using the universal drivers for a lexmark T644 in this case and everything worked hunky dory. Tips: - Driver name for x64 bit and x32 bit drivers need to match!

- To install a 64 bit printer driver you need to install it while on a 64 bit machine - To install a 32 bit printer driver you need to install it while on a 32 bit machine Cheers. I have the same problem. Now that there seems to be a solution for this issue, can someone (MS?) please summarize the procedures needed to get the printing problem resolved. My situation is this: 1) I have some HP, OKI and LexMark networked printers. 2) All the networked printers connect to a windows 2003 x86 SP2 server via TCP/IP.

Each printer is shared. 3) I now have about 20 Windows 7 x64 workstations.

They can't map to the print queues on the windows 2003 x86. I see number of solutions mentioned above in this thread.

I would appreciate it, if someone can summarize the steps needed to get this issue resolved. It will tremendously help other admins as well. I sure hope there is a KB article by now. I'm logged into my Win7 system with domain admin perms and have run the PrintManagement.msc to provide the x64 drivers for my x32 Windows 2003 Server. I tried using the HP universal drivers and the built in Win7 drivers for the the PCL and PS versions of an HP 4650.

It absolutely doesn't work. If I look at the 2003 server the x64 drivers are not listed as being available, even though they were added via the msc snap in. This is another major MS failure and judging from this thread, it's been over three years and it still hasn't been fixed. BTW, I made super duper extra sure that the driver names matched. If I have to provide a separate print server for x64 clients I shouldn't have to pay for an extra server license..

I'm having similiar issues, and ready to scream! I have a SBS 2008 and a XP Pro workstation environment. I have a HP LaserJet 2600n installed on the server (x64) and I have gone through the steps to add the (x86) driver to the server also. When i go to add the printers to the workstations it looks like it adds it and then when I right click on it it tells me it needs to add a driver. I add the driver and then a window pops up that my Windows Explorer has stopped working. And then at that point if i try and print it won't.

It stays in the printer log and i have to start and restart the print spooler on the server. I can print from the server but when i try print from the workstations it always gets stuck in the que and doesn't print. I'm not sure where to go from here. Any help would be much appreciated. If the 32bit driver is installed on the server AND the printer is attached over USB on the server, uncheck Enable bidirectional on the ports tab of the printer in order to get around this security issue with the Zenographics language monitor software. If you still need assistance with the 32bit driver, you first need to remove any traces of any other version of the driver on the client machine, then ONLY install the exact same version of the driver that is installed already on the x64 server.

Alan Morris Windows Printing Team; Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1. Are you using version 6.2.0.0? The driver works for a net connected device (HP network card) with and without the Bidirectional setting (for networked devices Bidirectional typically does not matter). If you updated an existing printer to the latest driver, add a new printer instead and see if this clears up the explorer crash on 32bit clients.

This typically means the private section of the device mode has something in it that the 32 version of the driver cannot support. Normally creating a new printer will correct this when using the same version of the 32bit and 64bit driver. Alan Morris Windows Printing Team; Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1. So, how does one go about renaming a driver. It's just plain rediculous that drivers on a 2003 32bit machine have an extra space in the driver name, or an extra letter, or whatever. I need to get the 32bit and 64bit going on an R2 printer server.

The 64bit goes just fine of course however, the issue is the 32 bit driver straight from hp has a space in the PCL6 name: 64bit driver: 'HP Color LaserJet CP2020 PCL6' 32bit driver: 'HP Color LaserJet CP2020 PCL 6' So because there's an extra space there means that I'm screwed. Seriously Microsoft?? Did someone just get to this point during the programming and say, well that's enough work on the printer area. I've got 20 different types of printers and after days of working on it, I've got 2 of them going with 32 and 64 bit drivers and working. The others won't go because they're driver names are different.

Is there an easy way to rename these drivers? Or, is that just the way it is and it's final? I tried every way of installing the drivers that google could find, it won't work without the same name drivers.

So, how can I make it the same? Do I know the frustration, yes. But unless there is some mapping table that would require additional admin maintainance, there is not a better way to make sure someone does not the share the 'HP Color LaserJet CP2020 PS' driver in the cross platform case which has a completely unique device mode. The cross platform print driver is not associated with a print queue, the association is by name. I do not recommend breaking the digital signature by editting the name in the MODEL field of the inf for the print driver, but you can do this. Then install the 'new' driver using the matching model name as that of the 64bit driver.

I'm actually hoping you have already found this method from another source or figured this out, since you seem like a smart guy, so I was not the one to point you in this direction as I hate this as a solution. The name matching has been a requirement for the past 17 years. Let me know when you get this accomplished or if you need some additional instruction. The print driver names will be in ' under the [VENDORNAME] Alan Morris Windows Printing Team; Search the Microsoft Knowledge Base here: http://support.microsoft.com/search/Default.aspx?adv=1.

In response to Outbacker, (Granted I know this is an old post, but I can't find too much information on this subject) Ok I am trying to do something similar, but I have Windows 7 64 bit client machines and Windows 2000 32 bit Server. I follow the steps above. I am on the 64 bit Windows 7 client, go to start, type 'Run', then I type the servername. This works and I can get to the print share and click 'View Remote Printers' which takes me to the 'Printers' folder. I can view the 'Printers' folder 3. I cannot right click on the printers folder because 'Server Properties' is not an option here. I can go to 'File->Server Properties' 4. I can click on the 'Drivers' tab, I can highlight the printer I would like to update, I can click 'Add', but all I get are '86x' and 'Itanium' check boxes.

I can select either one of those options and click 'Have Disk', but because there is no 64 bit option, it will not let me install the 64 bit driver. It is not just this printer driver, it is others as well. I have 5 different printers and they all do the same. My question: Is this just not possible to do on a Windows 2000 32 bit server?

Matt Epstein, thank you. Even though it's several years later.:) ( ) to add the printer locally but providing the network path in the port name. (Look for the 14-step list of directions under the subheading for 'How to choose a compatible printer driver if you cannot locate a printer driver for your printer') I have Windows 7 64-bit, and my wife's XP Pro 32-bit is sharing a particular HP printer that requires an alternate driver. This solved it for me. (I know - wrong forum thread for my situation. But was the only thread I found with the answer.). SCENARIO: Print Server Windows Server 2003 R2, station Windows 7 with 64 -bit and HP LaserJet P4015n PROBLEM: Windows 7 64 -bit stations can not add HP LaserJet P4015n from print server Windows Server 2003 R2 showing the error 0x000007e SOLUTION: In the print server, delete the registry key 'HKEY_LOCAL_MACHINE SOFTWARE Microsoft Windows NT CurrentVersion Print Printers [ PrinterName ] CopyFiles BIDI ' CAUSE: The station of user was trying to access a path that the 64-bit operating systems do not recognize as valid: ' spool drivers w32x86 3 '.

This path is set in the printer settings on the P rint Server. Example: None of the 'solutions' above worked for me. Since I can't find an HP x64 driver for the printer whose name matches exactly Windows won't let me add one to the existing share. I've done it by editing the INF before but with HP it's hard to tell which one to edit. The alternate method, where I upload it from the x64 client, runs into the same problem.

After a frustrating hour or two, I've created a new share, called HPCP2025DNUniversal with the HP universal driver installed, x86 and x64. Now I can connect to it from Win7x64. Try to find drivers for your printer with matching descriptions and create a new share with both drivers added, or change the drivers on the existing share (and listen to the users whine about you changing things). That seems to be the only way around this. Why Windows can tell that the driver will work with the printer when I try to install it locally but can't tell when I try to add it to the share on the server is beyond me.

One of those questions only MS can answer. Well, try thihs. ( this may be your temp solution until you migrate your servers to a proper Architecture) I assume you can Dowload or Have x64 Drivers for your printer( no name matching) if installing it on different architecture and vice versa(x86 if installing it on x64 server). On your Client Machine which is joined to the domain( not necessary) go to add printer, add a port, choose tcp/ip and use IP address of your Network printer, if it prompts for drivers use the ones you already downloaded or have Extracted from CD to a folder on Client Machine.

Most vista and w7 workstations will recognize your printer by deafult actually and you just clik next and finish. So this scenario is printing to a port while using drivers installed locally on the machine doesn't matter x64 or x86. In Domain if you have stations with x86 and x64 and they both print to same printer you need to have both drivers installed on printer server( on your server). Method from Outbacker should work. I know this is a bit of an older thread, but I ran into this issue yesterday when we purchased a new Win7 x64 machine and added it to out Win 2003 x86 domain. We have three printers connecting as part of a logon script, and one of them is an HP LaserJet 1320.

I was able to get the printer to work by installing it locally and then changing the port, as suggested somewhere in the comments (sorry I've lost track after looking at so many threads). However, I was forced to change the logon script for this computer to exclude the HP printer, as it errored out every time the user logged on. Just a few minutes ago I decided to instead try the Vista x64 drivers for the printer, which I downloaded from HP.com, and then the first solution offered by Jason Gerend on this thread worked like a charm. I hope this helps someone!