API or W2K3 Security Issue?

[mortgagedeveloper]

Hello All!

I have a program that uses the following windows api commands and
structures for enumerating and adding printers and drivers to a remote
machine. The program's job is to copy drivers from a print server to a
remote machine and add the drivers and printer to the remote machine's
printer list.

GetPrinterDriverA
EnumPrinterDriversA
GetPrinterDriverDirectoryA
AddPrinterDriverA
EnumPrintersA
AddPrinterA
DRIVER_INFO_4

I have run into problems running this program from W2K and W2K3 boxes
to W2K3 boxes. It seems to be a rights issue, but I can't seem to
track it down.

ASSUMPTIONS
-Works perfectly on W2K and NT boxes.

-The W2K3 box I am running the program from is logged in with admin
rights to the domain.

-I CAN 'reinstall' the printers/drivers to the same box. So my program
is working nicely with 2003 api calls.

-I get "1801 - Printer name invalid" when trying to install a driver
copied from my machine.

-I get "1722 - RPC Server unavailable" when trying to install a
printer with a valid driver existing on the remote machine.

-I have turned on the following services
1-WMI Driver Extensions
2-NT LM Security Support Provider
3-RPC Locator

-The NIC card supports file and printer sharing

-The C:\WINDOWS\system32\spool\drivers directory is shared for access
to the driver files.

Thanks for any input.