Vista Tutorial - Vista X64 can't print to shared Vista X86

Well I have gotten father than before. However I can't figure out which file
in the repository is for Kodak AIO 5100. Any suggestion? I have tired quite a
few and wrote the entire list down to help troubleshoot.
"Alan Morris [MSFT]" wrote:

Jason,

The print driver is installed by the aioprnt.msi in the [CD
Drive]:\printer\printer. This put the driver in C:\Program Files
(x86)\Kodak\Printer\PrinterDriver. It will have to be run on a 32-bit
system to get the 32-bit driver. You could then copy that to the 64-bit
system and add it.

After running the aioprnt.msi, just double clicking on the shared printer
when you view the server from the 32-bit system may install it
auto-magically as well, but I'm unsure.

-Guy

"Jason" <Jason@xxxxxx> wrote in message
news:B69E7394-5D10-4CAE-B5D1-83894139389B@xxxxxx

Alan, I'm having the same issue with a Kodak on a 32, trying to get to it from Vista 64. I can print to it from a different 32, fine; I can transfer files; all the other symptoms everyone else has.

Following your instructions (thanks for all the details, btw), on the 32 box with the 64 bits printers folder open, at step

Right click any white space and select Server Properties / Drivers / Add

I get "Server properties cannot be viewed. Make sure you've typed the name correctly and that the printer is connected to network"

So, I'm dazed and confused: I haven't "typed" anything from the 32bit machine, and I haven't even specified the printer yet.

I have tried this with the 64 bit driver installed on the 64, and with it removed. Any assistance is most appreciated!

Did you add the 32 bit drivers to the 64 bit PC?
--
Cari (MS-MVP) Printing & Imaging
www.coribright.com/windows

"dazed" <guest@xxxxxx-email.com> wrote in message
news:aecf98fe4a1a77f9bfd4e170992a2257@xxxxxx-gateway.com...

Cari,
Thanks for the quick (and weekend!) reply. Re "Did you add the 32 bit drivers to the 64 bit PC?"...No; I think that is what I was trying to do when I got the "Server properties cannot be viewed" message.

I was following Alan's instructions at the time (sitting at the 32 bit machine):
"You can add the driver onto the 64 bit machine from the 64
bit machine using Have disk but it's easier to add the driver to the 64 bit machine from the 32 bit machine....

From the 32bit machine, open the remote 64bit machine's printers folder. Start / Run / \\remotemachine Open the printers folder. Right click any white space and select Server Properties / Drivers / Add"

Not meaning to point fingers, but I'm curious: I'm willing to wait for the proper fix so that it installs without these work-arounds, but I can't tell: Is it a bug in Vista, a bug in the drivers or is the limitation "as designed" (no printer sharing across 64/32 bit Vista)?

Thanks again to everyone chiming in on this issue! And Jason, if you're still following this, did you get your Kodak to work?

Dazed, what is your precise configuration?

from the previous post this is my assumptions

You have a Kodak printer (model not yet revealed)
shared from Vista 64bit machine
one 32 bit machine (OS unspecified) can print fine to the Vista 64 shared
printer
a different 32 bit machine (OS unspecified) cannot print to this shared
printer


Since one 32 bit machine can print to the shared printer, how did you
install the 32bit driver on this client?


Since you removed the 64 bit driver in your troubleshooting efforts, this
also requires one to first delete the printer. Did the printer get shared
after you added the printer again?

Is there any error on the 32bit client if you just attempt to add the
connection?

Keep the share name simple. Kodak will do unless you have a bunch of Kodak
printers shared from the same machine. The default share name with the
whole model name is too confusing.

If you get access denied verify that the print$ share exists on Vista 64 and
that Everyone has Read access.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"dazed" <guest@xxxxxx-email.com> wrote in message
news:8c1699184468a9464754b664961cb4ca@xxxxxx-gateway.com...

Alan, thanks for the reply. Sorry I didn't supply all the details... I apologize for the “communication breakdown”.


Allow me to summarize before supplying those details:


I'm trying to connect to a Kodak 5100 printer currently running on Vista Ultimate 32 bit, from Vista Home Premium 64, over a home wireless network.


If I try to connect the typical way ("Add network, wireless or Bluetooth Printer" on the 64 machine) it finds the printer but states "Windows cannot connect to the printer. Make sure that you have typed the name correctly and that the printer is connected to the network". If I try the "Create a new port" idea I get "Access denied".


The printer works fine on the local machine of course, and it works over the network on a different Vista Home Premium 32 bit machine (Note I had to use the "create a new port" trick to get it to work though on the other 32 machine). Network file sharing works fine on all machines. Printer sharing is on. By the way, all machines are new OEM Vista machines fully patched all running Avast A/V. Problem has been since day 1 (when I bought the 64 bit machine)


Here is the configuration details:


Printer: Kodak AIO 5100 firmware up-to-date


Attached via USB to:


HP Pavilion (2GB, Dual Core 6420 CPU) running Vista Ultimate 32 6.0.6001 SP1


The “problem” PC I'm trying to attach the printer to via the network is:
HP Pavilion (4GB, Quad Core Q6600 CPU) Vista Home Premium 64 Bit (6.0.6001 SP1)


The machine that connects fine over the network is a Gateway laptop running Vista Home Premium 32, btw.


At this moment, there are no printers at all installed on the 64 bit “problem” machine. What drivers are currently on there were installed via the Kodak CD and/or shipped with Vista or perhaps updated via Windows Update; so I assume they are the 64 bit drivers; but to be honest I can't tell what Kodak names the drivers.


The driver on the “server” (32 bit Ultimate) is unidrv.dll, modified 1/19/08, in C:\windows\system32\spool\drivers\w32x86\3


Unfortunately, your detailed questions were assuming the printer was physically on the 64 machine, but here are the answers:


Since one 32 bit machine can print to the shared printer, how did you install the 32bit driver on this client? All drivers (at this moment in time) came from the Kodak installation CD or were shipped with Vista. Any drivers workarounds I tried have been removed, btw.


Since you removed the 64 bit driver in your troubleshooting efforts, this also requires one to first delete the printer. Did the printer get shared after you added the printer again? Because the situation is opposite of your assumption, the printer never was deleted because it never successfully connected. I was also trying the 32 bit drivers (on the 64) in my troubleshooting efforts, in desperation. Those are removed and the drivers directory is as it was.


Is there any error on the 32bit client if you just attempt to add the connection? No, 32 to 32 works fine


Keep the share name simple. Kodak will do unless you have a bunch of Kodak printers shared from the same machine. The default share name with the whole model name is too confusing. Yes, I did that a few weeks ago, changing “Kodak 5100 AIO” to just “Kodak” thinking it would help. This is the only printer on the network.


At this point, another apology may be required. My original post was in response to your post from 4 weeks ago, when you were explaining a way to connect “... but I have plenty of x64 machines sharing printers to 32 Vista.” I see now it appears you have the printer attached to the 64 bit machine, not the 32 like I do, so I probably shouldn't have followed those steps anyway. Sorry for that.. I interpreted the title of this thread (X64 can't print to a shared X86) to mean the printer is being shared from a X86... but then again, I be dazed. Thanks for all the attention!

Alan:

Your name keeps popping up for solutions to Vista printing problems of the
type that I am experiencing. I am running vista and can see my printers on
other vista Pcs. One is a Kodak 5500 and the other a Canon MP830. However,
whenever I try to attach to the printer, I get the windows cannot connect -
make sure that you have typed the name correctly message. I have tried the
add a port solution and get an Access Denied message. Although I can see the
printer from Windows Explorer, when I click on it, I get an Operation could
not be completed (error 0X0000709) - make sure that you have typed the name
correctly and that the printer is connected to the network. I am also
running windows live onecare and onecare sees the printer but again no
installs. I thought the problem might be onecare so I shut it down. As near
as I can tell, the problem appears to be either a UNC or permissions issue
but I am completely stumped and I have tried every internet solution that I
could find but I simply can't find a solution.

Your help would be greatly appreciated.

Thanks.



"Alan Morris [MSFT]" wrote:

The machine sharing the printer, were these machine upgraded from XP or are
all fresh installs?


G:\>winerror 0X0000709
1801 ERROR_INVALID_PRINTER_NAME <--> No NTSTATUS matched



open a command prompt on the Vista machine that cannot connect. type

net view \\othercomputer


this should list shared printers and folders

Verify that the printer share is correct. I suggest that you make the
shares short rather than the default which uses the print driver name.
KODAK, CANON, LEXMARK, HP, ... It's just easier.

Are all the machine 32bit, 64bit, or a mix? If they are mixed you will need
to get both print drivers and if the two drivers don't have the same name,
they are not the same driver even though both will work with the device.
--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/search/?adv=1

This posting is provided "AS IS" with no warranties, and confers no rights.

"Rob" <Rob@xxxxxx> wrote in message
news:0790C138-8B48-4BCB-860E-36C6FA5B0848@xxxxxx