G
Guest
Hello,
I have a clients running Windows 2000 alongside 4 Widows XP Pro clients that
logon to the domain. When clients logon to the domain as soon as their logon
script executes I get this error appear on the server:
Event ID: 10
Source: Print
User: NT AUTHORITY\ANONY
Type: information
Description: Document XXX, Remote Downlevel Document owned by was printed
on Printer_nameX via LPT1:. Size in bytes; ## pages printed: 0
I then have to manually delete all the documents from the print queue. This
happening to the three workstations all are using the scripts are setup. When
they are finally cleared out the qeueue everything is fine the users can
print during the day, but at logon it happens again.
I have recently just installed Symantec AntiVirus Corporate Edition 10.2 and
I just need to confirm that this was not happening before I installed it I
want to confirm my Antivirus protection is not causing any problems, I've
never seen this type of error before.
I've scanned the server and the workstations for viruses but I can't find
any.
However, if I remove the startup script from running the error does not
occur, but the script is used to map shared printers to LPT 1 and LPT 2
because their account package is a DOS based program so they need these
mappings, is there any other way I can achieve this without using netuse?
I have referenced these articles:
http://support.microsoft.com/d...?scid=kb;EN-US;Q137065
&
http://support.microsoft.com/d...x?scid=kb;en-us;312015
I have a clients running Windows 2000 alongside 4 Widows XP Pro clients that
logon to the domain. When clients logon to the domain as soon as their logon
script executes I get this error appear on the server:
Event ID: 10
Source: Print
User: NT AUTHORITY\ANONY
Type: information
Description: Document XXX, Remote Downlevel Document owned by was printed
on Printer_nameX via LPT1:. Size in bytes; ## pages printed: 0
I then have to manually delete all the documents from the print queue. This
happening to the three workstations all are using the scripts are setup. When
they are finally cleared out the qeueue everything is fine the users can
print during the day, but at logon it happens again.
I have recently just installed Symantec AntiVirus Corporate Edition 10.2 and
I just need to confirm that this was not happening before I installed it I
want to confirm my Antivirus protection is not causing any problems, I've
never seen this type of error before.
I've scanned the server and the workstations for viruses but I can't find
any.
However, if I remove the startup script from running the error does not
occur, but the script is used to map shared printers to LPT 1 and LPT 2
because their account package is a DOS based program so they need these
mappings, is there any other way I can achieve this without using netuse?
I have referenced these articles:
http://support.microsoft.com/d...?scid=kb;EN-US;Q137065
&
http://support.microsoft.com/d...x?scid=kb;en-us;312015