Actually, Router A is a Cisco 2600 and Router B is a Cisco 2500. They both
come into a Bay Networks Accelar 1200 switch. The server and the packet
sniffer machine are both on a SynOptics LatticeHub 2813SA connected to the
Accelar 1200. The server is running QNX 4.25, and the client machines are
running some flavor of UNIX, most probably SCO. There are no Microsoft
I am now running Proc32 version 4.25H, Net version 4.25C, Net.epic version
4.25F, and Socklet version 4.25H. I’m still seeing the exact same problem.
Any more ideas?
“Ivan Bannon” <firstname.lastname@example.org> wrote in message
Are Router A and B Microsoft Windows platforms? If so then even though
app closes the socket I have seen where the MS side does not see it as
will not allow the client to reopen another socket on the same port.
Shawn P. Stanley <> email@example.com> > wrote in message
news:8ombdi$k2m$> firstname.lastname@example.org> …
Thanks, I’ve upgraded as suggested and I’ll post again if the problem
“Heather Johnstone” <> email@example.com> > wrote in message
news:8om1h1$b3b$> firstname.lastname@example.org> …
You are running an older version of Net.epic. Can you upgrade to the
driver, which is part of the qnx4.25D patch. You’re Socklet is also
Can you also update to the latest tcpip patch C.
Shawn P. Stanley <> email@example.com> > wrote:
I have an application which listens for TCP connections. When it
connect notification, it accepts the connection and spawns a process
handle it (ala inetd). The spawned process reads a message from the
writes a message to the socket, shuts down the socket, then closes
socket. A very normal application in that respect.
I’ve been receiving reports that every once in a while, for a period
anywhere from five minutes to an hour, clients time out trying to
the port. These clients come through what I’ll call Router A. At
time, clients coming through Router B have no problems.
I have a packet sniffer on the same wire as the server. Normally,
packet sniffer sees the TCP sync sequence packets to the server and
ack packets from the server for the connections coming from routers
both. When the “outage” occurs, I can see in the packet sniffer log
all the TCP sync sequence packets from Router A clients go
the TCP sync sequence packets from Router B are answered with TCP
I’m using Socklet 4.25C dated August 19, 1998. I’ve got four
processes running for my various network interfaces, all of which
version 4.24B dated September 24, 1998.
firstname.lastname@example.org > +1 612 512 9500
email@example.com > +1 952 929 5181