Printing to LPT1 w/DOS app

[stunpals]

When i try to capture a network printer with the net use command i am prompted with a msg "password is invalid.." but this same use can install and print from any windows app.??

 

[stunpals]

It seems the user must be a Local Administrator to the wkst... is there a permission i can set so I dont have to give them full admin rights.??

 

[inline]

Do you have a computer running Windows NT or Win2K server edition? If you do it sounds like you haven't joined the computer to the domain and or are not logged into the domain. On a basic network system joined to the domain a user can perform a net use to a printer share.

If there is no windows server software and you are only running a Workgroup network, then make sure you add the users account to the workstation you wish to connect to and that name to the share permission for that printer.

PS if you are using windows XP home edition on a Windows Domain network, i would suggest you upgrade to Pro as Home Edition cannot join a domain.

Note: When joining a machine to the domain you will be asked for an account and password to set it up. It wants an Administrator account and password not the users account who will be using that workstation.

 

[stunpals]

The printer is shared off an NT 4 server and the wkst is XP Pro. The computer has joined the domain successfully. All the permissions on the printer are the default ones with Everyone - Print.

But if they are not in the local admin group of the wkst it gives an invalid password error.

This doesnt make sense to me since the resourse in a server where they have print rights. it must be a local permission to assign the lpt1 port, because they can do the same cmd on lpt2 with success, just not lpt1 unless they have local admin rights..??
cmd i'm using is "net use lpt1 \\server\printer"

 

[beerhunter2]

Is there something in the DOS app that forces it to only user LPT1?

 

[stunpals]

No, I finally found the settings to change the LPT port used, so it seems like it should be fine now.. I'll have to get the user to test it.

Kind of strange though, there must be a policy or permission denying control of the lpt1 port.

Thanks