topic Re: Remote downlevel document in Networking

Remote downlevel document

Donald Mackenzie_1 — Sun, 30 Nov 2003 14:07:36 GMT

A PC running Win2k will regularly send to any available printer a document described as "Remote downlevel document".

This causes the printer to continually print pages with only one line of symbols on the top of each page.

Once cancelled the document will constantly re-appear as if a random timer in the Win2k PC is programmed to regularly print this document.

Re: Remote downlevel document

Michael Schulte zur Sur — Sun, 30 Nov 2003 17:03:04 GMT

Hi,

is the printer shared? Remote downlevel document indicates a printing over the network and if the printer driver on the other side is faulty or the format not supported, that might be the cause for the symbols.

greetings,

Michael

Re: Remote downlevel document

Norman_21 — Sun, 30 Nov 2003 21:22:26 GMT

Hi,

Would you mind to be more specific what is required exactly. The symbols could mean either a bad driver or bad cable..
In regard of the document will constantly re-appear, that means one of the applications is configured to start printing on a certain time. Check your startup programs or the Task Scheduler!! or remove the print and file share service from the My network Places properties..

Good luck and please keep us updated!

Re: Remote downlevel document

Jon Finley — Sun, 30 Nov 2003 23:08:44 GMT

This can also be caused by a virus on one of the systems within your network.

http://us.mcafee.com/virusInfo/default.asp?cid=9043

http://securityresponse.symantec.com/avcenter/vinfodb.html#threat_list

http://support.microsoft.com/default.aspx?scid=kb;en-us;312015&Product=win2000

Jon

Re: Remote downlevel document

Michele Berg — Mon, 02 Feb 2004 14:03:39 GMT

Which virus might cause this to happen?

Re: Remote downlevel document

Scott Wood_1 — Thu, 04 Mar 2004 16:14:06 GMT

FunLove has caused this problem for us.

Re: Remote downlevel document

Peeyush — Wed, 24 Mar 2004 13:34:27 GMT

http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/Q162/4/47.ASP&NoWebContent=1&NoWebContent=1
http://support.microsoft.com/default.aspx?scid=kb;en-us;137065

Re: Remote downlevel document

Brad Cozine — Sun, 04 Apr 2004 11:59:14 GMT

I just had the issue with W32.Gaobot.SA in file:

C:\WINDOWS\SYSTEM32\SPOOL\PRINTERS\00003.SPL

Re: Remote downlevel document

jason kuroshima — Mon, 18 Oct 2004 20:47:16 GMT

me too only i'm running XP

Re: Remote downlevel document

Ryan C_1 — Tue, 16 Nov 2004 13:01:45 GMT

Good stuff folks,

I was having the same issue, I just ran McAfee and found bomsvc32.exe under my C:\Documents and Settings\All Users\Documents
and it was detected as W32/Gaobot.worm.gen.g
Thank you all, for the forum :)

Thank You,
Ryan

Re: Remote downlevel document

Steve Caldwell_1 — Tue, 04 Jan 2005 15:14:05 GMT

I've read a thousand posts all across the web trying to figure this one
out. In Win 2000, NT, and 2003, network printers spit out garbled pages
until the printer is out of paper. We are losing hundreds of sheets of
paper a day to this nuisance. The object appears in the spool as
"Remote Downlevel Document" and cannot be deleted without a long delay.
The only way to stop it is to pull the plug on the printer. Although I
have not completely solved the problem, I have a point of view which I
have not yet come across.

It is important to note that this will only work if the user name on
the RDD is "Guest" (This is the only username I've heard of that causes
the problem.)

If you are on the computer that has the RDD in the printer queue, you
will need to change some security settings for the printer. Go into the
printer's properties. Click the security tab (If this isnt visible, log
in as admin.) Click add, type in "Guest" for the user name" Now, deny
the guest of all printing privledges.

This is simply a work around that is only useful if you don't utilize
the guest user name on your domain.

-- I use WIN2003 Standard as a DC and all of my clients are win XP pro.

--This procedure worked for me for a great deal of time, but the
problem persists here and there.

****--For a network printer...If you cant figure out which pc is
causing the problem...try removing the trays or paper from your printer
and then let it attempt to print the garbage. Then go to every terminal
and see which one is acting up. Then try and change the security
settings.