Your timers can be updated to:

[1  ]     Retransmission Interval Lower Bound (Secs)
[360  ]   Maximum Time to Wait For Remote Response (Sec)
[2  ]     Initial Retransmission Interval (Secs)
[8  ]     Maximum Retransmissions per Packet

Cleanest way to implement is to do a reboot.

(as long as I have the floor...) and patch patch patch (but you knew I was
going to say that :-)

For folks anticipating running their 3000 for any length of time you
*really* need to be up-to-date on your network patches.  This is THE part of
the operating system that exposes your 3000 to the rest of the world.  Just
because you haven't had any problems doesn't mean you won't.  so take a
proactive step and just do it.

   - d 'amen'

---
Donna Hofmeister
Allegro Consultants, Inc.
408-252-2330


> -----Original Message-----
> From: HP-3000 Systems Discussion [mailto:[log in to unmask]] On
> Behalf Of Stanfield, Randy (Carrollton, TX)
> Sent: Thursday, April 09, 2009 6:30 AM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Socket errors and any configurable Numbers or
> times?
> 
> Sorry, Donna, I never received your e-mail until this morning in the
> summary.
> 
> TRANSPORT GLOBAL CONFIGURATION:
> >   Home Network Name:              NET1
> >   Maximum Inbound Buffer Memory:  768
> >   Name Search Method:  1. (None selected)
> >
> > PACKET EXCHANGE PROTOCOL (PXP) CONFIGURATION:
> >   Checksum Enabled:                    N
> >   Retransmission Interval (Secs):      10
> >   Maximum Retransmissions Per Request: 4
> >
> > TRANSMISSION CONTROL PROTOCOL (TCP) CONFIGURATION:
> >   Checksum Enabled:                                Y
> >   Maximum Number of Connections:                   4096
> >   Retransmission Interval Lower Bound (Secs):      2
> >   Maximum Time to Wait For Remote Response (Secs): 180
> >   Initial Retransmission Interval:                 3
> >   Maximum Number of Retransmissions:               5
> >   Connection Assurance Interval:                   600
> >   Maximum Connection Assurance Retransmissions:    4
> 
> And Craig Lalley asked for this.
> 
> Linkname: DTSLINK   Linktype: PCI 100BT        Linkstate: CONNECTED
>  Physical Path:              1/12/0/0
>  Current Station Address:    00-30-6E-06-01-E4
>  Default Station Address:    00-30-6E-06-01-E4
>  Current Multicast Addresses:
>   09-00-09-00-00-01  09-00-09-00-00-03  09-00-09-00-00-04
>   09-00-09-00-00-06
> 
>  Transmit bytes            33287309530    Receive bytes
> 54689369376
>  Transmits                   133520651    Receives unicast
> 118548573
>  Transmits no error          133520651    Receives broadcast
> 3800948
>  Transmits dropped                   0    Receives multicast
> 198706
>  Transmits deferred                  0    Receives no error
> 122472987
>  Transmits 1 retry                   0    Recv CRC error
> 0
>  Transmits >1 retry                  0    Recv Maxsize error
> 0
>  Trans 16 collisions                 0    Recv dropped: addr
> 26697
>  Trans late collision                0    Recv dropped: buffer
> 48543
>  Trans underruns                     0    Recv dropped: descr
> 0
>  Carrier losses                      0    Recv dropped: other
> 0
>  Trans jabber timeout                0    Recv watchdg timeout
> 0
>  Link disconnects                    0    Recv collisions
> 0
>  Link speed                        100    Recv overruns
> 0
>  Link duplex                      Full    Link auto sensed
> No
>  Link mode            100Base-TX Addon    Secs since clear
> 4515169
> 
> Date:    Wed, 8 Apr 2009 13:24:49 -0700
> From:    donna hofmeister <[log in to unmask]>
> Subject: Re: Socket errors and any configurable Numbers or times?
> 
> Please send your NETXPORT.GPROT.TCP settings.        - d
> 
> ---
> Donna Hofmeister
> Allegro Consultants, Inc.
> 408-252-2330
> 
> * To join/leave the list, search archives, change list settings, *
> * etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *