Y
Yoshi
Hi all !
First of all, I like to wish everybody a happy new year, and not so many
troubles with computers. Unfortunately, I know this is quite impossible.
Let's kick of the year, with a network printing problem. Everybody knows the
principles : A printer is installed on a server or a workstation, and is
shared so other users can also use this printer. Quite simple.
But, this shouldn't be a message to the newsgroup, if it was working fine
all the time ! The problem is not the connection from the server to the
printing device, but connecting from a XP-workstation through the server
(2000 or even 2003) to the device.
There are some ways to do it. Following the 'Add Printer Wizard' is maybe
the most known and used. Select a network printer, and almost everything is
going automated.
Another way, is browsing the network for shared printers, and if you find
the right one, right-click and select the option 'Connect'. The result
should be the same, I guess.
Whatever I try, it isn't always correct. Sometimes it works fine, other
times even a test print can not be send to the printer. However, most of the
time it works with Microsoft applications like Word and Excel; even if it
was impossible to make a test print from the driver. But using applications
like Acrobat Reader, it won't work. Nothing happen, even not an error
message.
There is a way to let it work properly. Installing the desired printer
locally on the workstation, and finally change the port-settings to :
\\servername\printername. So, the driver is installed locally on the
workstation, jobs are spooled locally and finally send through the server
to the printing device.
This works fine, but not the most recommended way to use in great networks.
An administrator has to do it. A simple user has not the rights to do this.
I have seen this several times, independent the printer type used. All
drivers are digitally signed by Microsoft and Kernel-mode drivers, so that
is not the problem, I guess.
First of all, I like to wish everybody a happy new year, and not so many
troubles with computers. Unfortunately, I know this is quite impossible.
Let's kick of the year, with a network printing problem. Everybody knows the
principles : A printer is installed on a server or a workstation, and is
shared so other users can also use this printer. Quite simple.
But, this shouldn't be a message to the newsgroup, if it was working fine
all the time ! The problem is not the connection from the server to the
printing device, but connecting from a XP-workstation through the server
(2000 or even 2003) to the device.
There are some ways to do it. Following the 'Add Printer Wizard' is maybe
the most known and used. Select a network printer, and almost everything is
going automated.
Another way, is browsing the network for shared printers, and if you find
the right one, right-click and select the option 'Connect'. The result
should be the same, I guess.
Whatever I try, it isn't always correct. Sometimes it works fine, other
times even a test print can not be send to the printer. However, most of the
time it works with Microsoft applications like Word and Excel; even if it
was impossible to make a test print from the driver. But using applications
like Acrobat Reader, it won't work. Nothing happen, even not an error
message.
There is a way to let it work properly. Installing the desired printer
locally on the workstation, and finally change the port-settings to :
\\servername\printername. So, the driver is installed locally on the
workstation, jobs are spooled locally and finally send through the server
to the printing device.
This works fine, but not the most recommended way to use in great networks.
An administrator has to do it. A simple user has not the rights to do this.
I have seen this several times, independent the printer type used. All
drivers are digitally signed by Microsoft and Kernel-mode drivers, so that
is not the problem, I guess.