Networks

Ask something
Discussion Locked

File transfers missing final bytes

0 helpful
5 replies

by mm212 1 view

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

This question was previously posted in the NetWare section, but got no response. I'm hoping someone in this area can help. I also upped the points.

On a Novell NetWare 4.11 WAN using IP and IPX, files being transferred to a couple of locations end up missing the final one or two bytes and thus end up unusable. We have 75 locations, most of which are on 56K leased lines. The problem locations are all on 56K leased lines.

Groupwise email seems to work fine across the WAN links, including attachments.

It's only files that are copied from one server or workstation to the NW server on the other end that cause problems. We've attempted copying by Windows Explorer, DOS copy and xcopy (with /v) and ncopy (also with /v). Nothing seems towork. All files copied end up missing the final one or two bytes. Using the /v with xcopy and ncopy show no errors, but the file isn't complete.

5 replies

by rick

Would you have access to a packet sniffer? You could then see the details on the transaction.

by mm212

We ended up changing out the routers before I had a chance to test much of anything. After the router change, we no longer have this problem. I appreciate your contribution even though it didn't directly help. Not wanting to do a bait-and-switch, I'm awarding the points to both of you. Thanks!

by estebandelatorre

It's a very strange issue, i'm not able to resolve it in a single shot, but this couple things may help you to debug the problem.
Try with another file:
1.- In order to isolate the problem, we have to issue a copy file from any wks of lan A, to the destination server on lan B, and then have it copied back again (different name) from a wks in lan B to the server in lan A. Do not use the "problem file" but any MS-Access database will be fine.

2.- While copying the file be sure (using monitor.nlm) that the file is not "in use" by any wks.

3.- When the file arrives again, not only DOS compared the two files lenght but try them with access.
Why Access, because it may came unusable if it has some corruption.

4.- If this test performssucessfully, you may have an application (the apps tahat leaves the file) problem, Which is writing a corrupted file. The file may be in use, or corrupted. To confirm this, copy the file to another subdir and try to read it.

5.- If you can't perform this test sucesfully, your files are getting corrupted in the wan link. This may be a virus!

6.- Why groupwise dont't have problems? The answer is that the groupwise comunications between MTA's is not standart! (neither smtp nor ftp ) it's groupwise protocol.

by mm212

We ended up changing out the routers before I had a chance to test much of anything. After the router change, we no longer have this problem. I appreciate your contribution even though it didn't directly help. Not wanting to do a bait-and-switch, I'm awarding the points to both of you. Thanks!

This discussion is closed to new replies.