Client configuration utility.

Is the logging client service running? The window title bar shows the logging service status. (Note - under Vista you need to run the client configuration utility as administrator if you are using UAC for the server status to be displayed correctly).

If the service is shown as not installed / not running you can reinstall the service by :

Open the command prompt.
Enter CD \program files\prnlogclient <return>
Enter plsvc /iss <return>
Restart the client configuration utility.

Is the printer message field recording the number of jobs logged? (You may need to refresh - tools / refresh - to get an up to date count.)

If the count is not incrementing with each job printed then either

1) The 'Use advanced printing features' is checked off in the advanced tab of the printer driver properties.

2) The account used for running the client logging service (Normally the system account) is not a printer administrator. (This is extremely unlikely).

Are the logs being recorded but remaining in the logs queue?

The logs queue holds all recorded logs, from here they are sent to the logging server. If there is a problem with the logging server (eg: crashed), the logs will remain here until the logging server is operational again. This is a safely feature to prevent the loss of print logs.

There are four possible reasons for logs accumulating here when they should not.

1) A firewall (or virus scanner) on the logging server is blocking incoming log packets.

Try disabling the firewall on the logging server and see if the logs go through.
If this works open ports 2326 - 2330 and 2376 - 2380 on the logging server firewall.

Why so many ports? Printer Squirrel uses a dynamic method of allocation ports, so that if a port is in use by another program, it simply uses the next available rather than generate an error or simply not work.

2) A firewall (or virus scanner) on the logging client may be blocking outgoing packets.

Some of the latest firewalls block outgoing packets for virus propagation protection reasons. Try disabling the firewall on the logging client and see if the logs go through. If so open ports (outbound) 2326 - 2330 and 2376 - 2380 on the logging client firewall.

3) The virtual printer no longer exists on the logging server.

Check on the logging server (Printer Squirrel) that a virtual printer exists with the same NETID as the NETID of the logged printer in the client configuration utility.

4) The logging server is offline or crashed.

'nuff said.