We help IT Professionals succeed at work.

64-bit print server

Angry_Stu
Angry_Stu asked
on
Grrrr ,I am pulling my hair out here.  Why does everything need to be so difficult!!?

Ok I am trying to rebuild my print server on a 64-bit server 2008 installation.   And it is an absolute nightmare.  I am trying to follow some advice I got in a previous post which is:

*Here's a step by step:
*On any one of the clients machine running 32-bit OS.
*Access the x64 print server \\PrintserverName\Printers.
*Open the printer required to add the 32-bit driver.
*Go to properties.
*Sharing Tab.
*Additional drivers.
*Check the box for x86 for Windows 2000, Windows XP and Windows 2003.
*Click OK.

*Then, locate the INF file of the printer driver for XP 32-bit downloaded driver.
*After doing this, you should now be able to install a shared printer from a x64 OS to x86 OS.

When I try and do this for our large Konica Minolta 750 here, it just tells me that it cannot find a suitable driver, even though I am pointing to it.

I have no idea what I am supposed to do from here, or why it has to be so difficult.
error.JPG
Comment
Watch Question

Commented:
You're going to kick yourself.  If the image posted is valid, you have IA64 selected to add... that's for an Intel Itanium series CPUs which requires a special verison of Windows geared specifically for that chip.  If you want to add a 32bit driver you need to select the box below that, the Intel Windows 2000 or XP (I see you already have the x64 Xp driver installed).  Make sure you are selecting the correct type of drivers to add and pointing to correct driver setup files.

Author

Commented:
I have tried selecting the one below it too, with exactly the same results.

From struggling on alone I have found that the method above just will not work at all.   I cannot ever install 32-bit driver support in this manner.

What I have found though is that generally if I have the 32-bit driver files stored in a public area, I can then add the printer in the usual manner (add printer, network printer, find in directory, double click printer name) and then it will tell me the printers are for a 64-bit OS only.    It will then prompt me to locate the 32-bit drivers manually to continue.

This has worked with two of the printers here, but for another two it keeps telling me they are not valid.    I cannot find a way around this.

From all accounts this is supposed to be an "easy" process, but from what I can see it simply does not work how it should.

Any ideas on what I am supposed to do about the model of printers which my manual method will not work on?   I need to get them operational.

Commented:
WOW!  Haven't ran into that problem but we only have HP printers.  I agree it shouldn't be that difficult, the server should be able to accept valid drivers for either 32 or 64 bits.

Have you checked the vendor site to see if there are any updated drivers?  

Just checked and there are some drivers dated from 12/18/2009 through 5/??/2010 at http://onyxftp.mykonicaminolta.com/download/SearchResults.aspx?productid=877&filetypeid=0

Author

Commented:
Yeah all the drivers I am trying I have downloaded fresh today.

It's funny you mention HP, the two that are working fine here are both HP printers.    It's the Kyocera and Konica Minolta's that are giving me a huge amount of greif.

So frustrating!
I have run into this with the Bizhub. KM's drivers support for W2k8 x64 are horrible. A couple things you can try.
First, try installing one of the built in Konica Minolta drivers right from Windows 2008. They may not have the exact model, but one should work.
You can also try installing the W2K3 driver on the server.
If you don't like that idea here is what I remember about how I had to fix it......
- You install x64 driver on the server.
- Go to the workstation, navigate to print server, \\printerver
- When trying to add the printer it will prompt you for the driver
- Install the XP x86 driver on the client.
Not the most automated procedure, but it will work.

Commented:
Make sure that the version number of the 64 bit and 32 bit drivers match.  If they are not the same you can get this error.

Author

Commented:
Encrypted:

Yeah that's the exact method I am using.  Both versions are phase 2, version 2.0.0.   I went back and had a look at where I got them form and it looks likely that it isn't working due to there not being any server 2008 driver support.  I have used the windows xp 64-bit drivers.

I will try using the built-in server 2008 drivers and see how it goes.   Not sure what I am going to do about these disobedient Kyocera's though.  I have tried using the inbuilt drivers for those, and no dice.

Usecomp:  Thanks buddy, but I am downloading every driver I am using fresh.   Everything is the latest driver available from the vendor, but I will remember to keep double checking all version numbers.
I ended up getting my Kyocers's going. What models are they?

Author

Commented:
I just got the FS-C5015N going.   That one actually works properly, as in I can add x86 driver support to the server itself.   This is the only printer that has worked this way so far!

The model I am struggling with at the moment is the FS-3900.  I will try out looking for some different drivers this afternoon.  See if that helps anything.
I think my Kyocera is a FS-38**. I had to play around with the drivers but I did get it going. I remember somthing about a k-pdl driver. I will check when I get to the office and get back to you.
P.S. Kyocera nd KM are the only 2 I have issues with. All the HP's and Lexmarks work like a charm.

Commented:
Angry_Stu:  Hope you find a solution soon, I know it's a drag to say the least.

For Kyocera try the KX drivers, they are suppose to be somewhat universal.  If the latest drivers don't work try the prior version.

Author

Commented:
I managed to get it all going, thank you so much for all your help guys!

I made sure I had the same version numbers for the 64 and 32 bit drivers, put them in a publically accessible place and then add the printer as normal.   When prompted, navigate to the 32 bit folder on the network to finish the install.

It's not the prettiest solution, but everyone can print now and I have turned from villain to hero haha.

Thanks again everyone.

Commented:
Good to hear you got it working, not as designed but at least it's a solution.  I have a bigger problem; a vendor of a netwrok sharing device refuses to update drivers for Windows 7 which means have to find a suitable replacement.  I told them I hope the rest of the IT world does the same as I'm doing, taking them off my vendor list.  In the mean time I can upgrade a number of XP systems until we get replacements for the device.  Not really that much of a problem as most users don't like Windows 7.  I'm being told 'take your time finding a replacement'. LOL

Author

Commented:
That's a bit lame.  Lack of driver support is something that turns me completely off a particular vendor also.  Hope you find a better solution!