RE: Printing from Win9x clients stops

Tech-Archive recommends: Fix windows errors by optimizing your registry

Hello Dave,

Thank you for posting back! I'm glad to hear that things are working
correctly for you now.

I appreciate your sharing the RESOLUTION and EXPLANATION of the issue.
Again thanks for your time and patience in this matter.

Please do not hesitate to post in this newsgroup if you need any assistance
in the future. I look forward to working with you again.

Best regards,

Nathan Liu (MSFT)
Microsoft CSS Online Newsgroup Support
Get Secure! - www.microsoft.com/security
=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.

--------------------
>Thread-Topic: Printing from Win9x clients stops
>thread-index: AcVw78vS8ygBgLyNRNKrafm4PrJ8MA==
>X-WBNR-Posting-Host: 83.104.120.90
>From: "=?Utf-8?B?RGF2ZVI=?=" <DaveR@xxxxxxxxxxxxxxxxxxxxxxxxx>
>References: <451C05BA-43DA-436F-A3CC-1A7485336799@xxxxxxxxxxxxx>
<gAkUl#PZFHA.2184@xxxxxxxxxxxxxxxxxxxxx>
<CEE9A710-4801-4C3D-B75B-025ECC2B9FD4@xxxxxxxxxxxxx>
<$nLk1T3ZFHA.3336@xxxxxxxxxxxxxxxxxxxxx>
<EA5F1149-3AC8-43C6-A5AA-5B5DE2D1124F@xxxxxxxxxxxxx>
<LO#CLdDaFHA.3052@xxxxxxxxxxxxxxxxxxxxx>
<9C0A5B91-AF2C-493B-BBDA-A8D6BAD78C5D@xxxxxxxxxxxxx>
<G9HaOAwaFHA.2476@xxxxxxxxxxxxxxxxxxxxx>
<B494F89E-1634-4AEC-A502-ACAB33567582@xxxxxxxxxxxxx>
<l1ySCI7bFHA.3928@xxxxxxxxxxxxxxxxxxxxx>
>Subject: RE: Printing from Win9x clients stops
>Date: Tue, 14 Jun 2005 07:46:06 -0700
>Lines: 53
>Message-ID: <3E5322F4-45B3-40D7-8DF7-9383E6C4273C@xxxxxxxxxxxxx>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 8bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.windows.server.sbs
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.2.250
>Path: TK2MSFTNGXA01.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: TK2MSFTNGXA01.phx.gbl microsoft.public.windows.server.sbs:127226
>X-Tomcat-NG: microsoft.public.windows.server.sbs
>
>Hello Nathan,
>The matter is now entirely resolved.
>We are indebted to Lynn Xu (CS&S) who has been extremely quick and
efficient.
>I attach parts of two emails which explain the situation:
>
> PROBLEM
>========
>Users were unable to send print jobs to shared printers hosted by SBS2003
>from Windows ME client computers.
>
>RESOLUTION and EXPLANATION:
>=============================
>When a Windows ME computer prints to Windows 2003 server, it must render
the
>job locally at first into RAW format which printer device can recognize.
>After rending, it sends the rendered job to Windows 2003 server and the
file
>is placed at "C:\WINDOWS\system32\spool\PRINTERS". As soon as the sending
>completes, Windows 2003 server involves printer language monitor to
forward
>job to printer device. Unlike printing from Windows XP, the job lists in
>printer queue both in Windows ME client and Windows 2003 server. More
>importantly, Windows ME monitors the sending procedure. Immediately after
the
>sending completes, Windows ME asks server to delete print job. However,
>because Windows ME client doesnâ??t have sufficient permission to remove
the
>file, Windows 2003 leave the file in C:\Windows\System32\Spool\Printers.
The
>amount of temp files increased daily and till one day when Windows 2003
>server can no longer accept more temp file. Therefore the printing failed.
>
>Because Windows ME uses Anonymous Logon account to authenticate, we gave
>full control permission to this account and deleted the existing temp
file,
>which resolved the problem.
>
>and second:
>
>I missed one point in my summary. In this case, it seems that the
antivirus
>software could also be responsible for the corrupted temporary files. I
>configured E-Trust to exclude the printer spool folder. Antivirus software
>may interfere with those important system temporary files. For example, we
>also recommend users exclude the folders of Exchange from the real-time
>protection of Antivirus software:
>
>328841 Exchange and antivirus software
>
>http://support.microsoft.com/?id=328841
>
>There must be others in the community using a similar setup, so I hope
that
>this will be of assistance. My customer sends a large number of very
large
>and complex plots to two HP750 DesignJets, so this may have exacerbated
the
>problem here.
>Very many thanks for all your time and suggestions.
>Best regards,
>Dave
>
>All previous snipped because "your post is too long......"!
>
>

.

Relevant Pages

  • SecurityFocus Microsoft Newsletter #154
    ... MICROSOFT VULNERABILITY SUMMARY ... ISS RealSecure Server Sensor SSL Denial Of Service Vulnerabi... ... Roger Wilco Remote Server Side Buffer Overrun Vulnerability ... available for Microsoft Windows operating systems. ...
    (Focus-Microsoft)
  • SecurityFocus Microsoft Newsletter #49
    ... Subject: SecurityFocus Microsoft Newsletter #49 ... Microsoft Windows NNTP Denial of Service Vulnerability ... Microsoft IIS SSI Buffer Overrun Privelege Elevation Vulnerability ... Microsoft ISA Server H.323 Memory Leak Denial of Service... ...
    (Focus-Microsoft)
  • ~~~~~~~~~~~~~~~ CANNOT FIND ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    ... cannot find server or dns error ... windows cannot find null ... windows cannot find the network path ... cannot find internet explorer on computer ...
    (comp.protocols.snmp)
  • Questions Relating to Administering Windows 2000 Server
    ... installed the network client on the target computer. ... Sarah has been attempting to install Windows 2000 ... Server for two days. ... Sarah has checked the cables and hard drives. ...
    (microsoft.public.cert.exam.mcse)
  • pqv소박한 꿈@mBGRx
    ... O-009바▣ MS Windows 2000 Datacenter Server -2만원 ... Main Application (Borland C++ Builder 6 Enterprise Edition) ... Y-166▣ Sex Starved Sluts 1 (Divx) ...
    (FreeBSD-Security)