VKontakte.DJ
forum traveling
 

Celestial Software

...better by design

Home Support SSH Client Forums
Welcome, Guest
Please Login or Register.    Lost Password?
Incoming Binary Zmodem Transfer Fails (1 viewing) (1) Guest
Go to bottom Favoured: 0
TOPIC: Incoming Binary Zmodem Transfer Fails
#1745
Incoming Binary Zmodem Transfer Fails 11 Years ago  
(If I am in the wrong forum, please direct me accordingly.)

I run Absolute Telnet 3.85 on Windows 98. (I cannot afford to upgrade either.) I establish a dialup PPP connection to my ISP, which runs netBSD servers, and "A.T." into my shell account using SSH-2 and XTERM emulation.

From time to time I want to transfer files between my shell account and my Win98 box. Just this evening I had no problem transferring straight text files in both directions with Ascii Zmodem transfer. However, I am not able to download a binary file from the shell host to the Win box.

On the shell host, I cd to the directory where the file resides. Then I enter (no quotes) 'sz -b sample.jpg' for a 252830-byte JPEG file. The A.T. Zmodem receive message box opens, and the "progress meter" shows file transfer. But as soon as it appears that the transfer is complete, I get the error message "Transfer failed!" and there is no file on the local machine.

This happens every time I try it. I know that the JPEG file is good, because I can open it with a web browser (Opera, in my case). See http://www.panix.com/~bartlett/sample.jpg . (No viruses, but obviously appropriate precautions should always be taken.)

Any ideas on why Ascii transfers succeed and binary transfers fail? Thanks.

[ November 02, 2006, 12:32 AM: Message edited by: Brian T. Pence ]
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1746
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Paul,

Can you test with 5.06 to see if it makes a difference? A number of changes have been made to the file transfer since 3.85.

http://www.celestialsoftware.net/telnet/AbsoluteTelnet5.06.exe

Brian
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1747
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
I downloaded it but have not installed it. Will I be charged if I install it? My year of free upgrades has come and gone. You are entitled to the fruits of your labor, but I genuinely am in a money pinch just now. (I think A.T. is a great product, and your support shines. I have been using it for several years now and have pitched it on my ISP's in-house newsgroup.)

If I install the later version, will my *.TNT files still be valid? They are what I use to access my ISP's servers so that all my settings are rolled in. Do I just install the later version right over the top of what I have?

I forgot to mention that the problem with binary file transfers only arose after I switched to using SSH-2, if that is significant. Most of the transfers I do are Ascii.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1748
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
You can install 5 on top of what you have or in a separate directory.

You can always install the older version after you're done testing. TNT files will not be affectedd, but make a copy of them if you're worried about that.
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1749
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Just a short time ago I finally had a chance to install version 5.06. The installation went fine, but it turns out not to be usable, at least as things are now set up.

I started v. 5.06 and went to open one of my .tnt files. Very quickly I got an error message: "Connect to panix2.panix.com failed. Winsock Error: the namelen argument is incorrect." (My ISP has five shell servers. I commonly login to one of them specifically for SSH-2. However, I have SSH-2 .tnt files set up for all five.)

So v. 5.06 is not working. I reinstalled v. 3.85 back over the top, and I am able to login again just as before. When I did the installation, I forgot to install 5.06 in a separate directory, so it and the reinstallation of 3.85 went into the same directory.

I do have a problem with this machine, something having to do with name resolution, that affects three different web browsers as well as A.T. Sometimes things will hang for almost a minute and then break loose on their own. However, I got this winsock error message almot immediately, and I tried it a couple of times.

[ November 03, 2006, 06:08 PM: Message edited by: Paul O. Bartlett ]
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1750
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Winsock Error: the namelen argument is incorrect You're the second person to report this. May have something to do with the new IPV6 code in version 5 not working properly under Win98. In Win98, it is supposed to gracefully degrade to IPV4-only because Win98 does not support IPV6. I'll have a look.

I do have a problem with this machine, something having to do with name resolutionI've heard of this happening on Win9x with dialup accounts. I'm not sure why it happens, but it is not A.T. specific, so I'm not going to be much help resolving that. In any case, it is not related to the problem above.

I'll have to work out the "namelen argument is incorrect" issue and get back to you to test the real original problem of zmodem transfer.

Brian
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1751
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Thanks for the quick response. I tried 3.85 with another binary file, this time a PDF, and the transfer still fails. There should be a way to convert a binary file to Ascii encoding so that I could download two files. Something about base64 or some such. I need a temporary workaround. It may be Monday before I get to it, though.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1752
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
You could use uuencode/uudecode, but you'd have to be able to uudecode on the Windows side.

Or, you could just wait till I have this figured out. I'm working on it tonight.

Brian
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1753
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Alright, Paul.

I've got this fixed. You should be able to connect using SSH2 on Win98 now. Now, if you could test the zmodem, I'd be grateful.

http://www.celestialsoftware.net/telnet/AbsoluteTelnet5.09.exe

Brian
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1754
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
I downloaded it, but I am working this weekend, so I will probably not get to it until Monday. I will keep you posted.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1755
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
STATUS REPORT:

The attempt to use 5.09 was only partially successful. I was able at least to login to my remote shell account, but I was not able to download files.

I have a PDF file, 774352 bytes. I UUENCODEd it to 1066922 bytes. When I tried a 'sz -b xxx' for the PDF, the download started, but after a while the progress meter and bytes received field "stuck" and did not increase. I noticed that there was a bytes received received field, but in the panel the bytes transmitted (so I am guessing) field was truncated in the display and hard to read. Anyway, eventually the transfer ended, as shown by the little icon in the system tray for a dialup connection, but there was no message of successful or failed completion. When I looked in Windows Explorer, there was no file in the directory.

When I tried to start the download, A.T. complained that "C:Download", my download directory, did not exist, even though it has existed for years. I clicked on the directory in the message box, but A.T. did not seem to accept it, but eventually started the -- failing -- download.

Next I tried 'sz -a' with the UUENCODEd file. Same complaint from A.T. that the C:Download directory does not exist, even though it does. Eventually the download started. It failed, although I did not get a message one way or the other, as just about then my firewall put up an alert about an intrusion attempt. (I have been getting a lot of those lately.)

Another item. Both 3.85, my current version, and 5.09 both say from time to time that my panix2.tnt has been modifed, even though it hasn't. I don't know what they are complaining about. When I go to close A.T., I have to tell it not to save any -- nonexistent -- changes.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1756
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Are you using the US-English version of Win98 or one localized in another language?

Do you have access to a Win2000 or XP box somewhere where you can test sending from the same host to a different client?

What type of host are you using?

What version of sz?

Any chance you could give me a temporary login to that machine so I can test this myself? It may be something host specific that I am not able to reproduce here.

Brian
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1757
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
1. US-English, no localization.

2. No. An old, decrepit computer running Windows 98 is all I have and have access to. If this old machine ever breaks down, I am out of luck. (Some of us are behind the technology curve and can't do anything about it. We're lucky to have anything at all.)

3. NetBSD 3.1_RC3, according to the login of the shell host. I don't know what kind of front end servers are involved.

4. 'sz --version' shows "sz (lrzsz) 0.12.20". It is whatever is supplied by my ISP. I never previously had a problem transferring files. I don't know what changed, as not long ago I was able to transfer even binary or large Ascii files with A.T. v3.85.

5. So far as I understand, I cannot give you temporary login without giving you total access to my account with my userid and login password, and that would violate my subscription agreement with my ISP, if I recall correctly. My ISP is a commercial enterprise in New York City, and they run a tight ship. Bend the rules and you're out on your ear.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1758
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
A bit more. I can upload and download Ascii files in the 10's of KB size range with no trouble. But I am wondering if there is a filesize problem involved. I tried to upload a 379KB ZIPfile and ran into trouble. For a long time after the transfer started the dial-up networking icons in the system tray flashed on and off back and forth, but eventually the message box disappeared, and all I got was "square box" characters at the shell prompt, and it took 14000 ^C's to break things loose. An attempt to upload an 87KB ZIPfile also failed with the same problem.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1759
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
ADDITIONAL INFORMATION

Usually I use A.T. in SSH-2 mode for the security. However, not long ago I decided to try an experiment. Rather than login to my shell host with SSH-2, I tried straight TELNET. Now I got some different results.

I was able to download large files with Zmodem in both Ascii (almost 1MB) and binary (>700KB) modes correctly. One was a PDF (binary) and the other was a UUENCODE (Ascii) of that same file. Both were received on my Win98 machine correctly. The Ascii file UUDECODEd correctly, and both versions of the PDF were good. So there is a first impression that somehow SSH-2 as such may be involved.

There is still the erroneous message about the download directory being missing, even though it isn't. I have to go through the directory browse and select it, and even then the download process still squawks. I have to go through that a time or two and then Cancel, and the download starts. I don't know what is going on here.

HOWEVER, I cannot upload successfully in TELNET mode, either Ascii or binary. I start 'rz -a[b]' on the shell host. Then I get the usual browse box to select the file. I select the file, and the browse box pops up again. I select the file a second time, and then the upload supposedly starts. But within just a second or two the Zmodem progress window closes, some gibberish shows up on the shell host, and I have to ^C out to interrupt.

So at least there is something else involved. I can download in TELNET mode but not in SSH-2. I can upload small files in SSH-2 but cannot upload large files in SSH-2 or anything in TELNET. (I do want to be able to use SSH-2 for the security.)

Finally, as I have mentioned before, there seems to be a visual glitch in the Zmodem window. It appears that the "Packets Transmitted" label is truncated.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1760
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
I'm not ignoring you, I'm just having trouble reproducing this bug in order to fix it.

Is there anything about your box that I should be aware of? Custom shells, desktop, program launchers, or task switchers?

Anything out of the ordinary?
bpence (Admin)
Admin
Posts: 1328
graph
User Offline Click here to see the profile of this user
Logged Logged  
 
Brian Pence
Celestial Software
SSH , SFTP, and Telnet in a tabbed interface for Windows XP, Vista, Mobile, and others
 
The administrator has disabled public write access.  
#1761
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
I am not aware of anything out of the ordinary with the software. This is a very generic Windows 98 machine. I have all the critical updates installed that Microsoft made available up to the time that they dropped support for 98. You could say that it is plain vanilla. I can't think of anything that has changed since I was able to transfer large files with version 3.85.

I did drop back to 3.85, as it suits my needs as long as I can make the file transfers. Just to check I logged into a different shell host (I have a choice of five) from the one I usually use. There was no diference in the results.

It seems to be a file size issue with 3.85. I was able to succesfully download both Ascii and binary files in the 115 - 200 KB range with no problems. Attempting to download a larger file failed. Uploading any file of much more than about 26 KB -- that is the largest file I tried -- in either Ascii or binary fails. The progress meter quickly -- very quickly -- shoots up to about about 115 KB (and I don't see how that much data could possibly be transferred that quickly over a slow dialup link) and then hangs. Eventually the transfer message box disappears and it takes many, many, many ^C to the shell host to regain control.

Now that I think of it, one thing has changed, although I don't know whether that was in relation to the inability to transfer large files, as usually I am only transferring small to medium files.

I have only a dialup connection with a modem. Some time back I had a major hardware problem and now have a different motherboard in the machine. I also had to install a different modem with a different driver. My usual connect speed used to be 26400. About the same time as I made the hardware change one day I noticed a telephone repairman diddling around the apartment building. Since that time, my usual connect speed has dropped to 24000. I know the machine and modem are capable of more, because when someone else (I am not a hardware type) installed the modem and driver in another location we got a connect speed of 31600. So there does seem to be a hardware limitation on connect speed in my particular location. Whether any of this coincided with the inability to transfer large files with 3.85 I can't say, as I do not recall when I had last tried to transfer a large file until I started this thread.

But I am definitely suspicious about how the progress meter shoots up in just a few seconds to 115 - 120 KB when trying to upload a large file.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1762
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Would some sort of debugging data help? I have DebugView installed on this machine. It has been quite a while since I used it, but I am sure I could fire it up again for a version of A.T. that has debugging points.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1763
Re: Incoming Binary Zmodem Transfer Fails 11 Years ago  
Is there another subversion of A.T. I can try? Nothing has changed. This everning I tried to download a 175245 byte binary file with SSH-2 on A.T. 3.85, and it failed again. On straight TELNET it worked. This is the same as before. I am willing to try another subversion if it is available, although I am not aware of any goodies in v5 that are really of much use to me.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1764
Re: Incoming Binary Zmodem Transfer Fails 10 Years, 8 Months ago  
You may try this:

Code:

stty raw; lrz
when finished, type this:
Code:

stty sane
wangyi6854 (User)
Junior Boarder
Posts: 25
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
The administrator has disabled public write access.  
#1765
Re: Incoming Binary Zmodem Transfer Fails 10 Years, 8 Months ago  
Thanks for the tip. I will try it next time I need to do a transfer. (I don't transfer every session.) Version 5 of A.T. -- at least the last time I looked -- buys me nothing I need or could use over the version 3.85 I have, except that the transfers of large files unexplicably and without warning began failing last fall, and my attempts to use some builds of 5 that Brian Pence provided were generally not usable. Usually I have had to jigger around outside of A.T. to download some files such as large PDFs.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
#1766
Re: Incoming Binary Zmodem Transfer Fails 10 Years, 8 Months ago  
I tried the suggestion, and it did not work when trying to upload a 581KB ASCII file. The result was the same as before. The upload would seem to proceed, but after a time the progress bar would freeze. The icons in the Win98 system tray for DialUp Networking would blink on a off for a while and then stop. It was hard to close the transfer window with the Cancel button. When the window eventually closed, the shell prompt would show numerous unreadable characters, and many, many ^C were necessary to regain control on the shell host. Apparently Brian Pence has abandoned this item as unresolvable.
bartlett22183 (User)
Expert Boarder
Posts: 92
graphgraph
User Offline Click here to see the profile of this user
Logged Logged  
 
Paul Bartlett
 
The administrator has disabled public write access.  
Go to top