Topic Options
#30049 - 03/25/09 10:53 AM LPR Windows 2003 R2 Standard QUE configuration
GRM Offline
Junior Member

Registered: 03/23/09
Posts: 3
I have a PlanetPress Suite 6 server configured with the LPD service running, the Suite is installed on a Windows 2003 R2 Enterprise machine.

From my Windows 2003 R2 Standard machine, I can go to the Command Prompt and using the LPR command I can send files to the LPD que on the server machine and everything works fine.

If I configure a Windows Que on the Windows 2003 R2 Standard machine as an LPR que with the same ip address and que name, the que produces an error and the LDP que never get the file. I can see that the connection between the two machines is working.

Is there some kind of special configuration required to print to PlanetPress LPD ques from Windows 2003 R2 standard LPR ques?

Top
#30050 - 03/26/09 09:38 AM Re: LPR Windows 2003 R2 Standard QUE configuration
Raphael Lalonde Lefebvre Offline
OL Expert

Registered: 10/14/05
Posts: 4953
Loc: Objectif Lune Montreal
GRM,

The Windows version is probably not the problem.

To make it work, I've created a new port that points to 127.0.0.1, the local IP address(use your remote machine's IP if you're sending to an external source). I set it up to use LPR, to point to the queue defined in Watch. However, the key to make it work was to enable "LPR Byte Counting". Without it, I got errors, but once checked, it worked just fine.

Try it out, and see if that works for you!

Regards,
Rapha

Top
#30051 - 03/26/09 01:31 PM Re: LPR Windows 2003 R2 Standard QUE configuration
GRM Offline
Junior Member

Registered: 03/23/09
Posts: 3
Okay, I tried that, and the message is a little different, it now says 'Printer Busy or error'.

Also, the byte count for the number of bytes send goes up to 128KB and then stops.

Is there a log file for LPD that shows connections and such.

Top
#30052 - 03/26/09 03:01 PM Re: LPR Windows 2003 R2 Standard QUE configuration
GRM Offline
Junior Member

Registered: 03/23/09
Posts: 3
It's okay, I found the directories for the logs and have corrected the access manager.

Top