RPM does not respond

Problem:

My print client is connecting to the PC, but RPM Remote Print Manager™ does not respond.

Answer:

It turns out that the Microsoft Windows 95 or NT TCP/IP stack does not tell RPM that another print server is running on that machine. If you are running NT, make sure that TCP/IP printing services are not running. If you are running Windows 95, make sure that you are not running a package that includes an LPD client, such as Exceed or Execustar.

 

Article 113-03

Issue: Connectivity
Topic: RPM 9X All

Did this information answer your question?

Your email address (optional):

Please provide additional comments. We welcome your feedback.

Case Studies
Satisfied customers using Brooks' software in their print environments to simplify document workflows.
 
 
IPDS Printing
Print IPDS files to any of your PCL-supported printers for ONLY $495!
 
 
Host to Windows
White Paper  Simple tools for connecting IBM-based data with the Windows® world
 
 
Print to File
RPM writes to disk incoming data from ANY host system, checks for duplicates...
 
 
AS400 Printing
RPM applies all the features of Windows printing to your AS/400 (iSeries / zSeries) spool files
 
 
UNIX to Windows
RPM enhances UNIX print services' ability to customize and control processing