Remote Downlevel Document

[Guest]

I have a Windows 2000 Server SP4, with diferents printers shared. The clients
are Windows XP. Aleatory i receive the printing job "Remote Downlevel
Document" and i can not know how many pages are printed and the job's name.

I was searching information in internet about that. what i found speak about
viruses (i dont have it) and about to conect to printers "using net use" that
is not the case. The software used by the client are not DOS.

The printers are all diferents and with diferents models. The proble appear
in many of them and with diferent users. I can not found a pattern.

How can i solve this problem???

I will be very helpful with your help.

Best Regards.
Rosana

 

[Alan Morris [MSFT]]

when it's a virus, the client machine is the one that copies exe files to
the shared printers. You will have many pages printed with one to ten
characters at the top of the page. It waste a bunch of paper and you have
to track the client machine in order to remove the virus.

You can easily create the downlevel job by selecting Print to File
(usually in the application print dialog) then enter a name for the file
when prompted. Now copy this file to the shared printer from command
line.
copy printtofilename \\printserver\sharedprinter


Since these documents are rendered on the client rather than the server and
printed in raw format, the server does not have the page count information,
it just acts as a bridge to the printer.


Printing to file is fairly common when one knows the model type of the
office printer and sets up a printer at home to format the data. Then bring
the file in to actually get the information on page.


--
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, thank you very much for your answer.

Is true,the file are printed in raw format. The jobs are correctly printed
without any mistake. I have installed a software that is a printer logger and
show even the size of the printed document... With Windows 2003 i have no
problem, works perfect.

This is not a virus, I check very carefully and there is nothing in the
shared printer folder, and the printer really works perfect.

Kind Regards
Rosana.

when it's a virus, the client machine is the one that copies exe files to
the shared printers. You will have many pages printed with one to ten
characters at the top of the page. It waste a bunch of paper and you have
to track the client machine in order to remove the virus.

You can easily create the downlevel job by selecting Print to File
(usually in the application print dialog) then enter a name for the file
when prompted. Now copy this file to the shared printer from command
line.
copy printtofilename \\printserver\sharedprinter


Since these documents are rendered on the client rather than the server and
printed in raw format, the server does not have the page count information,
it just acts as a bridge to the printer.


Printing to file is fairly common when one knows the model type of the
office printer and sets up a printer at home to format the data. Then bring
the file in to actually get the information on page.


--
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.

I have a Windows 2000 Server SP4, with diferents printers shared. The
clients
are Windows XP. Aleatory i receive the printing job "Remote Downlevel
Document" and i can not know how many pages are printed and the job's
name.

I was searching information in internet about that. what i found speak
about
viruses (i dont have it) and about to conect to printers "using net use"
that
is not the case. The software used by the client are not DOS.

The printers are all diferents and with diferents models. The proble
appear
in many of them and with diferent users. I can not found a pattern.

How can i solve this problem???

I will be very helpful with your help.

Best Regards.
Rosana

 

[Guest]

Check the print queues on the workstations. These are probably Local Queues
using a Local Port t the Print Server. If this is the case the Job will show
up at the server as Remote Downlevel Document. This can be handled by using a
Network Queue to the Share on the server rather than a Local Queue, the
Document title will remain in tact. If you have to use a Local Queue (Because
it carries across Local Profiles where a Network queue does not) then enable
Print Services for Unix on the Server and on the Workstations and use a Local
Queue using an LPR port, rather than a Local Port. The Document title will
not be repolaced with Remote Downlevel Document when using an LPR port AND
the document will spool a lot faster.

Alan, thank you very much for your answer.

Is true,the file are printed in raw format. The jobs are correctly printed
without any mistake. I have installed a software that is a printer logger and
show even the size of the printed document... With Windows 2003 i have no
problem, works perfect.

This is not a virus, I check very carefully and there is nothing in the
shared printer folder, and the printer really works perfect.

Kind Regards
Rosana.

when it's a virus, the client machine is the one that copies exe files to
the shared printers. You will have many pages printed with one to ten
characters at the top of the page. It waste a bunch of paper and you have
to track the client machine in order to remove the virus.

You can easily create the downlevel job by selecting Print to File
(usually in the application print dialog) then enter a name for the file
when prompted. Now copy this file to the shared printer from command
line.
copy printtofilename \\printserver\sharedprinter


Since these documents are rendered on the client rather than the server and
printed in raw format, the server does not have the page count information,
it just acts as a bridge to the printer.


Printing to file is fairly common when one knows the model type of the
office printer and sets up a printer at home to format the data. Then bring
the file in to actually get the information on page.


--
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.

I have a Windows 2000 Server SP4, with diferents printers shared. The
clients
are Windows XP. Aleatory i receive the printing job "Remote Downlevel
Document" and i can not know how many pages are printed and the job's
name.

I was searching information in internet about that. what i found speak
about
viruses (i dont have it) and about to conect to printers "using net use"
that
is not the case. The software used by the client are not DOS.

The printers are all diferents and with diferents models. The proble
appear
in many of them and with diferent users. I can not found a pattern.

How can i solve this problem???

I will be very helpful with your help.

Best Regards.
Rosana

 

[Guest]

I was proving your solution but didn't work. Unfortunatly, I still have DOS
systems that before they print, they execute batch files and connect the
printer using the command "net use". I can see the document while is printing
but continue showing the same information: Remote Downlevel Document, 0 pages.
I really dont know what else to prove!!!

Check the print queues on the workstations. These are probably Local Queues
using a Local Port t the Print Server. If this is the case the Job will show
up at the server as Remote Downlevel Document. This can be handled by using a
Network Queue to the Share on the server rather than a Local Queue, the
Document title will remain in tact. If you have to use a Local Queue (Because
it carries across Local Profiles where a Network queue does not) then enable
Print Services for Unix on the Server and on the Workstations and use a Local
Queue using an LPR port, rather than a Local Port. The Document title will
not be repolaced with Remote Downlevel Document when using an LPR port AND
the document will spool a lot faster.

Alan, thank you very much for your answer.

Is true,the file are printed in raw format. The jobs are correctly printed
without any mistake. I have installed a software that is a printer logger and
show even the size of the printed document... With Windows 2003 i have no
problem, works perfect.

This is not a virus, I check very carefully and there is nothing in the
shared printer folder, and the printer really works perfect.

Kind Regards
Rosana.

when it's a virus, the client machine is the one that copies exe files to
the shared printers. You will have many pages printed with one to ten
characters at the top of the page. It waste a bunch of paper and you have
to track the client machine in order to remove the virus.

You can easily create the downlevel job by selecting Print to File
(usually in the application print dialog) then enter a name for the file
when prompted. Now copy this file to the shared printer from command
line.
copy printtofilename \\printserver\sharedprinter


Since these documents are rendered on the client rather than the server and
printed in raw format, the server does not have the page count information,
it just acts as a bridge to the printer.


Printing to file is fairly common when one knows the model type of the
office printer and sets up a printer at home to format the data. Then bring
the file in to actually get the information on page.


--
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.

I have a Windows 2000 Server SP4, with diferents printers shared. The
clients
are Windows XP. Aleatory i receive the printing job "Remote Downlevel
Document" and i can not know how many pages are printed and the job's
name.

I was searching information in internet about that. what i found speak
about
viruses (i dont have it) and about to conect to printers "using net use"
that
is not the case. The software used by the client are not DOS.

The printers are all diferents and with diferents models. The proble
appear
in many of them and with diferent users. I can not found a pattern.

How can i solve this problem???

I will be very helpful with your help.

Best Regards.
Rosana