I have been using SSH in various forms for several
years to connect to a Solaris Unix machine from
my Mac at home. Periodically, and more and more,
recently, SSH simply stops echoing. If I have multiple
ssh windows open, sometimes those other windows are still
responding, or sometimes they all seem to halt.
If I just wait patiently (which is hard to do), then
within 45 seconds or so, it starts responding again.
Also it seems that if I use other internet-based
applications, like a browser or an e-mail client,
that sometimes "wakes" ssh up, but it may be that
ssh was just going to wake up again anyway.
Has anyone else had this experience, and if so,
do you know what might be causing it, and if
there is anything that can be done?
With no data to go on, my initial guess is that it is
my internet service provider (which is RCN using
a cable modem) has some kind of bias against
small, frequent packets, as are necessary for a full-duplex
application like SSH or Telnet. I am imagining that they are
throttling down the connection that is generating so
many packets to avoid swamping the shared cable
bandwidth. Is that possible? Would I do better with
a different kind of internet connection (e.g. one that involves
at least a partially "dedicated" line, such as DSL or
a fractional T1)? Is there something I can do
to avoid the problem (type slower? ;-).
Thanks,
-Tucker Taft
years to connect to a Solaris Unix machine from
my Mac at home. Periodically, and more and more,
recently, SSH simply stops echoing. If I have multiple
ssh windows open, sometimes those other windows are still
responding, or sometimes they all seem to halt.
If I just wait patiently (which is hard to do), then
within 45 seconds or so, it starts responding again.
Also it seems that if I use other internet-based
applications, like a browser or an e-mail client,
that sometimes "wakes" ssh up, but it may be that
ssh was just going to wake up again anyway.
Has anyone else had this experience, and if so,
do you know what might be causing it, and if
there is anything that can be done?
With no data to go on, my initial guess is that it is
my internet service provider (which is RCN using
a cable modem) has some kind of bias against
small, frequent packets, as are necessary for a full-duplex
application like SSH or Telnet. I am imagining that they are
throttling down the connection that is generating so
many packets to avoid swamping the shared cable
bandwidth. Is that possible? Would I do better with
a different kind of internet connection (e.g. one that involves
at least a partially "dedicated" line, such as DSL or
a fractional T1)? Is there something I can do
to avoid the problem (type slower? ;-).
Thanks,
-Tucker Taft