Conference abbott::mailworks-vms

1561.0. "Problem with DECnet OSI and Connect Process" by GRITS::CARTER_A () Fri Mar 21 1997 10:52

    Hello,
    
    Customer using Mailworks 1.3A-3, VMS 6.1, and an assortment of DECnet
    and  TCP/IP 2.7 clients.  They all can connect and work successfully
    and then all of sudden the team links users start to get filcabinet
    disconnect errors and they are disconnected and new users cannot
    connect. From the VT interface they receive errors like 8420 which
    insufficient system resources are the remote node and 8300 network
    partner aborted logical link.  Other systems related to DECnet also
    occur ie we cannot make a decnet link to their system using a tool we
    use called DSNlink and he has problems using Motif.
    
    If we stop and start the connect process (not the muas$server process)
    all of these problems go away and the users can succesfully connect for
    about a day.  We have done things like increase the buffer_limit and 
    page_file on the a1mail$connect process and he is no longer having
    MUTEX wait problems BUT we are still seeing this strange problem in
    relations to DECnet OSI.  
    
    As a next step we have turned on connect logging and we are sending him
    ICF37 but we want to know if anything has seen a problem similar to
    this.
    
    Thanks,
    
    Angela Stover
    Mailworks Support