printer looks fine, just doesn't print

[teash]

Greetings, I am running SBS 2003. I have 5 users and a printer. We only have 5 CAL's so this may be a problem. Does Micro$oft consider a printer a person?

The printer was part of the old domain before we updates to SBS 2003. I downloaded the new drivers for it, I configured it to work on an TCP/IP port. I am able to ping the Gestetner 3235 printer and can use a utlity program to get into its brains to reconfigure it.

I have shared the printer and all the computers can add it to their list of printers.

However if you send something to it to print, they get an error. If I try to send a file to the printer from the server it looks like it was accepted and processed...

after a 10 second walk to the printer... no document. no error on the server.

I am using the administrator account, so I don't think it has anything to do with permisssions... but then again.. what do I know. I posting for help!!!

Thanks guys. (and girls)

 

[WANguy2k]

I would start again: Delete the printer from the server completely, delete the TCP/IP port you created, then install it again. (And give the printer a new name.) Make sure you can print from the server to the printer first, then share it. Once that's done delete the old printer from the clients and then add the new printer.

The licensing shouldn't be an issue, printer devices don't login so they don't take a license.

 

[teash]

After uninstalling it, and reinstalling it, it just gets stuck in the printer queue with an error.

I have tried both drivers, ones digitally signed microsoft, and the gestetner version.

Is there a printer log that explains why it doesn't want to print for daddy?

 

[TopKatz]

Have you tryed PCL 6 drivers? I had some issues using PS and PCL 5 with a 2k3 server.

 

[WANguy2k]

So now the job is showing in the printer queue on the server and can't get to the printer? I'm assuming the printer is connected to the network and you can ping its address from the server? Do you have the correct default gateway and subnet configured on the printer?

To turn on print logging, open the Printers and Faxes icon on the server. The choose File, Print Server Properties, Advanced. You can turn on logging for all print jobs, successful or not.

If the server can ping the printer and you have the printer's network settings in properly, the only thing left that I can see is to make sure the printer isn't broken: hook it up to a PC and test it.

 

[WANguy2k]

By the way, you said "After uninstalling it, and reinstalling it, it just gets stuck in the printer queue with an error."

What's the error?

 

[teash]

I am beginning to think it's a driver issue.
I was able to print to the newly added Gestetner 2212 with out any issues using a similar setup.

However, trying to install the other 3235 using PCL 6 drivers is a no go.

The only error I get is "Error: Document failed to print".

Thanks for the posts.

 

[teash]

I tried the 3235s PCL 6 drivers and it accepts the document with out an error, except I don't get anything printed.

The 3235 driver (minus the "s") gives me the "document failed to print error".

 

[WANguy2k]

Did you turn on the print logging and try it again? What does the log show? Also, in the properties on the printer icon, try turning off bidirectional support in the "ports" tab.

 

[onechuck]

What type of printer is it? If it is an HP laser jet printer, you may try the HP Web Jet Admin to administer the printer. In addition, what are the security rights on that particular printer? In our case, those users have the Print and Manage Documents rights checked under the security tab. In addition, have you checked the event log to see if it generates any type of errors that relates to this printing issue?

 

[teash]

Event ID: 9
Printer Gestetner 3235s PCL 6 was set.


Event ID: 36
PrintQueue CN=RVM-Gestetner 3235s PCL 6 was successfully created in container LDAP://rvm.RVMarketingInc.local/CN=RVM,OU=Domain Controllers,DC=RVMarketingInc,DC=local.

I added the printer and sent it the standard test page.
Then the you get the window's ballon in the bottom right saying "Error-Printing". I am logged on as the Admin, I don't think you get much more permission than this. But I don't have all them fancy dancy MS certifications yet.

 

[WANguy2k]

If that's the ONLY error message you're getting in the logs after turning all logging on in the print server settings, I would restart the spooler service and try again.

Did you take all the steps above? Can you ping the address? Turn off bidirectional support? Try using a PCL5 driver?

If that doesn't work why don't you hook up the printer directly to the server or a PC and make sure it can print.

 

[teash]

I got it guys. Went to gestetners website and read through the crapload knowledge base that was rather useful when you decipher it.

Changed the TCP/IP port on the server to 10001, and switched from RAW to LPR for the older printer.

Worked like a charm!