| Title: | DEC TCP/IP Services for OpenVMS |
| Notice: | Note 2-SSB Kits, 3-FT Kits, 4-Patch Info, 7-QAR System |
| Moderator: | ucxaxp.ucx.lkg.dec.com::TIBBERT |
| Created: | Thu Nov 17 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 5568 |
| Total number of notes: | 21492 |
Hi to all!!
I have a customer who is using a client-server application between a pc
and axp.
What he pretends to do is seeing if the pc is not working against the
axp and then release the communication. He does this stopping the
process which is associated with the bgxx device , but we still seeing
packets between the two machines. It seems that ucx, because the
communication is over tcp/ip, is deleting the bg device but isn't
deassigning the port, so that the link still established between the
two sides.
What can be done so that this traffic of packets isn't going from one
side to the other after stopping the process related to the bg device?
Thanks in advanced
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 5555.1 | UCXAXP::GEMIGNANI | Fri May 30 1997 18:17 | 12 | ||
If you stop the process, the socket is going to be shut down by the
BGDRIVER. It will send FIN (finish) or RST (reset) packets to the
remote end AND, if the remote end sends datagrams it replies to them
with RST.
The TCP socket itself internally remains for a short time to ensure
that any communication with the remote system will be properly reset.
To do otherwise would mean that communication with the same ports and
hosts could easily get confused, as you could not tell whether the data
being exchanged is for the same actual connection or not.
| |||||