Windows 2000 security issue

I have a windows 2000 file server and a windows NT 4 PDC.
On a windows 2000 client i capture printer ports lpt2 and
3 to networked printers on the pdc, when i print using a
dos program nothing comes out of the printer. I can print
in windows fine, i do a copy bla.txt > lpt2 and it will
print fine. The wierd thing is that i logged on the
client using the administrator account from the pdc (nt4
server) and ran the program and it printed fine. I
thought maybe its a seurity problem so i put the user in
the domain admin group, and still i cant print. I have a
feeling its something to do with security but i dont know
what to do. Any suggestions..

Hmmm, i'm not the authority on this, however it seems that all you should have to do to set up the printer for W2000/NT/9x is to click the sharing tab in the printer properties, choose additinal drivers then select whatever client type you need to support. Whenever the client connects for the first time W2000 should set up the printer on the client. Not the same for earlier versions of Windows or even a MSDOS OS, where you have to install a 16bit printer driver on the client system and redirect a local port to be network share. You can even set up W2000 to support printing from *nix or IPP clients.
maybe someone else can see another possible on your question. Good luck!

is the user and or the domain admins group in the permissions list for the printer share?

-scoob8000

I think that this is a permissions problem. On my home network I have a Windows 2000 machine set up as the main file server. If I log into another machine on the network using the same login id and password as the one that I have logged into the file server with then the other machine has pretty much unlimited access to the file server, including printer ports and shared drives. If I log into the other machine with a different login and password then I am stuck by the permissions and every other resource requests a password for access.

exactally what i was getting at.. :)

see who all is in the permissions for the share.. make sure whatever group your user is in, has permissions to that share..

-scoob8000