The problem here is most likely that the names of the NT4 drivers don't
match those of the XP drivers. Quite often there is a tiny difference, such
as different capitalization or two spaces instead of one in the model name.
Two ways to fix:
1. see whether the manufacturer has a set of drivers with exactly the same
name
2. change the model name in the XP driver INF to match the one of the NT4
driver. This has a number of drawbacks: editing the INF invalidates any
signature that the driver may have, and typically, drivers of different
names don't understand the settings of the other drivers (hence actually the
name change in many cases) so it will start out with defaults (or crash...
depends on the driver) which means that if you have non-default things (such
as a duplexer), it may not be available from the XP machine. If that is
important, you can set the XP machines up with local queues printing to a
"local" port (that you have to create) named
\\YourNT4ServerName\YourPrinterShare and set the settings individually on
each of the clients. Not great, I know.
--
This information is provided AS-IS and confers no rights.
Heather said:
I have a number of XP clients and an NT4 domain, a number of NT4 BDCs are
acting as print servers. I try to use the XP clients to update the print
server with XP drivers for the printers by browsing to the Printers and
Faxes folder on the server from the XP client and then using Sharing and
Additional Drivers. With each of the three drivers I need to copy, I get an
error saying that Windows cannot find the correct driver and to contact the
systems administrator (me). How do I get the drivers copied over??
