home *** CD-ROM | disk | FTP | other *** search
- Number : A1TH082390U417
- Subject : Error "IPX received incomplete packet from <node #>"
- Date : February 14, 1991
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
-
- PROBLEM: The error "IPX received an incomplete packet from <node #>"
- appears on the console of NetWare 386 v3.1 sites.
-
- SOLUTION: There is a patch on NetWire. The file name is IPXINC.ZIP in
- library 16.
-
- Through research and reports from customers, it has been
- determined that this error does not indicate any serious
- problem. The file server merely discards the packet and
- requests the workstation to send another copy. Known
- drivers that may exhibit this error are the older NE2000 and
- NE/2 drivers (both file server and workstation drivers).
- However, other drivers may also cause this error to occur.
- When these drivers are rewritten and certified for NetWare
- 386 v3.1, the error should no longer occur.
-
- COMMENTS: The following indicates other possible solutions. These
- cases have not been verified by Novell:
-
- 1) A customer had a problem with DisplayWrite 4 made by
- IBM running on NetWare 386 v3.1 running Token-Ring.
- The workstation would hang when loading and the file
- server received the error "IPX received incomplete
- packet...". The problem was solved by changing the
- packet size at the workstation when loading IPX (for
- example: IPX TBZ=2000).
-
- 2) A customer was receiving the error "IPX received an
- incomplete packet" on the console. It turned out that
- he had a DMA conflict in the file server. After
- changing the DMA setting the error disappeared.
-
- 3) A developer was running their program and received this
- error.
-
- In his program he issued an INT 10 to the video with a
- scroll down (ie: al=0, cx=0, DH was the number of
- columns - DH had FF). Instead of issuing an INT 10 to
- the video with a scroll down, he changed it to be
- number of rows equal to 24. Executing the program
- worked without getting the error.
-
-