Printing From RS-6000 to Windows 98 Stopped Working

[Guest]

Print jobs sent from an RS-6000 AIX print queue, do not successfully print on
a Windows 98 workstation. We have printed this way for years. Suspect the
latest critical Windows 2000 server updates may have broken the link between
RS-6000 and Windows 98 workstation. The Windows 2000 server can successfully
print to the Windows 98 printer. It just does not relay the print job from
the RS-6000 to the Windows 98 workstation.

This situation effects only Windows 98 workstations. I am still successfully
printing to Windows 2000 pro workstations, configured the same way as the
Windows 98 workstation.

We use the following method to print from a RS-6000 to local printers
attached to Windows 98 workstations.
1. RS-6000 sends print job to Windows 2000 server running TCP/IP printing
service.
2. Windows 2000 server relays print job to print share on Windows 98
workstation.

Setup
1. Printer on Windows 98 workstation is shared.
2. Printer is installed in Windows 98 using the local share name
\\Windows98\PrinterShare
3. Windows 2000 server printer is shared.
4. Remote print queue in AIX is established; Print queue is directed to
Windows 2000 share.

What was attempted to remedy this situation.
1. Deleted / installed AIX print queue
2. Deleted / installed W2k print queue
3. Deleted / installed Windows 98 print queue
4. On W2K server gave printer operator status to everyone.
5. Stopped / started W2K TCP/IP print services - multiple times.
6. Stopped /started W2K print spool services - multiple times.
7. Paused then Restarted document printing
8. Paused then Resumed document printing
9. Printed numerous test documents from W2K server to Windows 98 workstation.
Sometimes, restarting the services allows the print job to print.

 

[Guest]

Combination of two critical updates caused this situation. KB885835 &
KB885836 are the update numbers. Removal of these updates restored the
printing.

Now, my concern is how vulernable is my server without these updates?

 

[Rebecca Chen [MSFT]]

Hi Charlie,

Based on my research, both 885835 and 885836 are critical security update,
a security issue has been identified that could allow an attacker to
compromise your Windows-based system and gain control over it. Therefore, I
strongly recommend you install two updates.

A privilege elevation vulnerability exists in the way that the Windows
Kernel launches applications. This vulnerability could allow a logged on
user to take complete control of the system. This is fixed in Update
885835. More details can be found from the link below, snippet "General
Information":

Vulnerabilities in Windows Kernel and LSASS Could Allow Elevation of
Privilege (885835)
http://www.microsoft.com/technet/security/bulletin/ms04-044.mspx

Update 885836 has fixed the vulnerability in WordPad . A remote code
execution vulnerability exists in the Microsoft Word for Windows 6.0
Converter. If a user is logged on with administrative privileges, an
attacker who successfully exploited this vulnerability could take complete
control of the affected system. However, user interaction is required to
exploit this vulnerability.

This is addressed in the following link, snippet "General information/
Vulnerability Details"

Vulnerability in WordPad Could Allow Code Execution (885836)
http://www.microsoft.com/technet/security/bulletin/MS04-041.mspx

According to my experience, Windows security updates will tight the system
security by changing certain system behavior. If the third-party
application has not been developed in a strict way, probably, some
third-party application cannot properly work after patch the system.
Another possibility is that the security patch has change the way which the
printer application need to authenticate with down-level system, such as
Windows 98.
I suggest you consider the following two methods:


1. Contact the printer vendor to update the printer application to resolve
this issue.

2. If possible, you may consider upgrading the win98 client to win2k or
above since the win2k has greatly secured the system in a different way. On
the other hand, Win98 is out of date and expires its life cycle.

Any update, let's get in touch!

Best regards,

Rebecca Chen

MCSE2000 MCDBA CCNA


Microsoft Online Partner 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.