[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference jamin::pathworks32

Title:Digital PATHWORKS 32
Moderator:SPELNK::curless
Created:Fri Nov 01 1996
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:337
Total number of notes:1612

251.0. "pwprint and broken pipe" by KAOT01::M_GREEN () Thu Apr 24 1997 18:51

    Folks,
    wondering if anyone has seen this.   My customer has installed
    Pathworks 32 Print Server on a Windows 95 machine which acts as a
    gateway to other printers on the LAN.  A Vax (VMS 6.2, UCX 4.1) 
    across a bridged WAN connection submits print jobs via the Print
    client.
    
    Most of the time, all works well, but during peak demand the print job
    will begin failing with "broken pipe" messages.   From what I
    understand, this is usually a consequence of the network session
    shutting down due to network congestion or latency issues.  Indeed, at
    time of failure, his ping times register as anywhere from 500msec to 
    1000msec (1 sec).  
    
    The customer's feeling is that PWPRINT symbiont on Vax server is unable
    to handle a timed out TCP (or UDP) packet.  The error registers as
    follows:
    
    VAX logfile:
    
    GPRTT7A.LOG
    
    23-APR-1997 09:12:34.22 %PWPRINT-I-INFO T.T;5
    23-APR-1997 09:13:01.68 Print job was transfered ok
    23-APR-1997 09:13:01.68 broken pipe
    23-APR-1997 09:15:30.63 %PWPRINT-I-INFO T.T;5
    23-APR-1997 09:16:04.80 %PWPRINT-E-TCPREERR, TCP/IP Read error
    
    23-APR-1997 09:16:04.80 broken pipe
    23-APR-1997 09:16:34.85 %PWPRINT-I-INFO T.T;5
    23-APR-1997 09:16:37.46 %PWPRINT-E-TCPREERR, TCP/IP Read error
    
    .
    .
    . 
       
    
Thanks 
    mike Green 
    Canadian CSC
T.RTitleUserPersonal
Name		DateLines