Unable to print to networked printer - get access denied message

[Guest]

Hello,

I am having an issue at my office with a user who needs to be able to print
to a networked printer. I have set up thousands of network printer
connections before, and I have never run into this problem. I have searched
the net for solutions but have had no luck. In our office, the user does not
have permission to set up printers so we as admins have to do it. Here is
the story

The user requested that he be connected to a networked printer in his
office. So I went down to his machine and logged on with my admin account.

I went into Printers and Faxes and clicked on Add Printer.

Then I choose Local Printer and on the next screen, I choose Create Port and
selected StandardTCI/IP Port.

Then I entered the IP address of the networked printer and that
automatically fills in the second field with the same Port Name.

Then I click Next and have to wait for the next screen to select type of
network card in the printer, which is the HP Jet Direct.

Then I click Next. Then it comes up and asks for the mfg and type of
printer to install the drivers. I select the printer drivers to be installed
and the drivers install and I the wizard finishes and the printer is
installed.

While I am logged on as the Administrator, I AM able to print a test page
just fine. However, when I log off and the user logs on, he is unable to
print a test page and gets the following error:

Test page failed to print. Would you like to view the troubleshooter for
assistance? Access denied.

I checked the Security tab of the printer properties. I compared these
settings to another network printer that is installed (and the user CAN print
to) and they are identical.

I am totally baffled as to why this user can't print to the one printer but
can print to the other one. I set them both up the EXACT same way. I found
a post on the web that said that the C:\Windows\System32\Spool\Printers
directory may be full of 0001.spl files and it may have reached the max of
255 files. But I checked this directory on the users machine and the
directory was empty.

If anyone has any suggestions or tips that they can pass my way that may
help resolve this problem, I would be most greatful.

 

[Alan Morris [MSFT]]

does the Users group have create file access to
\windows\system32\spool\printers directory? (HINT:compare the directory
permissions of the failing machine to one which is working.)

if the system32 directory got locked down and someone included
subdirectories, then this will cause user printer failures.

If this setting looks okay and the driver you use is not included in XP, the
driver may be writing to a location to which the user does not have access.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Guest]

Alan, if the client and print server are two different machines, are you
referring to the permissions of the \windows\system32\spool\printers
directory on the client or on the print server? And what was Lawrin Walker's
outcome?

I am having the same symptoms as him on an XP client pc but the print queues
are on a W2K3 server.

does the Users group have create file access to
\windows\system32\spool\printers directory? (HINT:compare the directory
permissions of the failing machine to one which is working.)

if the system32 directory got locked down and someone included
subdirectories, then this will cause user printer failures.

If this setting looks okay and the driver you use is not included in XP, the
driver may be writing to a location to which the user does not have access.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Hello,

I am having an issue at my office with a user who needs to be able to
print
to a networked printer. I have set up thousands of network printer
connections before, and I have never run into this problem. I have
searched
the net for solutions but have had no luck. In our office, the user does
not
have permission to set up printers so we as admins have to do it. Here is
the story

The user requested that he be connected to a networked printer in his
office. So I went down to his machine and logged on with my admin
account.

I went into Printers and Faxes and clicked on Add Printer.

Then I choose Local Printer and on the next screen, I choose Create Port
and
selected StandardTCI/IP Port.

Then I entered the IP address of the networked printer and that
automatically fills in the second field with the same Port Name.

Then I click Next and have to wait for the next screen to select type of
network card in the printer, which is the HP Jet Direct.

Then I click Next. Then it comes up and asks for the mfg and type of
printer to install the drivers. I select the printer drivers to be
installed
and the drivers install and I the wizard finishes and the printer is
installed.

While I am logged on as the Administrator, I AM able to print a test page
just fine. However, when I log off and the user logs on, he is unable to
print a test page and gets the following error:

Test page failed to print. Would you like to view the troubleshooter for
assistance? Access denied.

I checked the Security tab of the printer properties. I compared these
settings to another network printer that is installed (and the user CAN
print
to) and they are identical.

I am totally baffled as to why this user can't print to the one printer
but
can print to the other one. I set them both up the EXACT same way. I
found
a post on the web that said that the C:\Windows\System32\Spool\Printers
directory may be full of 0001.spl files and it may have reached the max of
255 files. But I checked this directory on the users machine and the
directory was empty.

If anyone has any suggestions or tips that they can pass my way that may
help resolve this problem, I would be most greatful.

 

[Alan Morris [MSFT]]

Check the permissions on the server assuming the client has a true RPC
connection

How is the Standard TCP/IP port configured for the device?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Alan, if the client and print server are two different machines, are you
referring to the permissions of the \windows\system32\spool\printers
directory on the client or on the print server? And what was Lawrin
Walker's
outcome?

I am having the same symptoms as him on an XP client pc but the print
queues
are on a W2K3 server.

does the Users group have create file access to
\windows\system32\spool\printers directory? (HINT:compare the directory
permissions of the failing machine to one which is working.)

if the system32 directory got locked down and someone included
subdirectories, then this will cause user printer failures.

If this setting looks okay and the driver you use is not included in XP,
the
driver may be writing to a location to which the user does not have
access.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

Hello,

I am having an issue at my office with a user who needs to be able to
print
to a networked printer. I have set up thousands of network printer
connections before, and I have never run into this problem. I have
searched
the net for solutions but have had no luck. In our office, the user
does
not
have permission to set up printers so we as admins have to do it. Here
is
the story

The user requested that he be connected to a networked printer in his
office. So I went down to his machine and logged on with my admin
account.

I went into Printers and Faxes and clicked on Add Printer.

Then I choose Local Printer and on the next screen, I choose Create
Port
and
selected StandardTCI/IP Port.

Then I entered the IP address of the networked printer and that
automatically fills in the second field with the same Port Name.

Then I click Next and have to wait for the next screen to select type
of
network card in the printer, which is the HP Jet Direct.

Then I click Next. Then it comes up and asks for the mfg and type of
printer to install the drivers. I select the printer drivers to be
installed
and the drivers install and I the wizard finishes and the printer is
installed.

While I am logged on as the Administrator, I AM able to print a test
page
just fine. However, when I log off and the user logs on, he is unable
to
print a test page and gets the following error:

Test page failed to print. Would you like to view the troubleshooter
for
assistance? Access denied.

I checked the Security tab of the printer properties. I compared these
settings to another network printer that is installed (and the user CAN
print
to) and they are identical.

I am totally baffled as to why this user can't print to the one printer
but
can print to the other one. I set them both up the EXACT same way. I
found
a post on the web that said that the C:\Windows\System32\Spool\Printers
directory may be full of 0001.spl files and it may have reached the max
of
255 files. But I checked this directory on the users machine and the
directory was empty.

If anyone has any suggestions or tips that they can pass my way that
may
help resolve this problem, I would be most greatful.

 

[Guest]

I believe I have this figured out. Contrary to what I said in another
thread, it *IS* the 'non-admins cannot map LPTx to a printer if they have a
physical LPTx port' problem. I had been using LPT2 to avoid that problem,
but I had forgotten that the PC in question had physical LPT1, 2 and 3 ports!
If I disable the unused ports I can map printers to those ports.

I still have the problem if the print server is Win 98 and the user is a
non-admin but I am replacing the os on all W98 machines so it's no biggie.
Thanks.

Check the permissions on the server assuming the client has a true RPC
connection

How is the Standard TCP/IP port configured for the device?

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no rights.

Alan, if the client and print server are two different machines, are you
referring to the permissions of the \windows\system32\spool\printers
directory on the client or on the print server? And what was Lawrin
Walker's outcome?

I am having the same symptoms as him on an XP client pc but the print
queues are on a W2K3 server.

does the Users group have create file access to
\windows\system32\spool\printers directory? (HINT:compare the directory
permissions of the failing machine to one which is working.)

if the system32 directory got locked down and someone included
subdirectories, then this will cause user printer failures.

If this setting looks okay and the driver you use is not included in XP,
the
driver may be writing to a location to which the user does not have
access.

--
Alan Morris
Windows Printing Team
Search the Microsoft Knowledge Base here:
http://support.microsoft.com/default.aspx?scid=fh;[ln];kbhowto

This posting is provided "AS IS" with no warranties, and confers no
rights.

Hello,

I am having an issue at my office with a user who needs to be able to
print
to a networked printer. I have set up thousands of network printer
connections before, and I have never run into this problem. I have
searched
the net for solutions but have had no luck. In our office, the user
does
not
have permission to set up printers so we as admins have to do it. Here
is
the story

The user requested that he be connected to a networked printer in his
office. So I went down to his machine and logged on with my admin
account.

I went into Printers and Faxes and clicked on Add Printer.

Then I choose Local Printer and on the next screen, I choose Create
Port
and
selected StandardTCI/IP Port.

Then I entered the IP address of the networked printer and that
automatically fills in the second field with the same Port Name.

Then I click Next and have to wait for the next screen to select type
of
network card in the printer, which is the HP Jet Direct.

Then I click Next. Then it comes up and asks for the mfg and type of
printer to install the drivers. I select the printer drivers to be
installed
and the drivers install and I the wizard finishes and the printer is
installed.

While I am logged on as the Administrator, I AM able to print a test
page
just fine. However, when I log off and the user logs on, he is unable
to
print a test page and gets the following error:

Test page failed to print. Would you like to view the troubleshooter
for
assistance? Access denied.

I checked the Security tab of the printer properties. I compared these
settings to another network printer that is installed (and the user CAN
print
to) and they are identical.

I am totally baffled as to why this user can't print to the one printer
but
can print to the other one. I set them both up the EXACT same way. I
found
a post on the web that said that the C:\Windows\System32\Spool\Printers
directory may be full of 0001.spl files and it may have reached the max
of
255 files. But I checked this directory on the users machine and the
directory was empty.

If anyone has any suggestions or tips that they can pass my way that
may
help resolve this problem, I would be most greatful.