S
shannon
Somebody please HELP!
Suddenly this morning a handful of users cannot print
using their Office applications (IE, Word, Excel,
PowerPoint, Outlook) but they CAN print using wordpad or
adobe reader or other such apps.
The printers are connected to the network, and then there
is a Windows 2000 Server with a bunch of Standard TCP
Ports, each pointing to one of the printers.
The clients then connect to the printers via the server.
For example: we would run the Add Printer Wizard and
either browse for the printer (in which case the printer
shows up as shared from the server) or simply type
\\servername\printersharename
If we go the client workstation and create the Standard
TCP Port directly on that workstation, then add a "local"
printer using that port and install the drivers directly
on the workstation the client can print without any
problems.
Also - if we do this at the client workstation's command
prompt:
--net use lpt1: \\servername\printersharename
--dir > lpt1
The job will print.
It's just when the printer is added via the server that
the problem appears - the user can print from wordPAD, but
when they open up Word and submit the job (via file|print
or via the button on the toolbar - doesn't matter) it
hangs halfway through spooling and never goes anywhere.
The job just sits in the queue when viewed from the
server - status is "spooling"
If anyone can help it would be great - tomorrow is
supposed to be my day off! hehe
TIA,
Shannon
Suddenly this morning a handful of users cannot print
using their Office applications (IE, Word, Excel,
PowerPoint, Outlook) but they CAN print using wordpad or
adobe reader or other such apps.
The printers are connected to the network, and then there
is a Windows 2000 Server with a bunch of Standard TCP
Ports, each pointing to one of the printers.
The clients then connect to the printers via the server.
For example: we would run the Add Printer Wizard and
either browse for the printer (in which case the printer
shows up as shared from the server) or simply type
\\servername\printersharename
If we go the client workstation and create the Standard
TCP Port directly on that workstation, then add a "local"
printer using that port and install the drivers directly
on the workstation the client can print without any
problems.
Also - if we do this at the client workstation's command
prompt:
--net use lpt1: \\servername\printersharename
--dir > lpt1
The job will print.
It's just when the printer is added via the server that
the problem appears - the user can print from wordPAD, but
when they open up Word and submit the job (via file|print
or via the button on the toolbar - doesn't matter) it
hangs halfway through spooling and never goes anywhere.
The job just sits in the queue when viewed from the
server - status is "spooling"
If anyone can help it would be great - tomorrow is
supposed to be my day off! hehe
TIA,
Shannon