Error 5 Access Denied - Printing XP Pro 1

[dufresnem]

Just got new pc's with XP Pro. I need to capture LPT1 to a network printer for a specific DOS application. My kixtart scripts already have the correct capture statements and have always worked.

When I login as the user and manually try to capture LPT1 to the queue, it wants me to specify an username and password.

i.e. net use lpt1: \\Server\PrintQueue
It then prompts me to provide me with a username & password for the domain. I'm already logged in as the user.

If I'm logged in as administrator, I can capture to LPT1 and XP doesn't ask me for a username & password.

 

[bcastner]

http://support.microsoft.com/?id=313644

Prior to the Net Use lpt1: statement, you need to either:

. Use Device manager to disable the physical LPT1 port on the computer; or,

. Use devcon.exe, (a command line Device Manager) to make the entry:

devcon disable *PNP0401

(Place devcon.exe in the folder %windir%\system32

Direct download of Devcon.exe:

http://support.microsoft.com/kb/311272/EN-US/

 

[bcastner]

I should note that this approach:
. Use devcon.exe, (a command line Device Manager) to make the entry:
devcon disable *PNP0401

Would require that it be in the logon script for each startup, whereas a disable through Device Manager would be persistent.

A third possibility: you might have BIOS entry to disable the native parallel port.

 

[dufresnem]

Thanks, I've reviewed the article. Its pretty bad when Micrsoft feels a printer port is a security risk????

Thanks again.

 

[bcastner]

It is not that the printer port, per se, is a security risk. It is in the general sense of the security model that allowing limited users permissions to make changes to the global OS settings, that ends up restricking this particular user right.

The fact that it is a printer port effected is irrelevant; the fact that the permissions could allow a limited user elevation to Administrator is a different fish altogether.

It is admitedly an obscure issue, but the "fixes" I suggested above should work fine.

I too would like more granular controls with XP. But this unexpected consequence with the printer port is well documented, and the workaround non-offensive.

Best wishes,
Bill Castner

 

[dufresnem]

The fix does work and everything works fine now.

That's my point though, the security settings in Windows is so restrictive anymore that the items they are trying to lock down are infact causing so many problems for administrators. In order for some items to work properly, you need the admin right, or spend hours upon hours trying to find a solution.

XP has a nice look to it, but Win2K, is much better to manage and assign rights. Microsoft keeps changing the look and location of everything and they cause there on security holes. They tighten down the desktop and leave something critical wide open.