Article View: comp.os.netware.misc
Article #677Re: File corruption on NetWare 3.12
From: Alex Tatistcheff
Date: Thu, 18 May 1995 00:00
Date: Thu, 18 May 1995 00:00
22 lines
1486 bytes
1486 bytes
In article <D8Fsos.1D0@bokonon.UUCP>, stephen@bokonon.UUCP (Stephen M. Dunn) says: > > I just inherited a client this week who appears to have a long >history of data corruption on their server. I'm still working on (deleted to save bandwidth) You might do some checking to see if you can reproduce it yourself. You can create an ASCII file with all A's in it or something then copy it from the server to a workstation repeatedly. After each copy, run a compare and when the compare fails use your LANalyzer to look at the packets and see if it's happening on the wire on somewhere else. NW 3.12 and up also has a feature called IPX checksums which is useful for troubleshooting driver problems. You set it in the net.cfg and with a SET command on the server. Good luck... -------------------------------------------------------- Alex Tatistcheff, CNE CRI/The Resource Group, Inc. cri@micron.net --------------------------------------------------------
Technical Details
Message-ID:
<3pg6iu$nev@mis02.micron.net>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailReferences:
<D8Fsos.1D0@bokonon.UUCP>Show Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: fe659,551869cd2282a43f X-Google-Attributes: gidfe659,public X-Google-Thread: f8bf7,551869cd2282a43f X-Google-Attributes: gidf8bf7,public From: CRI@micron.net (Alex Tatistcheff) Subject: Re: File corruption on NetWare 3.12 Date: 1995/05/18 Message-ID: <3pg6iu$nev@mis02.micron.net> X-Deja-AN: 102890251 references: <D8Fsos.1D0@bokonon.UUCP> organization: CRI/The Resource Group newsgroups: comp.os.netware.misc,bit.listserv.novell