Re: Server 2003 32-bit Queue with XP Pro 64-bit

Thanks for the info and response. I did get a message from one of you fellow
MS employees. I now have the x64 printing functions installed on the x32
server OS and was successful in adding the drivers for the printer to the
Share tab of the properties. However, now when I go to the x64 XP Pro
workstation and browse to the server to see the printers, then find one that
I know has the x64 driver and click it to open it to connect, the following
error immediately pops up under the window title of Printers:
Operation could not be completed. Either the printer name was typed
incorrectly, or the specified printer has lost its connection to the server.
For more information, click Help. [OK] [Help]

So I feel like we are making progress but the error is still happening. This
is the same error I used to get as well. Seemingly it has made no difference
that the drivers for x64 are now on the server. Almost as if that isn't
related to this error at all.

"Alan Morris [MSFT]" wrote:

This works fine but the Server requires SP1 for x64 driver support.

I was assuming this but if you are not running with a service pack (go for
SP2 since it's out), then adding x64 print drivers is not possible.



The driver files you are installing should also be engineerd for Server 2003
x64 (or XP x64) which will include the inf decorations for x64 support

open the inf for the device driver you are attempting to install. If you
see a layout.inf section you can only install the x64 driver using an x64
machine to remotely install the driver to the 32bit print server. I found
many Xerox drivers use this


[Version]
Signature="$Windows NT$"
Provider=%HP%
ClassGUID={4D36E979-E325-11CE-BFC1-08002BE10318}
Class=Printer
CatalogFile=hpc4700u.cat
DriverPackageType=PlugAndPlay
DriverPackageDisplayName=%HP_Mombi_Driver_Name%
DriverVer=02/24/2007,61.071.661.41


inf decorations (no clue why this name)

[MANUFACTURER]
%HP%=HP,NTAMD64,NTAMD64.6.0






--
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.

"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:A3EB8666-69FA-4F75-A0C3-528D9A78CEB5@xxxxxxxxxxxxxxxx
Alan, thanks for the attempted help and don't feel like you have to give
up
now, but I did have to contact MS to get paid support on this issue as I
have
3 brand new machines sitting doing nothing while I am trying to figure
this
out.

I don't see how what I am wanting to do is so "out there". I just want to
be
able to print to the queue on the 32bit server from a 64bit XP client.
Doesn't seem that hard. But apparently it is. Maybe it can't be done? I
dunno. Maybe the server HAS to be 64bit as well? Or maybe the client can
only
print to the printer via the IP address independent of the server?
Hopefully,
the person that contacted me via phone yesterday will be able to provide
help
where every other avenue has failed. Thanks anyway. : (

"CB" wrote:

The printer share is on the Server 2003 x32 environment.

"Alan Morris [MSFT]" wrote:

No dunce, it's okay. I've just been doing this action for the past 4
years.

I was under the impression you were sharing the printer from a 32bit XP
machine.

What OS is the machine sharing the printer?


--
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.

"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:42B6503C-5564-4ED7-B2BD-EF41E98B00EE@xxxxxxxxxxxxxxxx
So if I understand you correctly, you are saying I can add teh driver
to
the
server machine via the XP x64 machine?
I don't understand the part about "must be named the same". If it
isn't
the
same, how do you change it? If it is the same, what should happen?

So I'm on the server console. I then go to the XP machine with start
> Run
>
\\xpmachinename. Then I get the printer object and then get to the
properties
of that printer? If it is already installed on the XP machine with
the x64
dfiver, how can I add the x64 driver? I am obviously missing
something.
Sorry
for being a dunce...

"Alan Morris [MSFT]" wrote:

You will need to install the vendors x64 print driver onto the XP
machine.
The easiest way to do this is to use the x64 machine and remotely
add the
x64 driver. The driver name must be named the same as the 32bit
driver
or
it's not the same driver.

Start
Run
\\XPmachine

Open the remote printers folder, File , Server Properties, Drivers,
Add
Driver


Read the file prompt dialogs as they pop. If you don't get it
right the
first time just try again

XP 64bit is the client version of Server 2003 (released the same
day,
they
run the same bits).

--
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.

"CB" <CB@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:1DEE902E-E3A7-4BC8-968E-08870865E592@xxxxxxxxxxxxxxxx
But most importantly, how do I fix the error so I can just add the
printer
to
the 64-bit workstation?

"CB" wrote:

We have a printing tracking program that we use for billing. 3
new
machines
for CAD design were ordered that have XP Pro 64-bit edition. The
software
that does the print billing uses the server queue to monitor for
print
jobs.
There is a client that runs on the workstation. When the print
job
hitws
the
queue, the software tells the server that a job arrives which
triggers
the
server to tell the client to pop-up a web interface that lets you
choose
the
job number to assign it to. On the 32-bit XP workstations, this
all
works
fine.
The 64-bit machines however, I can't even install the printer
from the
queue. When I try, I get an error that states...
'Windows cannot connect tot he printer. Either the printer name
was
typed
incorrectly, or the specified printer has lost it's connection to
the
server.' This error pops up whether I choose the printer through
browsing
to
the server with just Start > Run > \\servername\ <enter>, or the
print
install wizard, or the IP address, or any method. I can't get to
the
queue of
the server with the 64-bit workstation.
I also tried adding the printer as a local printer but giving the
port
as
\\<servername>\<printqueue>. That works for printing but again
bypasses
the
print auditing software. So it must not be actually going though
the
queue.

I have searched endlessly on this error and everyone's solution
is
either
upgrade the server to 64-bit or install the printer as a local
port IP
printer. Upgrading the server isn't that easy and for the print
auditing
software, I can't use the second solution. If I setup the printer
as a
direct
IP printer, it works fine. But of course bypasses our print
auditing
software.

How can I fix the error so I can get to the server queue?
Additionally,
when
I try to add the printer driver for 64-bit to the server queue
itself,
it
asks for the Server 2003 64-bit install disc, which I have, but
that
is
not
what is on the server. I don't want to jack up the server for
everyone
else
so I haven't put that disc into the server to let it copy files.
Do I
need to
do that? And will it mess anything up?









.

Relevant Pages

  • Re: Shared Printer
    ... Brother HL1430 can not used on the SBS server box and client workstations. ... driver must be installed on the computers. ... If you try to install the drivers from the Brother CD-ROM into a Windows ...
    (microsoft.public.windows.server.sbs)
  • Re: Printing issue in XP over Remote Desktop VPN
    ... You will need to install the driver on the remote machine only if you are ... So your saying I should install the print drivers on the machine I'm ... Look for Terminal Server event ... Print Terminal Server Applications to Local Printer ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Printing issue in XP over Remote Desktop VPN
    ... I am trying to remote to another XP machine. ... So your saying I should install the print drivers on the machine I'm ... Look for Terminal Server event ... a driver that is not available on the Windows 2000 Server. ...
    (microsoft.public.windowsxp.print_fax)
  • Re: Dude !! Never Buy a Dell !!!
    ... Sounds like when you "converted" from Home to Server, you didn't install the ... go to Dell site, download the Driver, and then when installing the Driver, ... it complains, that the CD drive is missing, Darn, thing.. ...
    (microsoft.public.windows.server.general)
  • Re: XP 64
    ... and this includes the "press F6 to add some driver" message. ... The only difference during install is that xp x64 knows more newer hardware since it's around 4 years younger than 32bit xp, ...
    (comp.cad.solidworks)
Loading