| Title: | PATHWORKS V5 for DOS and Windows |
| Notice: | OS2LAN::OS2:[PUBLIC] is alive again, but not what it used to be |
| Moderator: | RANGER::CURLESS |
| Created: | Fri Feb 11 1994 |
| Last Modified: | Fri Jun 06 1997 |
| Last Successful Update: | Fri Jun 06 1997 |
| Number of topics: | 7404 |
| Total number of notes: | 27276 |
Hello
a customer has a problem with Netscape and Pathworks TCP
transport protocol. It works normal but all 10~15 minutes
he gets a Netscape error.
A network error occured while Netscape was sending data
(Network error: Connection aborted)
Try connecting again
The customer has to reload the web page and then it will
work normal for another 10~15 minutes.
I made an IRIS trace and found out that the server sends
data to the client when the error occures. In this frame
there is a TCP protocol error 55. What is the meaning of
this error?
The customer is using
- MS-DOS V6.22
- MS-Windows V3.1
- PATHWORKS for DOS/Windows V6.0 ECO2
- Netscape Navigator V3.01
IRIS capture data Page 1
06/03/97 15:04:45
** Summary for frame 282 **
282 +.5m 54.881<- 54.251 TCP HOSTS2-NS: SYN ACK Src=81
Dst=4420 Seq=1633730568
Ack=600833478 Win=10164
IP TCP Dest=193.5.120.31
Src=150.1.250.98 Len=44
DLL DIX PType=08-00
** Detail for frame 282 **
DLL:
DLL: - - - - - Datalink Header - - - - -
DLL:
DLL: Frame 282 arrived at 22638.2 milliseconds, length = 60 bytes
DLL:
DLL: Destination Address = AA-00-04-00-71-DB (54.881)
DLL: Source Address = AA-00-04-00-FB-D8 (54.251)
DLL:
DLL: DIX format, Protocol Type = 08-00
IP:
IP: - - - - - Internet protocol (IP) - - - - -
IP:
IP: Internet header version = 4
IP: Internet header length = 20 bytes
IP: Type of service = 00
IP: .....0.. = Normal Reliability
IP: ....0... = Normal Throughput
IP: ...0.... = Normal Delay
IP: 000..... = Routine
IP:
IP: Total Packet Length = 44
IP: Identification = 6529
IP: Fragment Information = 4000
IP: Fragment Offset = 0
IP: ..0............. = May Fragment
IP: .1.............. = More Fragments
IP:
IP: Time to live (sec) = 253
IP: Protocol Type = 6 (TCP)
IP: Header Checksum = 39617
IP: Source Address = 150.1.250.98
IP: Destination Address = 193.5.120.31
TCP:
TCP: - - - - - Transmission Control Protocol (TCP) - - - - -
TCP:
TCP: Source port = 81 (HOSTS2-NS)
TCP: Destination port = 4420 (Unknown)
TCP: Sequence number = 1633730568
TCP: Acknowledgement number = 600833478
TCP: TCP Header Length = 24
TCP: TCP Control Bits = 12
TCP: .......0 = --
TCP: ......1. = SYN: Synchronize sequence numbers
TCP: .....0.. = --
TCP: ....0... = --
TCP: ...1.... = ACK: Acknowledgement
TCP: ..0..... = --
TCP: Window = 10164
TCP: Header Checksum = 21069
TCP: Maximum segment size = 1452
TCP: Protocol Error = 55
TCP:
** Hex for frame 282 **
0000: AA 00 04 00 71 DB AA 00 04 00 FB D8 08 00 45 00 ....q.........E.
0010: 00 2C 19 81 40 00 FD 06 9A C1 96 01 FA 62 C1 05 .,[email protected]..
0020: 78 1F 00 51 11 44 61 60 C0 08 23 CF FD C6 60 12 x..Q.Da`..#...`.
0030: 27 B4 52 4D 00 00 02 04 05 AC 55 55 '.RM......UU
Thanks for your help
Stefan Schmid
DEC Support Center Zurich Switzerland
[Posted by WWW Notes gateway]
| T.R | Title | User | Personal Name | Date | Lines |
|---|---|---|---|---|---|
| 7400.1 | SPELNK::curless | Sure it's a bug, but did you CLD/QAR it? | Tue Jun 03 1997 11:00 | 6 | |
Try reducing the number of threads/connections within netscape to 4... or less, our TCP/IP stack on DOS/Windows is limited in its ability to handle a large number of transfers over multiple connections, due to buffering problems. Jeff | |||||