General discussion

Locked

Remote Downlevel Document

By svybiral ·
Hello all. I have two NT 4.0 servers, 1-PDC and the 2-BDC. All my users login the PDC and use the BDC for file/print resources. I have 98% of my print queues setup on the BDC. I have the printers setup so the jobs are retained in the queue so I can periodically view what my users are printing. I can view the jobs from the print queues on the BDC but not on the PDC. The jobs are retained in the queues on the PDC but the document names are all listed as Remote Downlevel Documents. I also have frequent problems with this queue where the jobs will just stop and I have to restart them. How can I get the print jobs to list the real document names instead of this Remote Downlevel Document name?

The printers have JetAdmin NIC's and theyhave static IP's. And the users are running DHCP.

Any suggestions would be greatly appreciated.

Sue

This conversation is currently closed to new comments.

5 total posts (Page 1 of 1)  
| Thread display: Collapse - | Expand +

All Comments

Collapse -

Remote Downlevel Document

by Joseph Moore In reply to Remote Downlevel Document

This is not a solution for your problem; is is more of an alternate way to do this.
The System Log in Event Viewer on your BDC (where the print queues are) contains every print request sent to its printers.
Here is an example of what it is recording:

Event Type: Information
Event Source: Print
Event Category: None
Event I 10
Date: 3/1/2002
Time: 3:20:31 PM
User: MYDOMAIN\JOE
Computer: PRINTSERVERNAME
Description:
Document 140, Microsoft Word - ldnchklst.doc owned by JOE was printed on SHAREDPRINTERNAME via port PORTNAME. Size in bytes: 378286; pages printed: 3


So, you get the file name, the user, time, date, etc.
You could also build a Filter on the System Log to only show Event ID 10, which is the normal Print message.
You could then export the Event 10s if you want to keep an offline log.

hope this helps

Collapse -

Remote Downlevel Document

by svybiral In reply to Remote Downlevel Document

The question was auto-closed by TechRepublic

Collapse -

Remote Downlevel Document

by curlergirl In reply to Remote Downlevel Document

I am not completely sure what the technical cause of this is, but it happens when a workstation is sending documents to the printer using a captured LPT port rather than a Windows networking shared resource. For some reason when the document is sent in this manner, the NT print server doesn't get whatever information it needs to identify the document in any more detail than "remote downlevel document." This is common with workstations that are running DOS programs under Windows, where you have to map the shared printer to a local LPT port in order for the program to be able to send files to the printer. Usually there's nothing you can do about this if that is the cause. However, if your users are printing from Windows programs, you might want to try making sure that they are not in fact sending their print jobs to an LPT port instead of directly to the shared resource on the print server. I'm not aware of any other cause of this behavior. Also, be sure they are using the correctprinter drivers, and the latest versions, just as a precaution. Hope this helps!

Collapse -

Remote Downlevel Document

by svybiral In reply to Remote Downlevel Document

The question was auto-closed by TechRepublic

Collapse -

Remote Downlevel Document

by svybiral In reply to Remote Downlevel Document

This question was auto closed due to inactivity

Back to Windows Forum
5 total posts (Page 1 of 1)  

Related Discussions

Related Forums