zmodem uploads via dialup
Kirt Olson (CITS)
I tried to upload to my shell account using dialup (using minicom from
a Linux system) with no success. The system hung, never returning from
the dialog box. Although Ctrl-C appeared to stop the process, further
communication was impossible without hanging up and redialing.
I finally sent the file via zmodem to another ISP and mailed it to my
account. But everything at this end was the same as for the failed
attempts with USF.
Is zmodem uploading broken going through the terminal server? Is this
related to the need for sending ctrl-^ twice in PINE? Are the missing
characters in some prompts (elios, assword) being swallowed as well?
--Kirt
Glenn Cabler
In article <Pine.GSO.3.96.980204233418.29894B-100000@helios> "Kirt Olson (CITS)" <kol...@helios.acomp.usf.edu> writes:
>I tried to upload to my shell account using dialup (using minicom from
>a Linux system) with no success. The system hung, never returning from
>the dialog box. Although Ctrl-C appeared to stop the process, further
>communication was impossible without hanging up and redialing.
I am unfamiliar with this upload process (and Linux as well).
>I finally sent the file via zmodem to another ISP and mailed it to my
>account. But everything at this end was the same as for the failed
>attempts with USF.
I am unsure what you mean by the last sentence. Did you receive the file
intack or did this transfer fail as well. If it failed via this route, then
it would appear that zmodem is failing with your other ISP as well...which
might indicate a problem with zmodem on your system.
>Is zmodem uploading broken going through the terminal server? Is this
>related to the need for sending ctrl-^ twice in PINE? Are the missing
>characters in some prompts (elios, assword) being swallowed as well?
I've never supported the zmodem file transfer protocl. Kermit file transfers
(using Windows 3.x Terminal, Windows 95 HyperTerminal, MS-DOS Kermit) are
functional on the new modem pools.
Missing characters in some prompts sounds like a PC/modem configuration
problem...else everyone would be experiencing it.
Glenn Cabler
Academic Computing
Kirt Olson (CITS)
On Thu, 5 Feb 1998, Glenn Cabler wrote:
> In article <Pine.GSO.3.96.980204233418.29894B-100000@helios> "Kirt
> Olson (CITS)" <kol...@helios.acomp.usf.edu> writes:
>
> >I tried to upload to my shell account using dialup (using minicom from
> >a Linux system) with no success. The system hung, never returning from
> >the dialog box. Although Ctrl-C appeared to stop the process, further
> >communication was impossible without hanging up and redialing.
>
> I am unfamiliar with this upload process (and Linux as well).
Okay, I provided the info only for context.
> >I finally sent the file via zmodem to another ISP and mailed it to my
> >account. But everything at this end was the same as for the failed
> >attempts with USF.
>
> I am unsure what you mean by the last sentence. Did you receive the file
> intack or did this transfer fail as well.
This transfer worked like a champ.
> >Is zmodem uploading broken going through the terminal server? Is this
> >related to the need for sending ctrl-^ twice in PINE? Are the missing
> >characters in some prompts (elios, assword) being swallowed as well?
>
> I've never supported the zmodem file transfer protocl. Kermit file transfers
> (using Windows 3.x Terminal, Windows 95 HyperTerminal, MS-DOS Kermit) are
> functional on the new modem pools.
Okay.
> Missing characters in some prompts sounds like a PC/modem
> configuration problem...else everyone would be experiencing it.
This could be so and I will look for that possibility. My strong
impression is, though, that this happens *only* through the USF
terminal server connection. I don't recall seeing this if I Telnet in
from another site.
The P in Password is always missing after the login to Helios via the
server, but the H in Helios is only missing sometimes when returning
from some programs--not so clear to me.
I take it from your comment that others are not reporting this
character dropping.
--Kirt
Glenn Cabler
Try resetting your modem to factory settings before dialing into USF modems.
Some modem pools will initialize your modem to match theirs, then when you
dial into another type of modem, it cannot fully intialize your modem (due to
the left over settings).
It seems that I heard of this symptom (missing characters) from one other
user (do not specifically recall, but it has not been reported a significant
number of times). My first troubleshooting recommendation is the factory
reset for problems in connecting, getting disconnected abrubtly, and strange
behavior once connected.
If you've already tried that or if it fails to fix the problem, let me know.
Glenn Cabler
Academic Computing
In article <Pine.GSO.3.96.980205115734.7089A-100000@helios> "Kirt Olson
Kirt Olson (CITS)
On Thu, 5 Feb 1998, Glenn Cabler wrote:
> Try resetting your modem to factory settings before dialing into USF modems.
Okay.
> If you've already tried that or if it fails to fix the problem, let me know.
Okay.
An additional bit of info--I can upload using the less automated
xmodem using procomm under DOS (all else is the same).
Also, the lost P in Password happens with procomm as well.
--Kirt
Glenn Cabler
Since my last post, I have verified that zmodem transfers are not functional
on the new modem pools. One of our techs is looking into it.
As you have verified that xmodem file transfers work and I have verified that
Kermit file transfers work...until the zmodem problem can be rectified (if it
can) either xmodem or kermit transfers will have to do for those using VT100
emulation.
The missing character symptom might or might not be related to the zmodem
problem. I haven't experienced missing characters on any of my test systems.
Since my last post, I've heard from a couple of others with similar
symptoms...the login prompt was missing, but the password prompt was
displayed (although this was particular to the St. Pete pool). Perhaps we can
pursue this in more detail...let me know if this still happens after you reset
to factory settings.
Glenn Cabler
Academic Computing
In article <Pine.GSO.3.96.980205185603.10287A-100000@helios> "Kirt Olson
Kirt Olson (CITS)
On Fri, 6 Feb 1998, Glenn Cabler wrote:
> ...Perhaps we can pursue this in more detail...let me know if this
> still happens after you reset to factory settings.
Okay, I have finally dug out the books and checked what's happening
with my modem.
Indeed, the modem is reset to factory defaults whenever minicom is
started, so as long as I call USF first it has not been reset by
any other system. This is a Megahertz 14.4 on a 486DX50 running
minicom under Linux to do a VT100 emulation.
Logging in to make this post, directly after starting minicom, I still
get the missing P in Password when logging in to Helios. And the
Ctrl-^ needs to be repeated to set the mark in Pine.
So I would say those two pieces are now known to be the same with
factory settings established.
Since we began this conversation, some new things have emerged.
Sometimes I am getting 12000 connects, and when that happens the
connection is essentially unusable, acting like a very laggy telnet
when trying to log onto the server. I cannot say with certainty that
no other system had been called before calling USF, but I am certain
that it happens running minicom/Linux since the Procom/DOS combo only
runs the modem at 9600.
Another thing that sometimes happens is that the logon to the server
acts like a laggy telnet, although the connection is at 14400. When
this happens, it does not seem to be on a specific tty. If I then log
onto Helios, the laggy behavior continues throughout the session.
--Kirt
Glenn Cabler
Is this a PCMCIA card modem? Do you have the model number?
Glenn Cabler
Academic Computing
In article <Pine.GSO.3.96.980210211731.9562A-100000@helios> "Kirt Olson
Kirt Olson (CITS)
On Wed, 11 Feb 1998, Glenn Cabler wrote:
> Is this a PCMCIA card modem? Do you have the model number?
Yes. It's a CC3144. I've been using it for over a year with both
concentric and usf and only the behavior wrt usf is changed.
additional info at end.
> In article <Pine.GSO.3.96.980210211731.9562A-100000@helios> "Kirt Olson
> (CITS)" <kol...@helios.acomp.usf.edu> writes:
>
> >Indeed, the modem is reset to factory defaults whenever minicom is
> >started, so as long as I call USF first it has not been reset by
> >any other system. This is a Megahertz 14.4 on a 486DX50 running
> >minicom under Linux to do a VT100 emulation.
The connection I currently have is only at 12000. I am on tty 32 of
the server and Helios says I am on Tampa1 pts/13 at 13:39 11 Feb
It acts lagged, but it is less of a problem than such sessions on
earlier days.
Earlier today I had telnetted to Helios and I specifically checked the
behavior of Ctrl-^. Via telnet I need send the mark set command only
once to have it take effect.
Again, earlier today, I noted the following behavior when the login to
the server was troubled.
[simulation]
login: kolson@helijnk <-system throws in characters after the 'i'
password:qaz <-I enter junk password to force another trial
login: kolson@helqaz <-system throws in the junk password characters
[end simulation]
I saw this more than one time during the session, with different
characters.
--Kirt
Glenn Cabler
Are you using 57600 for the port speed (baud rate) in the communications
program?
Maybe you could bring the modem by sometime and I could plug it into another
machine...I've got a laptop that I just pulled a Megahertz XJ2144 out of.
I located the problem with the missing "P" in Password. It is in the code on
the Access Server...happens on some hosts after it processes the rlogin host
lookup...it doesn't affect the connection, but I'm sure some folks are
surprised when they encounter the "assword" prompt.
Glenn Cabler
Academic Computing
In article <Pine.GSO.3.96.980211134117.15243A-100000@helios> "Kirt Olson
Kirt Olson (CITS)
On Wed, 11 Feb 1998, Glenn Cabler wrote:
> Are you using 57600 for the port speed (baud rate) in the communications
> program?
The screen is reporting 115200 8N1. The whole thing is running 'as
received'--I never messed with this program at all.
> Maybe you could bring the modem by sometime and I could plug it into another
> machine...I've got a laptop that I just pulled a Megahertz XJ2144 out of.
Possibly, but not soon since I am expecting to travel next week.
> I located the problem with the missing "P" in Password. It is in the code on
> the Access Server...happens on some hosts after it processes the rlogin host
> lookup...it doesn't affect the connection, but I'm sure some folks are
> surprised when they encounter the "assword" prompt.
Cool. My concern with it is the *idea* of swallowing characters
sometimes. That kind of behavior might, for example, eat the character
that zmodem is expecting on upload. Or, it may be totally unrelated.
--Kirt
Glenn Cabler
Set the speed to 57600. Let me know how it performs.
Glenn Cabler
Academic Computing
In article <Pine.GSO.3.96.980212001819.2932A-100000@helios> "Kirt Olson
(CITS)" <kol...@helios.acomp.usf.edu> writes:>On Wed, 11 Feb 1998, Glenn
Kirt Olson (CITS)
On Thu, 12 Feb 1998, Glenn Cabler wrote:
> Set the speed to 57600. Let me know how it performs.
>
Okay, I did and I see no difference.
I am currently TTY38 on the server, pts/6 on helios via Tampa2 and the
time is 12 Feb 12:10 in that file.
My first attempt to sign on met with failures like the [simulation] of
my earlier post. I did notice the string s29=1 in one of the junk
strings thrown during the attempted login process.
On the next dialin I logged on with the first try, seeing the
'assword' prompt on the way in. Nothing else appears to have changed
in any way.
Oooops.
Okay, now I am TTY10 on the server, pts/48 on Helios via Tampa2 and
the time is 12 Feb 12:33 in that file.
An attempt to test an sz download led me to hang up and call again.
This logon went smoothly, although this session is bursty. I am at
57600 8N1, but I do not notice any behavior not seen at 115200, nor
any improvement. I did test the zmodem download and it is still
working the same as at 115200. I get a functional transfer, but the
start and end signaling is messed up, just as before.
--Kirt
Glenn Cabler
In article <Pine.GSO.3.96.980212121601.11766A-100000@helios> "Kirt Olson (CITS)" <kol...@helios.acomp.usf.edu> writes:
>On Thu, 12 Feb 1998, Glenn Cabler wrote:
>> Set the speed to 57600. Let me know how it performs.
>>
>Okay, I did and I see no difference.
Looks like this approach is dead-ended. Let me know if/when you can bring the
modem by to test it under another OS on another machine.
Glenn Cabler
Academic Computing