UNIX for Advanced & Expert Users

Hello,

Anyone out there can help on this problem?

I have a zip file about 34MB containing a file in EBCDIC and is resided on a Windows 2000 server.

This zip file is retrieved and read from a UNIX server via SAMBA "SMBCLIENT" (by default the file is transferred via command bin) and issued error in reading remote file. Despite the read error, the incomplete file did transfer to the UNIX server.

Please explain the error and show how to correct the problem.

Note: I did spme test on read and retrieving zip files from a Windows NT 4.0 server and the zip file was read and transferred completely without errors to the UNIX server.

Thanks.

-------------------------------------------------------------------------------
Below showing the incomplete file copied:

-rw-r--r-- 1 clarify clarify 34078200 May 27 00:33 200304C20_blstnf.zip

Below showing the error messages:

smb: \csf_outputs\prod\2003-apr\cycle20\datalib\> smb: \csf_outputs\prod\2003-ap
r\cycle20\datalib\> getting file \csf_outputs\prod\2003-apr\cycle20\datalib\2003
04C20_blstnf.zip of size 34081006 bytes as 200304C20_blstnf.zip Error ERRSRV - E
RRerror (Non-specific error code.) reading remote file
Error reading file \csf_outputs\prod\2003-apr\cycle20\datalib\200304C20_blstnf.z
ip. Got 34078200 bytes
(3742.94 kb/s) (average 3742.94 kb/s)

Please post the UNIX OS and version.

Also, searching the samba archives came up with nothing for your error.

As a suggestion, why not change the file format from EBCDIC to ASCII and then transfer the file?

Thank you RTM:

The UNIX OS and Version is: AIX Version 4

The file format changing from EBCDIC to ASCII is not possible because this affect many areas and it is very costly to change unless there are no alternatives at all.

I know that this type of problems are very hard to evaluate because of so many variables. It is not something that have a straight answer for it. It is usually require debugging and/or reconfiguration.

However I would want to see anyone had this problem experience before, knowing the cause and the possible remedy for it.

From my recent tests I do know that the SAMBA smbclient which is using now works everytime with Windows NT servers but is not working 100% (sometimes works and sometimes don't) with Windows 2000 servers.

Worse come to worst SAMBA smbclient might have to be replaced by FTP.


Thanks.