Printing to a network printer in Publisher 2003

When I try to print to a network printer in Publisher 2003 I get the
following error messages

"Publisher cannot continue printing because of an error. For more
information, press F1"

followed by

"Please choose another printer.

Publisher cannot find the printer \\printserver\printershare for this
publication. To select a different printer, click OK.
To return to Publisher now, click Cancel."

All my other Office XP products print fine as do non-microsoft apps. Can
anyone shed any light on this?

neilvilla wrote:
When I try to print to a network printer in Publisher 2003 I get the
following error messages

"Publisher cannot continue printing because of an error. For more
information, press F1"

followed by

"Please choose another printer.

Publisher cannot find the printer \\printserver\printershare for this
publication. To select a different printer, click OK.
To return to Publisher now, click Cancel."

All my other Office XP products print fine as do non-microsoft apps.
Can anyone shed any light on this?


Publisher hates networks. You cannot (AFAIK)

1) Save Publisher files to a remote drive
2) Print to a remote printer


--
Facon - the artificial bacon bits you get in Pizza Hut for sprinkling
on salads.

While waiting for decisions from his 6 university choices, Ed sees a
message from Miss Perspicacia Tick . On it is
written:
Publisher hates networks. You cannot (AFAIK)

1) Save Publisher files to a remote drive
2) Print to a remote printer

FWIW, although saving to a network drive and installing to/running from a
network drive are not advisable, I've never seen anything wrong with
printing to a network printer. The only thing I've seen that could cause
problems is if the printer was installed by a batch script at logon.

--
Ed Bennett - MVP Microsoft Publisher
http://www.mvps.org/the_nerd/
Before reading this message, view the disclaimer:
http://mvps.org/the_nerd/disclaim.htm

Publisher is different in its approach to printers than other Office products. Could
be the printer driver may need updating.
This article has suggestions for solutions
How to troubleshoot problems that you may experience when you try to print to a local
printer by using Office programs in Windows XP
http://support.microsoft.com/default...b;en-us;870622

--
Mary Sauer MS MVP
http://office.microsoft.com/
http://msauer.mvps.org/
news://msnews.microsoft.com
"neilvilla" wrote in message
...
When I try to print to a network printer in Publisher 2003 I get the
following error messages

"Publisher cannot continue printing because of an error. For more
information, press F1"

followed by

"Please choose another printer.

Publisher cannot find the printer \\printserver\printershare for this
publication. To select a different printer, click OK.
To return to Publisher now, click Cancel."

All my other Office XP products print fine as do non-microsoft apps. Can
anyone shed any light on this?

Ed Bennett wrote:
While waiting for decisions from his 6 university choices, Ed sees a
message from Miss Perspicacia Tick . On it is
written:
Publisher hates networks. You cannot (AFAIK)

1) Save Publisher files to a remote drive
2) Print to a remote printer

Damn smartassed teenager! ;o)



--
Facon - the artificial bacon bits you get in Pizza Hut for sprinkling
on salads.

The printers weren't added with a batch script at logon but using the global
add/per machine function. I have tried mapping printers with a logon script
using con2prt, but I can't get this to run under XP.
Coincedentally when logged on as Enterprise Admin it will print. Can it be a
GP/permissions issue when all other apps are printing fine?

"Ed Bennett" wrote:

While waiting for decisions from his 6 university choices, Ed sees a
message from Miss Perspicacia Tick . On it is
written:
Publisher hates networks. You cannot (AFAIK)

1) Save Publisher files to a remote drive
2) Print to a remote printer

FWIW, although saving to a network drive and installing to/running from a
network drive are not advisable, I've never seen anything wrong with
printing to a network printer. The only thing I've seen that could cause
problems is if the printer was installed by a batch script at logon.

--
Ed Bennett - MVP Microsoft Publisher
http://www.mvps.org/the_nerd/
Before reading this message, view the disclaimer:
http://mvps.org/the_nerd/disclaim.htm